hp-systray 100% CPU usage since hplip 3.9.6

[iskarion]

Hello,

since upgrading to hplip 3.9.6, the hp-systray tool is no longer working for me. On system startup I have a "python /usr/bin/hp-systray" process stuck at 100% CPU usage.

Same result when killing the process and starting hp-systray manually. hp-systray is giving no error messages when started manually via terminal. The process is just freezing.

Up to and including 3.9.4b hp-systray did work just fine. I can print without problems, it's just hp-systray that's not working.

I did already unistall hplip and did re-download and re-install hplip 3.9.6 again. Though the problem still persists.
For installation I did use the automatic install.

I'm running Kubuntu 9.04 with KDE 4.2.4. Further details see attached hp-check.log

GDB is giving the following back trace at the point where hp-systray is stuck:

Program received signal SIGINT, Interrupt.
0xb73d2490 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
(gdb) bt
#0 0xb73d2490 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#1 0xb73d4959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#2 0xb6185d17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#3 0xb6e7fef6 in ?? () from /usr/lib/python2.6/dist-packages/PyQt4/QtGui.so
#4 0x080de562 in PyEval_EvalFrameEx (f=0x90d520c, throwflag=0) at ../Python/ceval.c:3706
#5 0x080df587 in PyEval_EvalFrameEx (f=0x8d62abc, throwflag=0) at ../Python/ceval.c:3792
#6 0x080e00b8 in PyEval_EvalCodeEx (co=0xb7daa608, globals=0xb7dec0b4, locals=0xb7dec0b4, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0)
    at ../Python/ceval.c:2968
#7 0x080e0217 in PyEval_EvalCode (co=0xb7daa608, globals=0xb7dec0b4, locals=0xb7dec0b4) at ../Python/ceval.c:522
#8 0x080fe0e1 in PyRun_FileExFlags (fp=0x8d11cc0, filename=0xbfe0c64b "/usr/bin/hp-systray", start=257, globals=0xb7dec0b4, locals=0xb7dec0b4, closeit=1, flags=0xbfe0b208)
    at ../Python/pythonrun.c:1335
#9 0x080fe43a in PyRun_SimpleFileExFlags (fp=0x8d11cc0, filename=0xbfe0c64b "/usr/bin/hp-systray", closeit=1, flags=0xbfe0b208) at ../Python/pythonrun.c:931
#10 0x0805c882 in Py_Main (argc=1, argv=0xbfe0b2d4) at ../Modules/main.c:599
#11 0x0805b972 in main (argc=Cannot access memory at address 0x24
) at ../Modules/python.c:23

See also attached strace output.

[Aaron Albright (albrigha-deactivatedaccount)]

Thanks for the report.

We haven't been able to reproduce this. Could I get specific steps you are doing? I've tried:

Installed Kubuntu 9.04
Install HPLIP 3.9.6

Reboot
htop - systray running correctly

Send a print job (watching htop) - No issue
Send print job while printer in error state - No issue
Send print job and put printer into error state - No issue.

What else can I try?

Thanks!

Aaron

[Xilanaz (a-vankaam)]

I dont know if this helps, but I seen this behavoir a few times under opensuse 11, when updating the nvidia driver manually so on ctrl+f1 terminal doing a init 3, the install and later a init 5 once the install is complete.

[iskarion (markus-goebel-hetos)]

Hi Aaron,

thanks for the quick reply.

>> Could I get specific steps you are doing?

- Install hplip 3.9.6 (with automatic installer)
- Reboot
- on KDE logon hp-systray is automatically started and immediately freezing. This is happening after every reboot / KDE re-logon.

So not many steps from my side involved. It's especially *not* related to sending a print job or any other interaction with the printer. Also it doesn't matter if the printer is switched on or off (my HP Color Laserjet CP1515n is connected via network).

As hp-systray is not really required for printing, one workaround for me is of course to kill the frozen hp-systray job after every restart or to prevent automatic starting of hp-systray in the first place.

Though currently I'm back 3.9.4b. At least what's also 100% reproducible is, that as soon as I go back to 3.9.4b, the problem disappears and when again upgrading to 3.9.6 the problem is back.

>> Installed Kubuntu 9.04

I will check if, I can reproduce the problem with a clean Kubuntu 9.04 install. My current Kubuntu 9.04 installation did start back in 2007 as Kubuntu 7.04 and was repeatedly upgraded. So I don't know if it's really behaving the same way as a vanilla 9.04 install.
Also I have some stuff installed, which is not part of the official Kubutnu 9.04 repositories like KDE 4.2.4 or the Nouveau driver. As hp-systray is Qt4 based (isn't it?) maybe it's conflicting with the most recent KDE 4.2.4 bugfix release or something like that. Though all other dependencies required by hplip like phyton or cups are from official Kubuntu 9.04 repositories.

>> when updating the nvidia driver manually so on ctrl+f1 terminal doing a init 3

I'm using the open source Nouveau driver, not the binary nvidia driver. Also changing runlevels back and forth doesn't have any effect on the hp-systray problem. So I'm not sure if this is really the same issue.

Kind regards,
Markus

[Aaron Albright (albrigha-deactivatedaccount)]

Are you still having this problem with 3.9.8? Please update if you are.

Thanks.

Aaron

[HinzundKunz (martin-tlustos)]

I have the same problem with 3.9.8. under kde 4.3.2, ubuntu 9.04. It also doesn't show up in the systray - just a black box, no icon. Clicking on it doesn't give any reactions.
Tried with standard values set, started with "never show up" and "always show up" option set, etc.
In system monitor it shows up three times when started.
I have two hp-printers - one at home and one in the office, which I connect over the network to.

Output of hp-systray -g (until it freezes and I have to kill it):

hp-systray[13075]: debug: Locking: /home/martin/.hplip/hp-systray.lock
hp-systray[13075]: debug: Creating pipe: hpssd (7) ==> systemtray (6)
hp-systray[13075]: debug: Creating pipe: hpssd (8) ==> hpdio (6)
hp-systray[13075]: debug: Creating pipe: hpdio (10) ==> hpssd (9)
hp-systray(hpdio)[13077]: debug: PID=13077
hp-systray(hpssd)[13076]: debug: PID=13076
hp-systray(hpssd)[13076]: debug: Entering main dbus loop...
hp-systray(qt4)[13075]: debug: PID=13075
hp-systray(qt4)[13075]: debug: Loading user settings...
hp-systray(qt4)[13075]: debug: FAB command: /usr/bin/hp-fab
hp-systray(qt4)[13075]: debug: Scan command: /usr/bin/xsane -V %SANE_URI%
hp-systray(qt4)[13075]: debug: Auto refresh: False
hp-systray(qt4)[13075]: debug: Auto refresh rate: 30
hp-systray(qt4)[13075]: debug: Auto refresh type: 2
hp-systray(qt4)[13075]: debug: Systray visible: 0
hp-systray(qt4)[13075]: debug: Systray messages: 0
hp-systray(qt4)[13075]: debug: Last used device URI: hp:/net/hp_LaserJet_4200?ip=192.168.20.3
hp-systray(qt4)[13075]: debug: Last used printer: photosmart_7700
hp-systray(qt4)[13075]: debug: Working directory: .
hp-systray(qt4)[13075]: debug: hp:/net/hp_LaserJet_4200?ip=192.168.20.3: back_end:hp is_hp:True bus:net model:hp_LaserJet_4200 serial: dev_file: host:192.168.20.3 zc: port:1
hp-systray(qt4)[13075]: debug: Cache miss: hp_laserjet_4200
hp-systray(qt4)[13075]: debug: Reading file: /usr/share/hplip/data/models/models.dat
hp-systray(qt4)[13075]: debug: Searching for section [hp_laserjet_4200] in file /usr/share/hplip/data/models/models.dat
hp-systray(qt4)[13075]: debug: Found section [hp_laserjet_4200] in file /usr/share/hplip/data/models/models.dat
hp-systray(qt4)[13075]: debug: Device URI socket://192.168.20.4:9100 is invalid/unknown
hp-systray(qt4)[13075]: debug: Exception: 4 (Unknown/invalid device-uri field)
hp-systray(qt4)[13075]: debug: Device URI cups-pdf:/ is invalid/unknown
hp-systray(qt4)[13075]: debug: Exception: 4 (Unknown/invalid device-uri field)
hp-systray(qt4)[13075]: debug: hp:/usb/photosmart_7700_series?serial=MY4CF2K16VU0: back_end:hp is_hp:True bus:usb model:photosmart_7700_series serial:MY4CF2K16VU0 dev_file: host: zc: port:1
hp-systray(qt4)[13075]: debug: Cache miss: photosmart_7700_series
hp-systray(qt4)[13075]: d...

[iskarion (markus-goebel-hetos)]

Just wanted to confirm, that I too still have the same problem with hplip 3.9.8. Currently I'm running Kubuntu 9.04 with KDE 4.3.2.
At the moment I'm still on hplip 3.9.4b.
Didn't do any further investigation so far, due to lack of time and because hplip 3.9.4b is working fine for me. This issue might very well be related to the fact that I'm running not the KDE/QT version originally delivered with Jaunty, but a more recent version from the backports repository.

I'll try if I can find the time to do a clean Kubuntu 9.04 install in VMWare, check if hplip > 3.9.4b is running there and then adding the non-standard stuff from backports which I currently have installed, to see if hp-systray is breaking.

Though I'll upgrade to Kubuntu 9.10 anyway once it's available. So first I will check if this is solving the problem.

[HinzundKunz (martin-tlustos)]

I have the same problem on my Ubuntu 9.04 machine, but ran accross this: update-notifier, which uses python as well and is displayed in the systray, has high cpu consumption, too - so it might be a python problem - maybe a dependency or so? Normal (non-systray) python programs seem to run fine.

[iskarion (markus-goebel-hetos)]

The problem was solved - at least for me - by upgrading to Kubuntu 9.10 (which comes with hplip 3.9.8).

[Boyd Stephen Smith Jr. (bss03)]

I'm getting a hang at 100% CPU on Debian Squeeze. This is consistent and occurs before I explicitly interact with the applet. I am using Plasma (KDE SC 4) as my desktop environment. Output of (hp-systray -g) after killing all hp-systray processes is attached, as is the strace output.

[Boyd Stephen Smith Jr. (bss03)]

Debian Squeeze shipped with 3.10.6. 3.11.1 is available in Debian's unstable. Should I attempt to reproduce with that version? I added the link to b.d.o#569976, but I'm not actually sure it is the same cause, it just seems quite similar.

[alfredo (alacis)]

Still happening, years later - this system is:

Linux <my machine's hostname> 2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:05:14 UTC 2011 i686 i686 i386 GNU/Linux

HPLIP version is 3.11.1
Device Manager Version 15.0 (Qt4)

Do you need further info?