Created attachment 234308 [details] Screenshot: htop and other utilities; preparing to kill hp-systray After I sign in (to KDE Plasma), on a notebook with four CPUs, overall performance is poor until I kill: hp-systray The attached screenshot shows me preparing to kill the process tree with htop. Not shown in this particular shot: the excessive use of (one) CPU, by hp-systray, that is often observable in this situation. ---- % pkg info -x hplip hplip-3.22.4 % pkg -vv | grep -e url -e enabled url : "pkg+http://pkg0.pkt.freebsd.org/FreeBSD:14:amd64/latest", enabled : yes, url : "https://alpha.pkgbase.live/current/FreeBSD:14:amd64/latest", enabled : no, url : "file:///usr/local/poudriere/data/packages/main-default", enabled : yes, % uname -aKU FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #12 main-n255769-f16e38162c7-dirty: Tue May 24 11:48:57 BST 2022 root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 1400059 1400059 % grep hp-systray /var/log/messages May 25 10:02:09 mowa219-gjp4-8570p-freebsd /hp-systray[67590]: hp-systray[67449]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... May 25 23:01:31 mowa219-gjp4-8570p-freebsd /hp-systray[3302]: hp-systray[3174]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... May 26 09:09:21 mowa219-gjp4-8570p-freebsd /hp-systray[3498]: hp-systray[3372]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... May 26 18:28:38 mowa219-gjp4-8570p-freebsd /hp-systray[3418]: hp-systray[3254]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... May 28 21:15:30 mowa219-gjp4-8570p-freebsd /hp-systray[3617]: hp-systray[3494]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... May 29 04:54:30 mowa219-gjp4-8570p-freebsd /hp-systray[34630]: hp-systray[34481]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... May 29 05:27:08 mowa219-gjp4-8570p-freebsd /hp-systray[3633]: hp-systray[3480]: error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... % pkg info -x py38-dbus py38-dbus-1.2.18 %
I'm not seeing this, so if you are building your own packages, try rebuilding dbus (with X11 option on), dbus-glib, pydbus-common, and py38-dbus. You can also disable hp-systray by creating .config/autostart/hplip-systray.desktop in your home directory with the following two lines: [Desktop Entry] Hidden=true
Thank you, (In reply to Tijl Coosemans from comment #1) > … if you are building your own packages, … Nothing related to D-Bus, as far as I can tell: % pkg query '%R %n' | grep "poudriere " poudriere festlex-oald poudriere gpu-firmware-radeon-kmod-btc poudriere gpu-firmware-radeon-kmod-sumo poudriere gpu-firmware-radeon-kmod-turks poudriere linux-wps-office poudriere openzfs poudriere pkg poudriere pulseaudio % ls -hln /usr/local/etc/poudriere.d/options total 1 drwxr-xr-x 2 0 0 3B 1 Apr 02:22 editors_libreoffice drwxr-xr-x 2 0 0 2B 29 May 22:25 emulators_virtualbox-ose drwxr-xr-x 2 0 0 3B 10 Nov 2021 emulators_wine drwxr-xr-x 2 0 0 3B 23 Dec 15:03 multimedia_webcamd drwxr-xr-x 2 0 0 3B 15 Apr 11:56 sysutils_openzfs drwxr-xr-x 2 0 0 3B 4 Mar 04:59 www_chromium drwxr-xr-x 2 0 0 3B 23 Dec 23:28 www_falkon % ---- I see D-Bus-related bug 263716 (reported by vermaden), however I do not have those symptoms. ---- Here I have: % /usr/local/bin/python3.8 /usr/local/bin/hp-systray -x HP Linux Imaging and Printing System (ver. 3.22.4) System Tray Status Service ver. 2.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. error: dbus failed to load (python-dbus ver. 0.80+ required). Exiting... ^C % pkg info -x py38-dbus py38-dbus-1.2.18 % pkg search -o py38-dbus devel/py-dbus Python bindings for the D-BUS messaging system % grep -R -i -e python -e systray /usr/local/etc/dbus-1/ % grep -R -i -e python -e systray /usr/local/share/dbus-1 % ---- desktop@ is the 0.80+ requirement still true? Or is there, now a greater requirement?
(In reply to Graham Perrin from comment #2) Is dbus enabled and running? You can check with "service dbus status". If it says "Cannot status dbus" then run "service dbus enable" followed by "service dbus start".
(In reply to Tijl Coosemans from comment #3) Yes, running.
Probed a few minutes ago: <https://bsd-hardware.info/?probe=1067f6ab27&d=FreeBSD>
Not a bug. Apologies for the noise. No problem, after the two Python commands at bug 264458 comment 18.