On 09.06.2015 14:56, Jan Engelhardt wrote:
On Tuesday 2015-06-09 14:39, Freek de Kruijf wrote:
Op dinsdag 9 juni 2015 12:10:57 schreef Roger Whittaker:
On Tue, Jun 09, 2015 at 01:05:23PM +0200, Knurpht - Gertjan Lettink wrote:
hplip-systray doesn't work with plasma5's systemtray. To avoid it from even trying copy the /etc/xdg/autostart/hplip-systray.desktop to ~/.config/autostart, then change the Exec= to "echo something" or whatever.
If I dismiss the error message at startup and then run
hp-systray &
it behaves as expected.
I also have that behavior, so it works with systemtray of plasma5.
Can I change the Exec in "sleep 10;hp-systray -x"
As Andreas said: a sleep won't fix it. Who says that after 10 seconds, the conditions are right enough for hp-systray to succeed launching?
...also note the difference between "hp-systray" and "hp-systray -x".
Agreed that a sleep won't be a true solution for the underlying problem (which probably would require some sort of dependency control). However, for the individual user it might be a sufficient workaround if a startup delay raises the success rate to 90% or more. For such cases, I tend to create a small shell script that handles the delay, and specify that in the *.desktop file. On a side note: this fails, however, if the application is started by session management and not by some autostart entry (as currently happens for me with kontact & plasma5 - annoying, but I'll live with it until kontact goes KDE Applications 15...). -- Cahn's Axiom: When all else fails, read the instructions. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org