Closed GoogleCodeExporter closed 8 years ago
Do you use some kind of compositing manager (i.e. do you have real transparency
or fake transparency)? You can see on tint2 startup on the commandline the
output, whether you're using real transparency...
How do you start tint2 in the beginning (with gnome autostart?)?
This seems like a bad combination of your graphics driver and xorg-server
version...
Original comment by Andreas.Fink85
on 24 Sep 2010 at 6:03
I use compiz, with some sort of transparency. I start tint2 in my startup
applications. But everything worked fine with version 0.7.1 Problems only
started when I upgraded.
Original comment by amad...@gmail.com
on 28 Sep 2010 at 5:43
Yes, and between 0.7 and 0.11 we've changed to use real transparency if a
composite manager is available. And with real transparency the drawing of
systemtray icons is completely different than with fake transparency. We've had
already once the problem with this kind of behaviour, and actually I've thought
that it was fixed the last time, but maybe we've introduced a change somewhere
which brought the problem back...
If you can upgrade your xorg-server then try first this if this does not help,
maybe you can come to #tint2 on irc to discuss the problem there (but then you
need to be able to compile from sources, coz I cannot reproduce the problem
with my graphic card and my xorg-server version)
Original comment by Andreas.Fink85
on 28 Sep 2010 at 11:45
Sorry it took me a while to get back to this, but I think I have solved the
problem. It seems that adding a sleep delay to my tint2 startup command has
everything loading properly. The command I'm using is sh -c "sleep 5; exec
tint2". Since this delay has fixed the problem I'm not sure if that confirms or
rules out this being a graphics driver/xorg-server problem. Hopefully this info
will help anyone else experiencing the same thing.
Original comment by amad...@gmail.com
on 12 Oct 2010 at 12:51
actually I changed some stuff with systray rendering. Can you try the newest
svn version without any delay and look if it works?
Original comment by Andreas.Fink85
on 14 Oct 2010 at 5:16
Original comment by Andreas.Fink85
on 2 Dec 2010 at 7:37
Just to say that I've experienced the same symptoms with Compiz and Tint2,
using both lxsession-lite and gnome-session. I worked around the problem under
gnome-session by firing up tint2 and compiz from .desktop files in
/etc/xdg/autostart with the key X-GNOME-Autostart-Phase=Initialization set in
both cases. The ensures the DE is in place before nm-applet et al fire up...
It would be nice if tint2 supported GNOMES XDG extensions properly
(http://live.gnome.org/SessionManagement/NewGnomeSession) via XSMP signalling.
That way, X-GNOME-Autostart-Phase=panel and X-GNOME-Provides=panel could be set
to better integrate Tint2 as a GNOME-panel replacement. In which case. if the
GConf key /desktop/gnome/session/required_components/panel was also set to
Tint2, it would fully integrated into the DE... ;)
Original comment by nat.hu...@gmail.com
on 9 Dec 2010 at 2:17
I've just upgraded to latest SVN version and it works fine for me now. All
icons appear consistently when running Tint2 from a .desktop file with the
X-GNOME-Autostart-Phase key set to "Application" (i.e. same phase as nm-applet
etc).
Thank you and apologies for the convolution in the last comment ;D I still
think it'd be cool if Tint2 integrated with GNOMEs session management more
gracefully, though! :D
Original comment by nat.hu...@gmail.com
on 9 Dec 2010 at 2:34
Original comment by mrovi9...@gmail.com
on 1 Feb 2015 at 5:47
Original issue reported on code.google.com by
amad...@gmail.com
on 24 Sep 2010 at 3:04