You are not logged in.
Pages: 1
if I start wpa_gui with settings/sessions/autostart is seems to be starting before the systray has had chance to start ?
even with the -t parameter (start in tray) it starts as a window
using session autostart I now run a simple script
if I straight open wpa_gui (with -t) the same (undesired) behaviour happens
however if I sleep first (for 4 seconds chosen arbitrarily) then it starts in the system tray as expected / required
hence my current theory that its getting started before the systray - its hard to tell its a very new machine on a fast ssd and everything just starts almost instantly from login... !
I was thinking of doing something lame like sleeping/polling the output of ps to find if the systray has started, but there is probably (i'm guessing) a better way....
Offline
I was thinking of doing something lame like sleeping/polling the output of ps to find if the systray has started, but there is probably (i'm guessing) a better way....
Probably best delay the startup.
There exists this bug report.
Please remember to mark your thread [SOLVED] to make it easier for others to find
--- How To Ask For Help | FAQ | Developer Wiki | Community | Contribute ---
Offline
I do wonder if panel, systray shouldn't get priority...
Offline
Pages: 1
[ Generated in 0.008 seconds, 7 queries executed - Memory usage: 523.6 KiB (Peak: 531.7 KiB) ]