You are not logged in.
Issue started after upgrading GNOME 41 to 42:
gnome-shell 1:42.0-1
mutter 42.0-2It is being associated with dual-GPU setups:
https://bugs.launchpad.net/mutter/+bug/1964037
However, I have a single GPU setup:
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2060] driver: nvidia v: 510.60.02
Display: server: X.Org 21.1.3 driver: loaded: nvidia resolution:
1: 1920x1200~60Hz 2: 1920x1200~60Hz
OpenGL: renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
v: 4.6.0 NVIDIA 510.60.02And getting that same segfault:
Stack trace of thread 1048:
#0 0x00007fb3d11fe540 g_log_structured_array (libglib-2.0.so.0 + 0x5c540)
#1 0x00007fb3d11fe80a g_log_default_handler (libglib-2.0.so.0 + 0x5c80a)
#2 0x00007fb3d11ffcdd g_logv (libglib-2.0.so.0 + 0x5dcdd)
#3 0x00007fb3d11fffe4 g_log (libglib-2.0.so.0 + 0x5dfe4)
#4 0x00007fb3d142534a n/a (libgio-2.0.so.0 + 0xe634a)
#5 0x00007fb3d142688f g_settings_get_value (libgio-2.0.so.0 + 0xe788f)
#6 0x00007fb3d1427cc1 g_settings_get_boolean (libgio-2.0.so.0 + 0xe8cc1)
#7 0x00007fb3d04d65dc n/a (libmutter-10.so.0 + 0x825dc)
#8 0x00007fb3d131d01a g_type_create_instance (libgobject-2.0.so.0 + 0x3d01a)
#9 0x00007fb3d1303cee n/a (libgobject-2.0.so.0 + 0x23cee)
#10 0x00007fb3d1304f35 g_object_new_with_properties (libgobject-2.0.so.0 + 0x24f35)
#11 0x00007fb3d1305a9a g_object_new (libgobject-2.0.so.0 + 0x25a9a)
#12 0x00007fb3d04b3ae2 n/a (libmutter-10.so.0 + 0x5fae2)
#13 0x00007fb3d13b1ca1 g_initable_new_valist (libgio-2.0.so.0 + 0x72ca1)
#14 0x00007fb3d13b1d5e g_initable_new (libgio-2.0.so.0 + 0x72d5e)
#15 0x00007fb3d053a085 n/a (libmutter-10.so.0 + 0xe6085)
#16 0x00007fb3d0537d09 n/a (libmutter-10.so.0 + 0xe3d09)
#17 0x00007fb3d053ef0e n/a (libmutter-10.so.0 + 0xeaf0e)
#18 0x00007fb3d053f613 meta_context_setup (libmutter-10.so.0 + 0xeb613)
#19 0x000056498779d14a n/a (gnome-shell + 0x214a)
#20 0x00007fb3d025a310 __libc_start_call_main (libc.so.6 + 0x2d310)
#21 0x00007fb3d025a3c1 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d3c1)
#22 0x000056498779d745 n/a (gnome-shell + 0x2745)Last edited by Mischa85 (2022-04-11 14:17:21)
Offline
The ubuntu backtrace doesn't match yours at all - you're likely hitting an out-of-bounds array access on logging "something", but the pretext is completely different.
As is tradition, this gnome update broke all extensions, so make sure to disable them all.
If you're still hitting the segfault despite that, please post the entire journal, since gnome will likely provide some context errors on when exactly this fails.
Offline
You are right. While digging further in the log I found this:
gnome-shell[1033]: Settings schema 'org.gnome.desktop.privacy' does not contain a key named 'privacy-screen'Which is part of package:
gsettings-desktop-schemasWhich ended up to be a manual git install on my end, so it did not get updated. I did not notice this at first, because there's no gnome in the package name. It is hard to find all related packages this way.
Once I manually updated that particular package to 42 everything started working.
Thank you.
Offline