TINT2 stoped working on some events

Marian · March 8, 2026, 11:36am

mar 08 12:31:14 computer1 kernel: traps: tint2[9465] general protection fault ip:55f4620604c5 sp:7ffd72885090 error:0 in tint2[55f46204e000+39000]
mar 08 12:31:14 computer1 systemd-coredump[16320]: Process 9465 (tint2) of user 1000 terminated abnormally with signal 11/SEGV, processing…
mar 08 12:31:14 computer1 systemd[1]: Started Process Core Dump (PID 16320/UID 0).
mar 08 12:31:14 computer1 systemd-coredump[16322]: [🡕] Process 9465 (tint2) of user 1000 dumped core.                                         Stack trace of thread 9465:
                                         #0  0x000055f4620604c5 on_change_systray (/usr/bin/tint2 + 0x254c5)
                                         #1  0x000055f46206085d resize_systray (/usr/bin/tint2 + 0x2585d)
                                         #2  0x000055f462072d40 relayout_fixed (/usr/bin/tint2 + 0x37d40)
                                         #3  0x000055f462072cf1 relayout_fixed (/usr/bin/tint2 + 0x37cf1)
                                         #4  0x000055f462072eb9 relayout (/usr/bin/tint2 + 0x37eb9)
                                         #5  0x000055f46205680a render_panel (/usr/bin/tint2 + 0x1b80a)
                                         #6  0x000055f46205a1f7 handle_panel_refresh (/usr/bin/tint2 + 0x1f1f7)
                                         #7  0x000055f46205a6ef run_tint2_event_loop (/usr/bin/tint2 + 0x1f6ef)
                                         #8  0x000055f46205a76f tint2 (/usr/bin/tint2 + 0x1f76f)
                                         #9  0x000055f46204e095 main (/usr/bin/tint2 + 0x13095)
                                         #10 0x00007f7428bfe6c1 n/a (libc.so.6 + 0x276c1)
                                         #11 0x00007f7428bfe7f9 __libc_start_main (libc.so.6 + 0x277f9)
                                         #12 0x000055f46204e525 _start (/usr/bin/tint2 + 0x13525)
                                         
                                         Stack trace of thread 9466:
                                         #0  0x00007f7428cef06d syscall (libc.so.6 + 0x11806d)
                                         #1  0x00007f74295fba2e g_cond_wait (libglib-2.0.so.0 + 0x8ca2e)
                                         #2  0x00007f742959522d n/a (libglib-2.0.so.0 + 0x2622d)
                                         #3  0x00007f742959529d g_async_queue_pop (libglib-2.0.so.0 + 0x2629d)
                                         #4  0x00007f7428b9a51c n/a (libpangoft2-1.0.so.0 + 0xc51c)
                                         #5  0x00007f742960513c n/a (libglib-2.0.so.0 + 0x9613c)
                                         #6  0x00007f7428c6d97a n/a (libc.so.6 + 0x9697a)
                                         #7  0x00007f7428cf12bc n/a (libc.so.6 + 0x11a2bc)
                                         ELF object binary architecture: AMD x86-64
mar 08 12:31:14 computer1 systemd[1]: systemd-coredump@1-4097-16320-0.service: Deactivated successfully.

This happens after start of Remote Desktop Manager (Devolutions inc.)

After upgrade to 2026.02

dmesg: 

[   78.826456] traps: tint2[3875] general protection fault ip:5646f93874c5 sp:7ffcfbc6fb80 error:0 in tint2[5646f9375000+39000]
[  370.909573] traps: tint2[9465] general protection fault ip:55f4620604c5 sp:7ffd72885090 error:0 in tint2[55f46204e000+39000]

napcok · March 8, 2026, 12:17pm

Thanks for reporting, I will try to reproduce and look at this.

napcok · March 8, 2026, 7:52pm

Hi @Marian, can you try the new tint2 build?

https://repo.maboxlinux.org/testing/x86_64/tint2-17.0.2-6-x86_64.pkg.tar.zst

Please let me know if it fixes the problem for you.

M0nst3r · March 9, 2026, 1:31pm

Hi @napcok .

What a coincidence, I recently had several random tint2 bar crashes in both main PC and VM.

Regards.

napcok · March 9, 2026, 1:44pm

Hi,

I’m unable to reproduce the errors, so I have no basis for commenting on this matter.
Tint2 works fine for me, both the one from the Mabox repo and this new build with a few Gentoo patches added.

Therefore, I’m asking for your feedback.
In particular, please let me know if the new build fixes the tint2 errors you are experiencing.
New build is here:

https://repo.maboxlinux.org/testing/x86_64/tint2-17.0.2-6-x86_64.pkg.tar.zst

M0nst3r · March 9, 2026, 3:27pm

In the meantime, here are my errors. It looks the same as @Marian ‘s:

kernel: traps: tint2[1321] general protection fault ip:55b8d255f4c5 sp:7ffd0f9cadd0 error:0 in tint2[254c5,55b8d254d000+39000]
systemd-coredump[7689]: Process 1321 (tint2) of user 1000 terminated abnormally with signal 11/SEGV, processing…
systemd-coredump[7707]: Process 1321 (tint2) of user 1000 dumped core.


---

kernel: traps: tint2[1312] general protection fault ip:560f6f3784c5 sp:7ffd64be5c20 error:0 in tint2[254c5,560f6f366000+39000]
systemd-coredump[91633]: Process 1312 (tint2) of user 1000 terminated abnormally with signal 11/SEGV, processing…
systemd-coredump[91651]: Process 1312 (tint2) of user 1000 dumped core.

Marian · March 9, 2026, 8:01pm

17.0.2-6-x86_64 makes similar effect:

run tint2 in terminal:
tint2
tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes
tint2: xRandr: Found crtc's: 3
tint2: xRandr: Linking output eDP-1 with crtc 0, resolution 1920x1080, DPI 157
tint2: xRandr: Linking output DP-2-1 with crtc 1, resolution 1920x1200, DPI 94
tint2: xRandr: Linking output DP-2-2 with crtc 2, resolution 1920x1080, DPI 102
tint2: xsettings: Net/IconThemeName = Gruvbox-Material-Dark
tint2: Loading config file: /home/marian/.config/tint2/tint2rc
tint2: real transparency off.... depth: 24
tint2: panel items: PPPPPPL:TESBCPP
tint2: Systray composited rendering on
tint2: Found power device BAT1
Found battery "BAT1"
tint2: Found power device ucsi-source-psy-USBC000:001
tint2: Found power device hidpp_battery_3
tint2: /build/tint2/src/tint2/src/battery/linux.c:142: read failed for /sys/class/power_supply/hidpp_battery_3/present
tint2: Failed to initialize battery "hidpp_battery_3"
tint2: Found power device BAT0
Found battery "BAT0"
tint2: Found power device AC
Found mains "AC"
tint2: nb monitors 1, nb monitors used 1, nb desktops 2
tint2: panel 1 uses scale 1 
tint2: Loading icon theme cache...
tint2: Could not open file /home/marian/.local/share/applications/calamares.desktop
Creating executor '~/.config/tint2/scripts/volumettf' with monitor -1 for panel on monitor 0
tint2: Kernel uevent interface initialized...
tint2: Could not find icon '(null)', using default.
tint2: systray window 6291476
tint2: systray started
Icon path not found in cache: theme = Papirus, icon = system-shutdown, size = 23
tint2: Loading icon theme Papirus:
tint2:  'Papirus',tint2:  'breeze',tint2:  'hicolor',tint2: 
Adding icon path to cache: theme = Papirus, icon = system-shutdown, size = 23, path = /usr/share/icons/Papirus/24x24/actions/system-shutdown.svg
Icon path not found in cache: theme = Papirus, icon = arrow-right, size = 16
Adding icon path to cache: theme = Papirus, icon = arrow-right, size = 16, path = /usr/share/icons/Papirus/16x16/actions/arrow-right.svg
add_icon: 39846129 (), pid 3670, visual 0x55658046b140, colormap 39845896, depth 32, width 22, height 22

-----------now starting remote desktop manager

tint2: systray: error code 9
tint2: systray: error code 9
tint2: remove_icon: 27262979 (geany)
add_icon: 75497535 (RemoteDesktopManager), pid 65531, visual 0x55658046b140, colormap 75497534, depth 32, width 1, height 1
systray 823: cannot embed icon for window 75497535 (RemoteDesktopManager) parent 6292501 pid 65531
tint2: remove_icon: 75497535 (RemoteDesktopManager)
Naruszenie ochrony pamięci(zrzut pamięci) tint2

I found something interesting. Tint2 is crushing only when RDM is opening on second monitor.
If I move RDM window to first monitor, close RDM and open it again → tint2 is ok.
If I move RDM to second monitor, close RDM and then start tint2 and RDM → tint2 is crushing.

Strange.

napcok · March 9, 2026, 8:32pm

I installed this RDM from AUR, but I can not reproduce this crash.

Maybe because I use only one monitor.

napcok · March 9, 2026, 8:36pm

@Marian, Maybe try to disable systray icon… as workaround

Marian · March 9, 2026, 10:35pm

Disabled systray icon and … nothing changed. Upgrade of RDM is an idea.
RDM crushing tint2 randomly, 20% works ok. (20 starts of 100 works without crushing). Monitor number has nothing to do with it.