* Brüns, Stefan <Stefan.Bruens@rwth-aachen.de> [06-09-15 15:42]:
On Tuesday, June 09, 2015 13:12:24 Patrick Shanahan wrote:
* Brüns, Stefan <Stefan.Bruens@rwth-aachen.de> [06-09-15 12:22]:
On Tuesday, June 09, 2015 12:32:31 Freek de Kruijf wrote:
After updating hplip and starting a KDE session I get a warning message from hplip that the system tray is not available. After searching for a solution to this problem I found that starting hplip-systray is too early. So a sleep of a few seconds before this application runs will solve the problem.
However I can't find where this program gets started.
Any suggestion?
hplip uses the Qt4 python bindings. Stock QSystemTrayIcon does not support StatusNotifierItem, but this can be changed by installing sni-qt.
hplip-systray polls for the availability of the Tray for 60 seconds and exits afterwards.
Actually, it should just start, QSystemTrayIcon handles the delayed start of the system tray by itself.
I also see this "anomaly" on three of my four local boxes, all with sni-qt installed and like settings. One desktop work and two laps and another dt fail, complaining missing setting-tray.
All systems are Tw.
Hm, there may be a race condition in the bus startup, tray startup and hp- systray startup.
Does it also happen if you invoke hp-systray after the desktop has started?
No, there appear to be at least two pids of hp-systray -x after the failure to find the system tray. I kill those processes but it is not required and issue "hp-systray -x" and have normal and expected function.
You can trace the hp-systray startup by copying the attached hplip- systray.desktop to your ~/.config/autostart/ directory. It will dump the relevant dbus messages to /tmp/dbus_sni_$pid.out
Kill the dbus-monitor process after your session has started: killall dbus-monitor
The added tracing may change the timing, thus the trace might be useless.
I have attached a trace of the hplip-systray startup. You can see the folllowing:
The unique name :1.2707 gets a new owner as result of a "Hello" method call (NameOwnerChanged, [:1.2707, "", :1.2707] The requester is informed of its aquired name (Hello -> ":1.2707")
:1.2707 adds a match for the StatusNotifierHostRegistered signal :1.2707 asks the bus for the StatusNotifierWatcher owner :1.2707 asks org.kde.StatusNotifierItem to Register a new StatusNotifierItem
I will do this on one of the lap tops and post a link. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org