https://bugzilla.novell.com/show_bug.cgi?id=729235 https://bugzilla.novell.com/show_bug.cgi?id=729235#c2 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |UPSTREAM Summary|hplip uses 100% CPU |hplip: hp-systray uses 100% | |CPU --- Comment #2 from Johannes Meixner <jsmeix@suse.com> 2011-11-09 15:32:43 UTC --- It never happened for me (i.e. I cannot reproduce it). We have a /usr/bin/hp-systray.wrapper which is called by the desktop magic via "Exec=hp-systray.wrapper" in /etc/xdg/autostart/hplip-systray.desktop but as far as I can imagine this cannot be the reason for 100% CPU usage for the process "python /usr/bin/hp-systray". Therefore there should be better workarounds than to deinstall HPLIP: Either try out if it helps to remove /etc/xdg/autostart/hplip-systray.desktop so that hp-systray is no longer started automatically during desktop startup (starting hp-toolbox starts hp-systray automatically) or try out if it helps to enlarge the sleep time e.g. to "sleep 30" in /usr/bin/hp-systray.wrapper to give the desktop stuff more time to start up or try out if it helps to move the /usr/bin/hp-systray away so that it can no longer be started at all. The HPLIP printer and scanner drivers should not need a running hp-systray so that plain printing and scanning should work even without a running hp-systray. Only the hp-toolbox may require a running hp-systray (see above). Very likely this issue is not caused by the openSUSE distribution efforts of the HPLIP software so that the responsibility for this issue is upstream, see https://bugzilla.novell.com/page.cgi?id=fields.html#status Accordingly I close it as "upstream". Please report the issue directly to HPLIP upstream via http://hplipopensource.com/hplip-web/support.html Please post an URL of the HPLIP upstream bug report here as reference. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.