Closed GoogleCodeExporter closed 9 years ago
I've dug into this a bit, but being new to xlib, I'm a bit lost. I've added a
ton of debug messages to tint.c and compared them with the output of another
systray app (stalonetray). Using tktray1.3.9 to trigger systray icon insertion,
I've compared the output of tint2 and stalonetray. One obvious thing that I've
noticed is that tint2 never seems to receive the _NET_SYSTEM_TRAY_OPCODE
messages that stalonetray does. The moment I run the make test from tktray
(which inserts an icon in the tray) I see a flurry of _NET_SYSTEM_TRAY_OPCODE
messages register in stalonetray. Tint2, on the other hand, doesn't seem to
register any of them.
I've run both tint2 and stalonetray at the same time and in isolation with
similar results.
Anybody have any ideas? Or even suggestions into how to better troubleshoot
this? I have no problem debugging the code myself.
On a side note, the system tray was /definitely/ working a few weeks ago when I
first installed tint2. Since then, I've done a number of package changes to do
my best to remove all the superfluous packages of KDE from my system. Is it
possible there are some libraries that are needed that might be missing?
Original comment by btmcgu...@gmail.com
on 18 Jul 2011 at 3:41
Running two applications which offer a system tray does not work anyway, as
there is only one system tray allowed to run.
I tried your tint2rc, and I have to say, that it works here with openbox. It's
strange that you're not getting the systemtray to work.
You could try to adapt your tint2rc to the new 'panel_items' config option (see
here: http://code.google.com/p/tint2/wiki/Configure#Panel), however it should
be automatically recognized, since you have systray=1 in config file.
Otherwise you could try to start debugging in the file src/systray/systraybar.c
in the function init_systray() (and than in any function that's called from
there).
Also the function add_icon (same file) is called each time an icon should be
added to the systray, so a debugging message there could help too ;)
Original comment by Andreas.Fink85
on 18 Jul 2011 at 6:15
After all the nonsense of debugging it along side stalonetray, I realized I
still had a few kde packages installed, which I removed, and everything worked
fine. My guess is that the kde systray was somehow interfering with tint2. Not
sure why stalonetray was registering the opcodes, though. And I didn't think
any kde systray was running... Regardless, tint2 works beautifully now. Great
app!
Original comment by btmcgu...@gmail.com
on 28 Jul 2011 at 6:28
This issue can be closed.
Original comment by btmcgu...@gmail.com
on 28 Jul 2011 at 6:29
Original comment by goo...@craigoakes.com
on 18 Oct 2011 at 3:25
Original issue reported on code.google.com by
btmcgu...@gmail.com
on 16 Jul 2011 at 8:07Attachments: