Page MenuHomeSolus

Polari 42.0 release 29 segfaults on startup.
Closed, ResolvedPublic

Description

Hello,
since last friday update, polari segfaults on startup:

►polari                                                       0.925s 12:11
fish: Job 1, 'polari' terminated by signal SIGSEGV (Erreur de frontière d'adresse)
►polari --version                                             0.914s 12:12
Polari 42.0

Event Timeline

Staudey added a subscriber: Staudey.

Thanks for the report! Will take a look as soon as I get home.

Hi,
This seem related to DRI and gtk4. Indeed, polari is not the sole gnome program to segfault. gnome-control-center segfaults too:
gdb shows this backtrace both on polari and gnome-control-center:

[...]
#14 0x00007fffd29f859c in  () at /usr/lib64/dri/crocus_dri.so
#15 0x00007ffff770aa97 in  () at /usr/lib/libgtk-4.so.1
#16 0x00007ffff770c2fc in  () at /usr/lib/libgtk-4.so.1
#17 0x00007ffff7703e66 in  () at /usr/lib/libgtk-4.so.1
#18 0x00007ffff76e66b0 in gsk_renderer_realize () at /usr/lib/libgtk-4.so.1
#19 0x00007ffff76e6d69 in gsk_renderer_new_for_surface ()

Interesting, so this is probably related to the issue someone mentioned on IRC, which should be fixed by libgtk-4 >= 4.6.4

Has this been fixed by the latest GTK4 update? Not sure if it's in Stable or Unstable.

Apparently didn't make it in time for the sync: https://packages.getsol.us/shannon/libg/libgtk-4/ still shows 4.6.2 as the latest version.

Unfortunately I can't test this on my system because it works fine for me, but I'll try to see if I can reproduce it in a VM (and if so, whether the update actually fixes things)

@be1: Is this still happening for you after the latest updates?

@be1: Is this still happening for you after the latest updates?

For now I switched to another distro. So I cannot tell.

@be1 Okay, thanks for reporting back in any case!

I'm tentatively going to close this as fixed by R5107:30f1e226cdc70141897aa5504a222f983694af54 since I never could reproduce it after the update, and it sounds similar to issues that should've been fixed by it.

If someone else still experiences this bug, we can re-open it.