Description of problem: When applet.py runs, it uses one cpu at 100% constantly. Running it from console does the same thing. This (similar) output keeps recurring on strace output: recvmsg(4, 0x7fff04d566a0, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable) write(6, "\1\0\0\0\0\0\0\0", 8) = 8 recvfrom(5, 0x113ad74, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=6, events=POLLIN}, {fd=5, events=POLLIN}, {fd=3, events=POLLIN}, {fd=7, events=POLLIN}, {fd=4, events=POLLIN}], 5, 0) = 1 ([{fd=6, revents=POLLIN}]) recvfrom(5, 0x113ad74, 4096, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable) poll([{fd=6, events=POLLIN}, {fd=5, events=POLLIN}, {fd=3, events=POLLIN}, {fd=7, events=POLLIN}, {fd=4, events=POLLIN}], 5, 4294967295) = 2 ([{fd=6, revents=POLLIN}, {fd=4, revents=POLLIN}]) read(6, "\3\0\0\0\0\0\0\0", 16) = 8 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 recvmsg(4, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\1$\0\0\0a(\0\0\265\0\0\0\1\1o\0(\0\0\0/org/kde"..., 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 236 write(6, "\1\0\0\0\0\0\0\0", 8) = 8 Version-Release number of selected component (if applicable): 1.3.12 How reproducible: always Steps to Reproduce: 1. install cauldron 2. run for ex kde 3. see constant 100% cpu used by applet.py Reproducible: Steps to Reproduce:
a task manager can't tell you from where this come ?
Keywords: (none) => NEEDINFO
I am sorry, but I don't really understand that. What should I post to give better sight of the issue?
This day a new sympton arose. Now not just the applet.py takes 100%, but an other python process does the same.
I have one configured printer, which is on an other box (shared from a windows)
In MCC, I have tried to change it's config (the printer configured is no longer available on my network) and CUPS says this: CUPS server error
There was an error during the CUPS operation: 'Transport endpoint is not connected'. It is just an idea, but isn't it possible that applet.py is eating up CPU while it tries to connect to a printer which can't be connected?
I have removed the printer from the system, applet.py still eats up the CPU.
there was a cups update, still valid ?
Installed all updates, rebooted my box, but sadly it is the same. I attach a small screenshot from top. If you need anything that could help in debugging please post it.
Created attachment 4402 [details] top showing the 2 faulty process
Keywords: NEEDINFO => (none)Priority: Normal => release_blockerCC: (none) => thierry.vignaud
With the latest updates, applet.py is no longer eating up CPU, but still there is an other python process which does.
Still no change with the latest updates. It is really only happening on my system?
Hardware: i586 => x86_64
python is using 100% of my processor, too. I only have Firefox and MCC running while I try to fix a "waiting for printer to become available error", which arose when I switched to Cauldron. The printer is an Epson Stylus C88+.
CC: (none) => jneri
Thank you. The latest update has allowed me to once again auto-locate my usb printer and eliminated the "waiting for printer to become available" error.
CC: (none) => olav
on my system (MGA4 64bit cauldron) there's also a pyhton process running at full load (one cpu core at 100%). I can't say which python-script is running as the "top" doesn't give me this information. Killing the process solves the issue temporarly. Maybe it's some MCC thing like checking for updates??
CC: (none) => alfaflo
No it's not. "ps awx" is your friend for getting the full script path. or "ls -ld /proc/<pid>/cwd"0
thanks for the hint. it's hp-systray which causes the high cpu load ps awx | grep python 2338 ? Rs 16:04 python /usr/bin/hp-systray -x top 2338 florian 20 0 555m 73m 37m R 100 2.4 18:14.90 python
Could you upgrade to system-config-printer-1.4.2-11 then restart your session and see if the bug is fixed?
Will do that when I got back from work.
The bug still persists. After updating everything hp-systray still eats up cpu.
CC: (none) => hhielscher
seen that it also affect users in a forums :/
Keywords: NEEDINFO => (none)Whiteboard: (none) => 4RC
i confirm that hp-systray -x causes the high cpu load my system-config-printer is the 1.4.3 bye
CC: (none) => pleny29
I have solved my pb when i have erased the package Hplip-gui bye
CC: (none) => doktor5000Summary: applet.py causes 100% CPU usage => hplip-gui causes applet.py to eat 100% CPU usageSource RPM: system-config-printer-1.3.12-6.mga3 => system-config-printer-1.3.12-6.mga3, hplip
(In reply to Florian Bauer from comment #15) > on my system (MGA4 64bit cauldron) there's also a pyhton process running at > full load (one cpu core at 100%). What printer do you use, and is it directly connected to your box? FWIW, there's a report open about a similar issue upstream: https://bugs.launchpad.net/hplip/+bug/391570 Only thing I could do is probably to disable systray icon, as this had been disabled for quite some time before (as it seems to have caused some issues in the past).
I've also uninstalled the hplip-gui to "solve" my problem. I don't have a HP printer and I - honestly - don't know what this systray-icon exactly do ;-) So I would agree to remove this package from standard cups-meta-task?!
I would rather disagree. The systray icon is very useful when it is working (of course you have to have an HP printer), similar to what hp has on windows too. Also it has features (like ink-state report) which is not shown by CUPS, besides the bug won't solve itself by just removing it from the standard CUPS meta package.
I have found the same issue on other bugtrackers: Debian, confirmed: https://bugs.launchpad.net/hplip/+bug/556368 Following them I have found the same error in xsession. So I checked on ~/.hplip/hp-systray.lock and the file was there. After removing it hp-systray starts up without errors. It also removes the file on exit. On my computer removing that file solves this problem. On the other hand I think this could happen again after a reset (so hp-systray will leave the file there).
(In reply to Tamás Hajdu from comment #27) > I have found the same issue on other bugtrackers: > Debian, confirmed: https://bugs.launchpad.net/hplip/+bug/556368 That's not Debian, that's a bug reported directly against hplip, and no response from upstream. The debian bugreport is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569976 and also no patch or solution available. I'm afraid there's nothing we can do about this. You can only add a comment on the hplip bug, ask about and update and mention that you're also affected.
Removing release_blocker status as no fix is available.
Keywords: (none) => NO_PATCH, UPSTREAMPriority: release_blocker => HighSource RPM: system-config-printer-1.3.12-6.mga3, hplip => hplipSeverity: normal => major
Whiteboard: 4RC => 4RC 4errata
Could this be another nvidia related issue? What do the problematic systems use? nvidia? KDE? I changed from nividia to noveau and this issue disappeared (dual core laptop vith nvidia quadro NVS 140, mga4 - 64bit KDE)
CC: (none) => fri
bug occured with proprietary driver module loaded (KDE). I've uninstalled hp-systray before I've switched to nouveau so I can't say if this would had solved the issue. I can test it on a netbook with intel grafix if it's interesting for developers. (But as I understood nvidia related bugs won't or can't be fixed in MGA4 so the alternative is using nouveau or switching to another distribution)
CC: (none) => dglent
I have a HP printer, do you know how i can disable the systray icon ? i saw the options to hide only but not to disable it.
simply uninstall hplip-gui
(In reply to Morgan Leijström from comment #33) > simply uninstall hplip-gui Thanks, i think it would be better to mention 'uninstall hplip-gui' in errata. https://wiki.mageia.org/en/Mageia_4_Errata#HP-Gui
(In reply to Dimitrios Glentadakis from comment #34) > (In reply to Morgan Leijström from comment #33) > > simply uninstall hplip-gui > > Thanks, i think it would be better to mention 'uninstall hplip-gui' in > errata. > https://wiki.mageia.org/en/Mageia_4_Errata#HP-Gui You can change things in the wiki, too ;)
Hi, I have happily announce that with the latest nvidia drivers for mag4 solves the problem. Now the HP GUI starts and works as expected.
Status: NEW => RESOLVEDResolution: (none) => FIXED
This issue returned again it mga4. Now it is the hp-systray applet which eats up the CPU and also with the new nvidia drivers, resume fails in 20% of the time (X restarts). Here is the Xorg's log: [ 60324.667] (EE) [ 60324.667] (EE) Backtrace: [ 60324.667] (EE) 0: /etc/X11/X (xorg_backtrace+0x3d) [0x5805dd] [ 60324.667] (EE) 1: /etc/X11/X (0x400000+0x184349) [0x584349] [ 60324.667] (EE) 2: /lib64/libpthread.so.0 (0x7f3b0ee87000+0xf720) [0x7f3b0ee96720] [ 60324.668] (EE) 3: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f3b089a8000+0x87b26) [0x7f3b08a2fb26] [ 60324.668] (EE) 4: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f3b089a8000+0x4eac27) [0x7f3b08e92c27] [ 60324.668] (EE) 5: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f3b089a8000+0x4ef0e4) [0x7f3b08e970e4] [ 60324.668] (EE) 6: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f3b089a8000+0x4fd0b2) [0x7f3b08ea50b2] [ 60324.668] (EE) 7: /usr/lib64/xorg/extra-modules/nvidia_drv.so (0x7f3b089a8000+0x4f4f81) [0x7f3b08e9cf81] [ 60324.668] (EE) 8: /etc/X11/X (xf86Wakeup+0x54a) [0x4733fa] [ 60324.668] (EE) 9: /etc/X11/X (WakeupHandler+0x6d) [0x439c7d] [ 60324.668] (EE) 10: /etc/X11/X (WaitForSomething+0x1af) [0x57db4f] [ 60324.668] (EE) 11: /etc/X11/X (0x400000+0x357b1) [0x4357b1] [ 60324.668] (EE) 12: /etc/X11/X (0x400000+0x24e9a) [0x424e9a] [ 60324.668] (EE) 13: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f3b0dcf0c85] [ 60324.671] (EE) 14: /etc/X11/X (0x400000+0x251df) [0x4251df] [ 60324.671] (EE) [ 60324.671] (EE) Segmentation fault at address 0x25 [ 60324.671] (EE) Fatal server error: [ 60324.671] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 60324.671] (EE) [ 60324.671] (EE) Please consult the The X.Org Foundation support at http://bugs.mageia.org for help. [ 60324.671] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 60324.671] (EE) [ 60327.127] (EE) Server terminated with error (1). Closing log file.
Status: RESOLVED => REOPENEDVersion: Cauldron => 4Resolution: FIXED => (none)Source RPM: hplip => hplip, nvidia
How is that X server crash or the nvidia driver and/or suspend issues related to this bug report or the hplip applet?
For first that was really strange to me too, but if you read back this thread, it somehow effects each other.
(In reply to Tamás Hajdu from comment #39) > but if you read back this thread, it somehow effects each other. There's no X crash reported in this bug, please open a separate bug for your X issues and resume problems.
That's true. Sorry for binding bugs. But still hp-systray eats up CPU.
Resolved.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED