https://bugzilla.novell.com/show_bug.cgi?id=649280 https://bugzilla.novell.com/show_bug.cgi?id=649280#c8 Johannes Meixner <jsmeix@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|hp-systray should not run |hp-systray should not be |if no matching print queue |started at all if no |exists |matching print queue exists --- Comment #8 from Johannes Meixner <jsmeix@novell.com> 2010-10-27 13:19:10 UTC --- The actual issue is not that hp-systray is running when no matching print queue exists because it exits in this case and the question in comment #4 if there is a special reason why upstream likes to run hp-systray in any case is answered: There is no such reason. The actual issue is that hp-systray should not be started at all if no matching print queue exists because the plain startup of hp-systray with all its Python stuff needs disk-IO resources which delays the desktop start up. I.e. the built-in test in hp-systray whether or not a matching print queue exists does not help in this case. Instead a less resource-consuming test must be used to increase desktop startup speed and therefore I will use /usr/bin/hp-systray.wrapper -- 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.