The tint2 crashes when it gets new tray icon since upgrading glib to 2.76.0. tint2: remove_icon: 35651590 () Thread 1 "tint2" received signal SIGSEGV, Segmentation fault. 0x0000555555577a2e in handle_x_event (e=0x7fffffffd4b0) at /var/portage/tmp/portage/x11-misc/tint2-17.1.3/work/tint2-v17.1.3/src/main.c:539 539 /var/portage/tmp/portage/x11-misc/tint2-17.1.3/work/tint2-v17.1.3/src/main.c: No such file or directory. (gdb) bt #0 0x0000555555577a2e in handle_x_event (e=0x7fffffffd4b0) at /var/portage/tmp/portage/x11-misc/tint2-17.1.3/work/tint2-v17.1.3/src/main.c:539 #1 0x0000555555577d6a in handle_x_events () at /var/portage/tmp/portage/x11-misc/tint2-17.1.3/work/tint2-v17.1.3/src/main.c:603 #2 0x00005555555788e7 in run_tint2_event_loop () at /var/portage/tmp/portage/x11-misc/tint2-17.1.3/work/tint2-v17.1.3/src/main.c:781 #3 0x0000555555578a98 in tint2 (argc=1, argv=0x7fffffffdfb8, restart=0x7fffffffde94) at /var/portage/tmp/portage/x11-misc/tint2-17.1.3/work/tint2-v17.1.3/src/main.c:824 #4 0x0000555555578c11 in main (argc=1, argv=0x7fffffffdfb8) at /var/portage/tmp/portage/x11-misc/tint2-17.1.3/work/tint2-v17.1.3/src/main.c:871 (gdb) Seems like one of many packages that are broken with new glib, same goes for openbox.
With glib-2.76.0 and tint2-17.1.3 Using pidgin-2.14.12 client, if pidgin is configured to put its icon in the tint2 system bar,closing pidgin breaks tint2 disappearing and leaving openbox without tint2. Fixed it by UD to the stable version of tint2-17.0.2. But then I had problems with mcabber and decided UD to glib-2.74.6 and a # emerge -euvaDN @world
Downgrading glib might lead to catastrophic system failure if you happen to rebuild other things with the new glib headers, you would be surprised how many things pulls in libglib via other dependencies, including openbox. Since tint2 is abandoned upstream I will most likely stop using it and switch to polybar or something similar.
For what it is worth. After trying out a bunch of potential replacements I've stayed longer with xfce4-panel with dock disabled. It even has nice GUI for configuration. In my box it did not pull in too many dependencies (I use plain Openbox).
I have experienced crashes with tint2 since March 2023, which indicates it is likely due to >=dev-libs/glib-2.76.0. The crashes that I see are when I get a new Thunderbird notification and try to remove the icon or notification pop-up. It doesn't happen all the time, but with some regularity. Just recently, it looks like a patched version of tint2 has been put into the Mabox Linux repositories: https://forum.maboxlinux.org/t/tint2-panel-started-disappearing-after-system-upgrade/1383/5 We may want to look into that patch in Gentoo.
Could you try dig up what the actual patch used is?
I posted on the Mabox Linux forum asking for details about the patch, but haven't yet received a response. However, it's possible that this is the referenced patch: https://bbs.archlinux.org/viewtopic.php?pid=2090946#p2090946
Mabox Linux Developer, napcok, confirmed the patch that I posted yesterday is the one that they have applied: https://forum.maboxlinux.org/t/tint2-panel-started-disappearing-after-system-upgrade/1383/15 and the corresponding patch from the Arch Linux forum: https://bbs.archlinux.org/viewtopic.php?pid=2090946#p2090946 Note that in Mabox Linux, they are using the 17.0.2 release (from o9000 on GitLab) instead of the forked 17.1.3 release (from Nikita Zlobin on GitLab) as the latter "seems very buggy".
Created attachment 864444 [details, diff] Patch from the Arch Linux forum for tint2-17.0.2 with glib-2.76
Created attachment 864742 [details, diff] Patch for 17.1.3 Analogous patch for 17.1.3 of uevent.c, plus the same kind of change in main.c handle_x_event(), which was the line identified in the stacktrace at https://gitlab.com/nick87720z/tint2/-/issues/4 Not sure if the main.c change is needed, since I had tried various versions of that without any positive result, but have been running with both these for a day now, and couldn't manage to force a crash.
I personally think that we go back to using the 17.0.2 release (from o9000 on GitLab) instead of the forked 17.1.3 release (from Nikita Zlobin on GitLab). This crash happens multiple times daily, so going back to the 17.0.2 release and applying this the applicable patch would be very helpful. Please let me know if you would like me to do any further testing. Thanks again for your time. Cheers, Nathan Zachary
FWIW I've been running the 17.1.3 patch I posted for almost 3 months now, with no crash or other unexpected behaviour.
(In reply to Arve Barsnes from comment #11) > FWIW I've been running the 17.1.3 patch I posted for almost 3 months now, > with no crash or other unexpected behaviour. Thank you for sharing your experience with the 17.1.3 patch as well. I wouldn't mind getting that one into the tree then either. It would just be nice to have a proper version available to all users.
