Bug#1098391: celluloid: Segfault at start
Hi,
This problem doesn't seem to be in the celluloid code, but it seems to
me to be a GTK 4 rendering problem that is occurring on some hardwares
that started in GTK 4.16 and I saw this in the backtrace when
reporting in the first lines vl_compositor_gfx_render. This occurs on
my machine if I don't set GSK_RENDERER=gl in /etc/environment and that
you can configure if your hardware is Nvidia or AMD (see
links[1][2][3][4]).
And it would be interesting if you could mention what your hardware
would be with inxi, if you prefer, or any other way that also helps us
to check if it is a problem that occurs specifically in some hardware
such as this.
There is a patch in Debian that changes the default renderer back to
ngl[6], but in your case, if it is not, this may be another problem
and it would be interesting to do some tests. But running on my
machine, I have no problems in Debian testing/sid and in Mint (Ubuntu
24.04) with this package using version 0.26-1.
[1] https://www.phoronix.com/news/GTK-4.16-Released
[2] https://docs.gtk.org/gsk4/class.Renderer.html
[3] https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/
[4] https://askubuntu.com/questions/1534586/ubuntu-24-04-freezes-at-various-times-and-even-reboots
[5] https://tracker.debian.org/pkg/gtk4
[6] https://sources.debian.org/src/gtk4/4.17.5+ds-3/debian/patches/debian/gsk-Change-default-renderer-back-to-ngl.patch/
[7] https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2082017
[8] https://discussion.fedoraproject.org/t/gsk-renderer-ngl-and-gl-nvidia-xorg-random-gsk-errors-after-6-7-apps-open/135123
--
Cheers,
Leandro Cunha
Reply to: