Arch Linux

strammer

Member

Registered: 2024-12-22

Posts: 1

Tixati causes segmentation fault

Tixati recently started causing segmentation faults upon opening the application without any apparent change that caused this. The GUI will open and crash as soon as I can start clicking. Once in a blue moon, Tixati does not crash.
I suspect an update may have caused this change but I don't know how verify this. Only the latest version is available on the Tixati website.

The journal reads:

дек 22 16:14:44 pc systemd-coredump[32993]: Process 32351 (tixati) of user 1000 terminated abnormally with signal 11/SEGV, processing...
дек 22 16:14:44 pc systemd[1]: Created slice Slice /system/systemd-coredump.
дек 22 16:14:44 pc systemd[1]: Started Process Core Dump (PID 32993/UID 0).
дек 22 16:14:46 pc systemd-coredump[32994]: [?] Process 32351 (tixati) of user 1000 dumped core.

                                               Stack trace of thread 32351:
                                               #0  0x000079ff14810e96 n/a (libgtk-3.so.0 + 0x410e96)
                                               #1  0x000079ff14dd9290 n/a (libgdk-3.so.0 + 0x7b290)
                                               #2  0x000079ff14de1041 n/a (libgdk-3.so.0 + 0x83041)
                                               #3  0x000079ff14d8268b gdk_display_get_event (libgdk-3.so.0 + 0x2468b)
                                               #4  0x000079ff14de1810 n/a (libgdk-3.so.0 + 0x83810)
                                               #5  0x000079ff150de559 n/a (libglib-2.0.so.0 + 0x5d559)
                                               #6  0x000079ff15141257 n/a (libglib-2.0.so.0 + 0xc0257)
                                               #7  0x000079ff150df287 g_main_loop_run (libglib-2.0.so.0 + 0x5e287)
                                               #8  0x000079ff145e4ebf gtk_main (libgtk-3.so.0 + 0x1e4ebf)
                                               #9  0x000000000081d978 n/a (n/a + 0x0)
                                               ELF object binary architecture: AMD x86-64
дек 22 16:14:46 pc systemd[1]: systemd-coredump@0-32993-0.service: Deactivated successfully.
дек 22 16:14:46 pc systemd[1]: systemd-coredump@0-32993-0.service: Consumed 1.356s CPU time, 679M memory peak.

```

The last comment on the AUR for Tixati is that it has moved to GTK3 while the dependencies for are it are in the GTK2 family.

What else can I do to debug this?

Last edited by strammer (2024-12-22 16:44:24)

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,589

Website

Re: Tixati causes segmentation fault

Mod note: moving to AUR Issues

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.