The real issue here is that your systray doesn't show when starting tint... Never had that behavior.Killing tint2 and running it again should work, but I suggest you look into the autohide option for a more elegant solution.Tint2 wiki on google code
dura wrote:Some conky edits (namely borrowing a .conkyrc from somewhere) can occasionally stop tint2 running I've found. Just stick tint2 & at the bottom of your autostart.sh and see if that makes a difference.The question is, how is conky setup related to tint2. What does it changes, that is essential for tint2 startup?
I do not like breaking things, but there is going to be a problem for existing Statler tint2 users when the latest tint2 package is included in the Statler repository. I am writing this as a kind of preemptive warning, so hopefully people will be aware of the issue.Basically, the tint2 config file which shipped with the alpha releases does not contain a `panel_items` variable.
What autostart script? I also have a dual screen setup but never used any autostart script, and it's working just fine. It's easier for others to help you if you give them as much info as possible. Maybe theres a mistake in your tint2rc for instance.
Whenever I close the lid on my laptop and reopen it, the tint2 system tray moves one icon's space to the left, drifting away from the right edge of the screen. Restarting tint2 fixes the issue. Any ideas what might cause this? One (hacky) fix would be to restart tint2 when I resume. If I went this route, what's a good way to respond to the resume event?