[SOLVED] Tint2 Panel Stops Working After Recent System Upgrade

walkingstickfan · 2024-03-08 06:25:26

I performed system upgrades on my laptop and desktop computers this week. Now the Tint2 panel stops working after use for minutes or hours. I'm wondering if it's a mkinitcpio issue. I found the following under Gnome Logs on my desktop:

18:05:52 systemd-coredum: Process 647 (tint2) of user 1000 dumped core.

Stack trace of thread 647:
#0  0x000057c01f4db2f5 find_area_under_mouse (tint2 + 0x3d2f5)
#1  0x000057c01f4be216 n/a (tint2 + 0x20216)
#2  0x000057c01f4be796 handle_x_events (tint2 + 0x20796)
#3  0x000057c01f4be8f5 run_tint2_event_loop (tint2 + 0x208f5)
#4  0x000057c01f4bea35 tint2 (tint2 + 0x20a35)
#5  0x000057c01f4b10ae main (tint2 + 0x130ae)
#6  0x00007aa548443cd0 n/a (libc.so.6 + 0x25cd0)
#7  0x00007aa548443d8a __libc_start_main (libc.so.6 + 0x25d8a)
#8  0x000057c01f4b1805 _start (tint2 + 0x13805)

Stack trace of thread 661:
#0  0x00007aa54852488d syscall (libc.so.6 + 0x10688d)
#1  0x00007aa548ee2337 g_cond_wait (libglib-2.0.so.0 + 0xb3337)
#2  0x00007aa548e541b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3  0x00007aa548e5421c g_async_queue_pop (libglib-2.0.so.0 + 0x2521c)
#4  0x00007aa548b02c48 n/a (libpangoft2-1.0.so.0 + 0x8c48)
#5  0x00007aa548ebaa45 n/a (libglib-2.0.so.0 + 0x8ba45)
#6  0x00007aa5484a955a n/a (libc.so.6 + 0x8b55a)
#7  0x00007aa548526a3c n/a (libc.so.6 + 0x108a3c)
ELF object binary architecture: AMD x86-64

18:05:48 systemd-coredum: Process 19112 (electron) of user 1000 dumped core.

Stack trace of thread 19112:
#0  0x0000587a7d16fd90 n/a (electron + 0x3924d90)
#1  0x0000587a7bd802c7 n/a (electron + 0x25352c7)
#2  0x0000587a7bc19767 n/a (electron + 0x23ce767)
#3  0x0000587a7bccc07c n/a (electron + 0x248107c)
#4  0x0000587a7ea8731e n/a (electron + 0x523c31e)
#5  0x0000587a7e49b2e0 n/a (electron + 0x4c502e0)
#6  0x0000587a7e1b931b n/a (electron + 0x496e31b)
#7  0x0000587a7e1b9048 n/a (electron + 0x496e048)
#8  0x0000587a7f4b89c0 n/a (electron + 0x5c6d9c0)
#9  0x0000587a7f49db27 n/a (electron + 0x5c52b27)
#10 0x0000587a7f4544f5 n/a (electron + 0x5c094f5)
#11 0x0000587a7f48e4ac n/a (electron + 0x5c434ac)
#12 0x0000587a7f488c2c n/a (electron + 0x5c3dc2c)
#13 0x0000587a7f47f6fa n/a (electron + 0x5c346fa)
#14 0x0000587a7f485e5a n/a (electron + 0x5c3ae5a)
#15 0x0000587a7e9b86e9 n/a (electron + 0x516d6e9)
#16 0x0000587a7e9b9024 n/a (electron + 0x516e024)
#17 0x0000587a7e9b7b4d n/a (electron + 0x516cb4d)
#18 0x0000587a7e9b7bbe n/a (electron + 0x516cbbe)
#19 0x0000587a7e9b7766 n/a (electron + 0x516c766)
#20 0x0000587a7beffb59 n/a (electron + 0x26b4b59)
#21 0x0000587a7befceb6 n/a (electron + 0x26b1eb6)
#22 0x0000587a7befcfb0 n/a (electron + 0x26b1fb0)
#23 0x0000587a7bc08468 n/a (electron + 0x23bd468)
#24 0x000073e7c17c4cd0 n/a (libc.so.6 + 0x25cd0)
#25 0x000073e7c17c4d8a __libc_start_main (libc.so.6 + 0x25d8a)
#26 0x0000587a7b80b02a _start (electron + 0x1fc002a)

Stack trace of thread 19117:
#0  0x000073e7c189a0bf __poll (libc.so.6 + 0xfb0bf)
#1  0x0000587a7eb64af0 n/a (electron + 0x5319af0)
#2  0x0000587a7f4ce3d5 n/a (electron + 0x5c833d5)
#3  0x000073e7c182a55a n/a (libc.so.6 + 0x8b55a)
#4  0x000073e7c18a7a3c n/a (libc.so.6 + 0x108a3c)

Stack trace of thread 19158:
#0  0x000073e7c18a588d syscall (libc.so.6 + 0x10688d)
#1  0x000073e7c2d05337 g_cond_wait (libglib-2.0.so.0 + 0xb3337)
#2  0x000073e7c2c771b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3  0x000073e7c2c7721c g_async_queue_pop (libglib-2.0.so.0 + 0x2521c)
#4  0x000073e7c1462c48 n/a (libpangoft2-1.0.so.0 + 0x8c48)
#5  0x000073e7c2cdda45 n/a (libglib-2.0.so.0 + 0x8ba45)
#6  0x000073e7c182a55a n/a (libc.so.6 + 0x8b55a)
#7  0x000073e7c18a7a3c n/a (libc.so.6 + 0x108a3c)

Stack trace of thread 19123:
#0  0x000073e7c1890ec7 wait4 (libc.so.6 + 0xf1ec7)
#1  0x0000587a7f4e9020 n/a (electron + 0x5c9e020)
#2  0x0000587a7f4e9980 n/a (electron + 0x5c9e980)
#3  0x0000587a7f4ce3d5 n/a (electron + 0x5c833d5)
#4  0x000073e7c182a55a n/a (libc.so.6 + 0x8b55a)
#5  0x000073e7c18a7a3c n/a (libc.so.6 + 0x108a3c)

Stack trace of thread 19135:
#0  0x0000000000000000 n/a (n/a + 0x0)
#1  0x00007ffdc8e1f440 n/a (n/a + 0x0)
#2  0x000002ec02de9180 n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

Last edited by walkingstickfan (2024-03-08 17:18:12)

8472 · 2024-03-08 06:33:39

check this out: https://gitlab.archlinux.org/archlinux/ … -/issues/3 , whether you aren't having similar symptomps because of the conky as I do?

walkingstickfan · 2024-03-08 07:01:22

I'll try downgrading and see if that helps. Thank you for your response.

Reported upstream as well and it doesn't look like the issue will be fixed very soon. Developer thought the issue might be fixed with 1.19.8, but others report the issue still exists.

Last edited by walkingstickfan (2024-03-08 17:17:24)

Mr Green · 2024-03-20 11:06:23

I am having problems with tint2 as well.

Running:

Tint2 17.0.2-3

Conky 1.19.7-2

Tint2 will stop working, if run from a terminal I simply get segmentation fault error.

From thread am assuming Conky is the issue....

EDIT changing conky setting own_window to false seems to help.

Last edited by Mr Green (2024-03-20 12:15:59)

Lineage_of_roots · 2024-04-03 16:05:26

Hi everyone. I have solved this issue (as good as it gets for now). I have it posted elsewhere as well and hope it works with conky issues elsewhere as well.
The problem isn't exactly with Conky because it's Tint2 that's crashing (from what I have gathered).
This fix is only for Tint2 crashing, Conky is working fine for me.

This line will fix the problem int tint2 (I am sure there are more efficient fixes, but this hack is working fine for me)

if((e->type==4 || e->type==5 || e->type==6) && e->xproperty.window==server.root_win)
return;

Insert it after line 420 in main.c (source of tint2 from github) to modify the handle_x_event function.

You will have to ofcourse compile and install tint2 again.

I hope it helps

As for the explanation of the problem and fix (I will try my best here)

For whatever reason that I have not fully investigated yet, hovering or clicking on Conky on your desktop triggers a certain kind of event in tint2 which gets poorly handled.

Normally in tint2 the Desktop events are handled fine as they have a different "type" assigned to them, but conky triggers them with type 4 or 5 or 6 (hover, press and release) and window id of the root window. The segfault happens when a null panel is returned and the event handler tries to iterate on it.

My code will make tint2 ignore these events involving conky

My suspicion is that the real problem might be elsewhere like in Conky or Xlib because other widgets on my desktop don't trigger the event in the same way. I have a weather widget and notes widget on my desktop that don't cause tint2 to crash.

This may also have something to do with the settings in conkyrc, mine has the settings

own_window yes
own_window_type 'desktop'

For various reasons like appearance tastes, my conky rc settings let conky blend into the desktop and doesn't show up in the taskbar.
Sine I don't want to change my conky appearance preferences, this will patch the problems with tint2

Let me know if it works out for you guys.

Thanks

Arch Linux

#1 2024-03-08 06:25:26

[SOLVED] Tint2 Panel Stops Working After Recent System Upgrade

#2 2024-03-08 06:33:39

Re: [SOLVED] Tint2 Panel Stops Working After Recent System Upgrade

#3 2024-03-08 07:01:22

Re: [SOLVED] Tint2 Panel Stops Working After Recent System Upgrade

#4 2024-03-20 11:06:23

Re: [SOLVED] Tint2 Panel Stops Working After Recent System Upgrade

#5 2024-04-03 16:05:26

Re: [SOLVED] Tint2 Panel Stops Working After Recent System Upgrade

Board footer