Hi Jeremy. Thanks for the reply. I'm not sure the issue is directly related to https://launchpad.net/bugs/2081291 . Both baobab and gnome-system- monitor (which, I believe, are gtk4-based) load without issue.
I upgraded libgtk-4-1 to the version in unstable, which caused these other updates as a side-effect: # apt-show-versions | grep unstable | grep gtk gir1.2-gtk-4.0:amd64/unstable 4.16.2+ds-3 uptodate gtk-update-icon-cache:amd64/unstable 4.16.2+ds-3 uptodate libgtk-4-1:amd64/unstable 4.16.2+ds-3 uptodate libgtk-4-bin:amd64/unstable 4.16.2+ds-3 uptodate libgtk-4-common:all/unstable 4.16.2+ds-3 uptodate libgtk-4-dev:amd64/unstable 4.16.2+ds-3 uptodate libgtk-4-media-gstreamer:amd64/unstable 4.16.2+ds-3 uptodate After reboot, the situation is the same: nautilus doesn't load, but baobab, gnome-system-monitor, etc., do load. And, just to clarify: I'm using the NVIDIA GPU as the primary one (as per these instructions: https://wiki.debian.org/NVIDIA%20Optimus#Using_NVIDIA_GPU_as_the_primary_GPU ). -- John M. On Mon, 2024-09-30 at 07:46 -0400, Jeremy Bícha wrote: > > Control: reassign -1 src:gtk4 4.16.2+ds-1 > Control: affects -1 src:nautilusControl: retitle -1 gtk4 apps crash > when using vulkan renderer with Nvidia hybrid graphics drivers > > On Sun, 2024-09-29 at 20:32 -0500, John M. wrote: > > After upgrade to version 47.0-1, nautilus fails to start with: > > … > > My video card is NVIDIA Quadro T2000, the X-Server is configured to > > use it directly (i.e., the Intel card is disabled). > > We believe this issue is https://launchpad.net/bugs/2081291 and needs > to be ultimately fixed in either Mesa or more likely in the Nvidia > drivers themselves. This issue affects other GTK4 apps beyond > Nautilus. > > We have worked around this issue by switching the default renderer > from vulkan to ngl in gtk4 4.16.2+ds-3. That version is currently in > Debian Unstable and should reach Debian Testing at the end of this > week. > > Thank you, > Jeremy Bícha
