You are not logged in.
I have testing repositories enabled and now GNOME 47.0 was made available in there. Since I installed the packages for version 47.0, starting GDM will fail to start gnome-session and show that "something went wrong" screen. However I'm not sure what is going on and how to better debug it.
GDM output of 'journal -b': http://0x0.st/X3fg.txt
Some relevant messages:
set 18 13:11:06 positivo gnome-shell[757]: JS ERROR: Gio.IOErrorEnum: TypeError: this._currentSource is null
Stack trace:
getCurrentGroup@resource:///org/gnome/shell/ui/keyboard.js:2033:13
_updateKeys@resource:///org/gnome/shell/ui/keyboard.js:1658:48
_setupKeyboard@resource:///org/gnome/shell/ui/keyboard.js:1302:14
_init@resource:///org/gnome/shell/ui/keyboard.js:1230:14
Keyboard@resource:///org/gnome/shell/ui/keyboard.js:1179:4
_syncEnabled@resource:///org/gnome/shell/ui/keyboard.js:1111:30
KeyboardManager@resource:///org/gnome/shell/ui/keyboard.js:1091:14
_initializeUI@resource:///org/gnome/shell/ui/main.js:240:16
start@resource:///org/gnome/shell/ui/main.js:173:11
@resource:///org/gnome/shell/ui/init.js:12:47
@resource:///org/gnome/shell/ui/init.js:21:20
@resource:///org/gnome/shell/ui/init.js:21:20
set 18 13:11:06 positivo gnome-shell[757]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
set 18 13:11:06 positivo kernel: traps: gnome-shell[757] general protection fault ip:7f1d878b4575 sp:7ffd6e6b6540 error:0 in libc.so.6[a5575,7f1d87833000+171000]
set 18 13:11:06 positivo systemd-coredump[842]: Process 757 (gnome-shell) of user 120 terminated abnormally with signal 11/SEGV, processing...
set 18 13:11:06 positivo systemd[1]: Created slice Slice /system/systemd-coredump.
set 18 13:11:06 positivo systemd[1]: Started Process Core Dump (PID 842/UID 0).
set 18 13:11:07 positivo systemd-coredump[843]: Process 757 (gnome-shell) of user 120 dumped core.
Stack trace of thread 757:
#0 0x00007f1d878b4575 __libc_free (libc.so.6 + 0xa5575)
#1 0x00007f1d881265c6 g_error_free (libglib-2.0.so.0 + 0x445c6)
#2 0x00007f1d87f348d8 n/a (libgjs.so.0 + 0x518d8)
#3 0x00007f1d864b8760 n/a (libmozjs-128.so + 0x18b8760)
#4 0x00007f1d864c0b99 n/a (libmozjs-128.so + 0x18c0b99)
#5 0x00007f1d864bf439 n/a (libmozjs-128.so + 0x18bf439)
#6 0x00007f1d862648c0 n/a (libmozjs-128.so + 0x16648c0)
#7 0x00007f1d865738e7 n/a (libmozjs-128.so + 0x19738e7)
#8 0x00007f1d864bb104 n/a (libmozjs-128.so + 0x18bb104)
#9 0x00007f1d8648a532 n/a (libmozjs-128.so + 0x188a532)
#10 0x00007f1d86489f2b n/a (libmozjs-128.so + 0x1889f2b)
#11 0x00007f1d8647e7b0 n/a (libmozjs-128.so + 0x187e7b0)
#12 0x00007f1d86383276 n/a (libmozjs-128.so + 0x1783276)
#13 0x00007f1d86572efa n/a (libmozjs-128.so + 0x1972efa)
#14 0x00007f1d87f6b41c n/a (libgjs.so.0 + 0x8841c)
#15 0x00007f1d880a3f6d g_object_unref (libgobject-2.0.so.0 + 0x20f6d)
#16 0x0000595ac316b89f n/a (gnome-shell + 0x289f)
#17 0x00007f1d87834e08 n/a (libc.so.6 + 0x25e08)
#18 0x00007f1d87834ecc __libc_start_main (libc.so.6 + 0x25ecc)
#19 0x0000595ac316b9e5 n/a (gnome-shell + 0x29e5)
Stack trace of thread 765:
#0 0x00007f1d8791abb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x00007f1d881a21a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x00007f1d88140187 g_main_loop_run (libglib-2.0.so.0 + 0x5e187)
#3 0x00007f1d88345ae4 n/a (libgio-2.0.so.0 + 0x113ae4)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 762:
#0 0x00007f1d879261fd syscall (libc.so.6 + 0x1171fd)
#1 0x00007f1d88170e20 g_cond_wait (libglib-2.0.so.0 + 0x8ee20)
#2 0x00007f1d8810798c n/a (libglib-2.0.so.0 + 0x2598c)
#3 0x00007f1d88177037 n/a (libglib-2.0.so.0 + 0x95037)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 763:
#0 0x00007f1d8791abb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x00007f1d881a21a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x00007f1d8813e955 g_main_context_iteration (libglib-2.0.so.0 + 0x5c955)
#3 0x00007f1d8813e9b2 n/a (libglib-2.0.so.0 + 0x5c9b2)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 769:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d860316b1 n/a (libmozjs-128.so + 0x14316b1)
#3 0x00007f1d8603140e n/a (libmozjs-128.so + 0x143140e)
#4 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#5 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 767:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d860316b1 n/a (libmozjs-128.so + 0x14316b1)
#3 0x00007f1d8603140e n/a (libmozjs-128.so + 0x143140e)
#4 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#5 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 768:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d860316b1 n/a (libmozjs-128.so + 0x14316b1)
#3 0x00007f1d8603140e n/a (libmozjs-128.so + 0x143140e)
#4 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#5 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 766:
#0 0x00007f1d8791abb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x00007f1d881a21a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x00007f1d8813e955 g_main_context_iteration (libglib-2.0.so.0 + 0x5c955)
#3 0x00007f1d800ea2fe n/a (libdconfsettings.so + 0x62fe)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 777:
#0 0x00007f1d879261fd syscall (libc.so.6 + 0x1171fd)
#1 0x00007f1d88171b37 g_cond_wait_until (libglib-2.0.so.0 + 0x8fb37)
#2 0x00007f1d88107955 n/a (libglib-2.0.so.0 + 0x25955)
#3 0x00007f1d88177afb n/a (libglib-2.0.so.0 + 0x95afb)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 770:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d860316b1 n/a (libmozjs-128.so + 0x14316b1)
#3 0x00007f1d8603140e n/a (libmozjs-128.so + 0x143140e)
#4 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#5 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 778:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d80ea5cae n/a (libgallium-24.2.2-arch1.1.so + 0xa5cae)
#3 0x00007f1d80e826cc n/a (libgallium-24.2.2-arch1.1.so + 0x826cc)
#4 0x00007f1d80ea5bdd n/a (libgallium-24.2.2-arch1.1.so + 0xa5bdd)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 772:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d80ea5cae n/a (libgallium-24.2.2-arch1.1.so + 0xa5cae)
#3 0x00007f1d80e826cc n/a (libgallium-24.2.2-arch1.1.so + 0x826cc)
#4 0x00007f1d80ea5bdd n/a (libgallium-24.2.2-arch1.1.so + 0xa5bdd)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 771:
#0 0x00007f1d8791abb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x00007f1d881a21a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x00007f1d88140187 g_main_loop_run (libglib-2.0.so.0 + 0x5e187)
#3 0x00007f1d87befbe8 n/a (libmutter-15.so.0 + 0x1efbe8)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 779:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d80ea5cae n/a (libgallium-24.2.2-arch1.1.so + 0xa5cae)
#3 0x00007f1d80e826cc n/a (libgallium-24.2.2-arch1.1.so + 0x826cc)
#4 0x00007f1d80ea5bdd n/a (libgallium-24.2.2-arch1.1.so + 0xa5bdd)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 780:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d80ea5cae n/a (libgallium-24.2.2-arch1.1.so + 0xa5cae)
#3 0x00007f1d80e826cc n/a (libgallium-24.2.2-arch1.1.so + 0x826cc)
#4 0x00007f1d80ea5bdd n/a (libgallium-24.2.2-arch1.1.so + 0xa5bdd)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 773:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d80ea5cae n/a (libgallium-24.2.2-arch1.1.so + 0xa5cae)
#3 0x00007f1d80e826cc n/a (libgallium-24.2.2-arch1.1.so + 0x826cc)
#4 0x00007f1d80ea5bdd n/a (libgallium-24.2.2-arch1.1.so + 0xa5bdd)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 782:
#0 0x00007f1d8791abb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x00007f1d881a21a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x00007f1d88140187 g_main_loop_run (libglib-2.0.so.0 + 0x5e187)
#3 0x00007f1d87be4e92 n/a (libmutter-15.so.0 + 0x1e4e92)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 781:
#0 0x00007f1d8789fa19 n/a (libc.so.6 + 0x90a19)
#1 0x00007f1d878a2479 pthread_cond_wait (libc.so.6 + 0x93479)
#2 0x00007f1d80ea5cae n/a (libgallium-24.2.2-arch1.1.so + 0xa5cae)
#3 0x00007f1d80e826cc n/a (libgallium-24.2.2-arch1.1.so + 0x826cc)
#4 0x00007f1d80ea5bdd n/a (libgallium-24.2.2-arch1.1.so + 0xa5bdd)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 791:
#0 0x00007f1d879261fd syscall (libc.so.6 + 0x1171fd)
#1 0x00007f1d88171b37 g_cond_wait_until (libglib-2.0.so.0 + 0x8fb37)
#2 0x00007f1d88107955 n/a (libglib-2.0.so.0 + 0x25955)
#3 0x00007f1d88177afb n/a (libglib-2.0.so.0 + 0x95afb)
#4 0x00007f1d88172f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x00007f1d878a339d n/a (libc.so.6 + 0x9439d)
#6 0x00007f1d8792849c n/a (libc.so.6 + 0x11949c)
ELF object binary architecture: AMD x86-64
set 18 13:11:07 positivo systemd[1]: systemd-coredump@0-842-0.service: Deactivated successfully.
set 18 13:11:07 positivo systemd[1]: systemd-coredump@0-842-0.service: Consumed 493ms CPU time, 209.3M memory peak.
set 18 13:11:07 positivo org.gnome.Shell.desktop[800]: (EE) could not connect to wayland server
and also:
set 18 13:11:12 positivo systemd-coredump[1136]: Process 983 (xdg-desktop-por) of user 120 dumped core.
Stack trace of thread 983:
#0 0x00005a3dc76273c7 n/a (xdg-desktop-portal-gnome + 0x323c7)
#1 0x000079d2ef90c40c n/a (libgio-2.0.so.0 + 0xa940c)
#2 0x000079d2ef90c455 n/a (libgio-2.0.so.0 + 0xa9455)
#3 0x000079d2efa8e459 n/a (libglib-2.0.so.0 + 0x5d459)
#4 0x000079d2efaf10d7 n/a (libglib-2.0.so.0 + 0xc00d7)
#5 0x000079d2efa8f187 g_main_loop_run (libglib-2.0.so.0 + 0x5e187)
#6 0x00005a3dc7603918 n/a (xdg-desktop-portal-gnome + 0xe918)
#7 0x000079d2ee719e08 n/a (libc.so.6 + 0x25e08)
#8 0x000079d2ee719ecc __libc_start_main (libc.so.6 + 0x25ecc)
#9 0x00005a3dc7603ee5 n/a (xdg-desktop-portal-gnome + 0xeee5)
Stack trace of thread 985:
#0 0x000079d2ee7ffbb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x000079d2efaf11a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x000079d2efa8d955 g_main_context_iteration (libglib-2.0.so.0 + 0x5c955)
#3 0x000079d2efa8d9b2 n/a (libglib-2.0.so.0 + 0x5c9b2)
#4 0x000079d2efac1f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x000079d2ee78839d n/a (libc.so.6 + 0x9439d)
#6 0x000079d2ee80d49c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 986:
#0 0x000079d2ee7ffbb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x000079d2efaf11a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x000079d2efa8f187 g_main_loop_run (libglib-2.0.so.0 + 0x5e187)
#3 0x000079d2ef976ae4 n/a (libgio-2.0.so.0 + 0x113ae4)
#4 0x000079d2efac1f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x000079d2ee78839d n/a (libc.so.6 + 0x9439d)
#6 0x000079d2ee80d49c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 988:
#0 0x000079d2ee80b1fd syscall (libc.so.6 + 0x1171fd)
#1 0x000079d2efac0b37 g_cond_wait_until (libglib-2.0.so.0 + 0x8fb37)
#2 0x000079d2efa56955 n/a (libglib-2.0.so.0 + 0x25955)
#3 0x000079d2efa56ac8 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25ac8)
#4 0x000079d2efac6930 n/a (libglib-2.0.so.0 + 0x95930)
#5 0x000079d2efac1f26 n/a (libglib-2.0.so.0 + 0x90f26)
#6 0x000079d2ee78839d n/a (libc.so.6 + 0x9439d)
#7 0x000079d2ee80d49c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 984:
#0 0x000079d2ee80b1fd syscall (libc.so.6 + 0x1171fd)
#1 0x000079d2efabfe20 g_cond_wait (libglib-2.0.so.0 + 0x8ee20)
#2 0x000079d2efa5698c n/a (libglib-2.0.so.0 + 0x2598c)
#3 0x000079d2efac6037 n/a (libglib-2.0.so.0 + 0x95037)
#4 0x000079d2efac1f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x000079d2ee78839d n/a (libc.so.6 + 0x9439d)
#6 0x000079d2ee80d49c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 987:
#0 0x000079d2ee80b1fd syscall (libc.so.6 + 0x1171fd)
#1 0x000079d2efabfe20 g_cond_wait (libglib-2.0.so.0 + 0x8ee20)
#2 0x000079d2efa5698c n/a (libglib-2.0.so.0 + 0x2598c)
#3 0x000079d2efa569fd g_async_queue_pop (libglib-2.0.so.0 + 0x259fd)
#4 0x000079d2ee0d85fc n/a (libpangoft2-1.0.so.0 + 0xc5fc)
#5 0x000079d2efac1f26 n/a (libglib-2.0.so.0 + 0x90f26)
#6 0x000079d2ee78839d n/a (libc.so.6 + 0x9439d)
#7 0x000079d2ee80d49c n/a (libc.so.6 + 0x11949c)
Stack trace of thread 989:
#0 0x000079d2ee7ffbb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x000079d2efaf11a4 n/a (libglib-2.0.so.0 + 0xc01a4)
#2 0x000079d2efa8d955 g_main_context_iteration (libglib-2.0.so.0 + 0x5c955)
#3 0x000079d2ea59d2fe n/a (libdconfsettings.so + 0x62fe)
#4 0x000079d2efac1f26 n/a (libglib-2.0.so.0 + 0x90f26)
#5 0x000079d2ee78839d n/a (libc.so.6 + 0x9439d)
#6 0x000079d2ee80d49c n/a (libc.so.6 + 0x11949c)
ELF object binary architecture: AMD x86-64
set 18 13:11:12 positivo systemd[1]: systemd-coredump@3-1132-0.service: Deactivated successfully.
set 18 13:11:12 positivo systemd[1]: systemd-coredump@3-1132-0.service: Consumed 319ms CPU time, 98.2M memory peak.
Offline
I had the same problem yesterday morning. Downgrade gnome-shell and mutter. After a reboot, you should be able to login and consider what to do next. Leave it or rollback via Timeshift or some other process.
Offline
So 47rc-1 was fine but 47.0 crashes?
It looks like an incompatible extension (as is common w/ gnome updates) - can you log into a fresh user account?
Offline
It happens before even the choosing the account.
Offline
I have the same problem. I can't log in using Wayland, only using Xorg.
Offline
Same problem here... Update broke my system.
Edit: I can confirm that downgrading gnome-shell and mutter to 46.5 as suggested above works.
Last edited by pvizc (2024-09-19 14:34:52)
Offline
Got the backtraces via 'coredump debug':
gnome-shell, pid 796: http://0x0.st/X3vw.txt
gnome-shell, pid 960: http://0x0.st/X3vx.txt
gnome-shell, pid 1057: http://0x0.st/X3v3.txt
xdg-desktop-portal-gnome, pid 1019: http://0x0.st/X3vY.txt
Offline
It happens before even the choosing the account.
So GDM is affected. Or only GDM?
Can you still launch gnome https://wiki.archlinux.org/title/GNOME#Manually ?
GNOME 47 and GDM 47 are now in extra, is this still a problem w/o gnome-testing?
From the release notes, gnome copied code from X11 to not depend on X11 for pure wayland configurations - because of a recent pecularity: does anyone here NOT use the pt_BR locale?
Offline
Same as https://bbs.archlinux.org/viewtopic.php?id=299488 ?
(Though the journal doesn't look like it)
Offline
Manual activation failed:
dbus-daemon[4545]: [session uid=1000 pid=4545] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=1000 pid=4569 comm="/usr/lib/gnome-session-check-accelerated")
dbus-daemon[4545]: [session uid=1000 pid=4545] Successfully activated service 'org.gtk.vfs.Daemon'
fusermount3: failed to access mountpoint /run/user/1000/gvfs: Permission denied
dbus-daemon[4545]: [session uid=1000 pid=4545] Activating service name='org.freedesktop.systemd1' requested by ':1.4' (uid=1000 pid=4546 comm="/usr/lib/gnome-session-binary")
dbus-daemon[4545]: [session uid=1000 pid=4545] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
dbus-daemon[4545]: [session uid=1000 pid=4545] Activating service name='ca.desrt.dconf' requested by ':1.4' (uid=1000 pid=4546 comm="/usr/lib/gnome-session-binary")
dbus-daemon[4545]: [session uid=1000 pid=4545] Successfully activated service 'ca.desrt.dconf'
A connection to the bus can't be made
Offline
Issue reported in GNOME Shell issue #7912 and xdg-desktop-portal-gnome issue #141. (I was told to file one issue for each project's coredump)
Offline
There seems to be some issue with the Vulkan renderer. Might be worth disabling it. One way to do this is to simply uninstall any Vulkan drivers you might have installed.
https://bbs.archlinux.org/viewtopic.php?id=299546
Offline
I hope this can be helpful. I have a similar issue, although I don't have vulkan-intel installed and I'm actually able to start gnome shell from the tty.
I can also confirm that installing the RC version of the gnome-shell package I could start gdm normally, but I had issues with wifi.
So I downloaded the PKGBUILD from here and then reverted every commit from the gnome-shell repo until I was able to run gdm.
Adding these lines to the PKGBUILD at line 89
git revert 39a3da65
git revert 961ca226
git revert 2975afaf
git revert ce89b15b
and recompiling with makepkg -si, I'm able to log in, so whatever has happened in my case I suppose is related to those commits.
ETA: I don't have nvidia, just an intel igpu.
Last edited by pol5xc (2024-09-19 19:57:53)
Online
https://gitlab.gnome.org/GNOME/gnome-sh … te_2227023
does anyone here NOT use the pt_BR locale?
https://bbs.archlinux.org/viewtopic.php?id=298417
nb. the OPs gnome bails on
getCurrentGroup@resource:///org/gnome/shell/ui/keyboard.js:2033:13
Edit: pol5xc's reverts are dead on…
ibusManager: Simplify code and logic for setEngine()
39a3da65
keyboard: Replace `oskCompletion` setter with public method
961ca226
ibusManager: Change return value of `setCompletionEnabled()`
2975afaf
ibusManager: Use async await instead of callbacks
ce89b15b
Last edited by seth (2024-09-19 20:10:40)
Offline
does anyone here NOT use the pt_BR locale?
Sorry, I missed it.
My locale is it_IT.
Online
Because of the weird bug, you might still want to try to set it to en_US…
Offline
I hope this can be helpful. I have a similar issue, although I don't have vulkan-intel installed and I'm actually able to start gnome shell from the tty.
I can also confirm that installing the RC version of the gnome-shell package I could start gdm normally, but I had issues with wifi.
So I downloaded the PKGBUILD from here and then reverted every commit from the gnome-shell repo until I was able to run gdm.
Adding these lines to the PKGBUILD at line 89
git revert 39a3da65 git revert 961ca226 git revert 2975afaf git revert ce89b15b
and recompiling with makepkg -si, I'm able to log in, so whatever has happened in my case I suppose is related to those commits.
ETA: I don't have nvidia, just an intel igpu.
This workaround made my GNOME 47.0 environment work, although I used 'git reset --hard 8af1a1df' (commit immediately before ce89b15b).
Will update on the GNOME Shell issue. Thanks, it was a major evolution.
Offline
I don't think is related to this issue. Firstly because pol5xc's workaround works for me and my locale is pt_BR. Also it was about GTK misreading XCompose provided by libx11 and messing with Delete key. Latest gtk4 package fixes it.
Offline
The commits explicitly deal w/ ibus and a "feature" of gnome 47 is to have *copied* input code from X11 into the gnome code… so… I'd try en_US, this smells utterly related to the previous situation, also because of the memory corruption.
Offline
It turns out it was the on screen keyboard for me. I didn't even remember I had it enabled.
Online
https://gitlab.gnome.org/GNOME/gnome-sh … uests/3476 fixes for me even if the OSK (on-screen keyboard) is enabled.
Offline
It turns out it was the on screen keyboard for me. I didn't even remember I had it enabled.
Having the same problem as OP, and I _do_ have OSK turned on... Guess I can wait for the update (no problem as I have another DE), but can anyone please let me know how I can turn off the OSK?
I tried to follow using: https://wiki.archlinux.org/title/GDM#Di … ility_Menu but if I check the value, it says false:
$ gsettings get org.gnome.desktop.a11y.applications screen-keyboard-enabled
false
Offline
I tried to follow using: https://wiki.archlinux.org/title/GDM#Di … ility_Menu but if I check the value, it says false:
$ gsettings get org.gnome.desktop.a11y.applications screen-keyboard-enabled false
This is probably because your are running for your user, not GDM's user. The issue happens when OSK is enabled in GDM login screen, which is not ran by your user. :-)
Offline
rifaz_n wrote:I tried to follow using: https://wiki.archlinux.org/title/GDM#Di … ility_Menu but if I check the value, it says false:
$ gsettings get org.gnome.desktop.a11y.applications screen-keyboard-enabled false
This is probably because your are running for your user, not GDM's user. The issue happens when OSK is enabled in GDM login screen, which is not ran by your user. :-)
Needless to say, you are absolutely correct. I did `sudo -u gdm` the above command, and got `true`.
However, trying to disable it as `gdm` user but from a Wayland session and a tty environment, gives me error like thus:
$ sudo -u gdm gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled false
(process:some number): dconf-WARNING **: 22:20:43.684: failed to commit changes to dconf: Cannot autolaunch D-Bus without X11 $DISPLAY
I didn't try logging in to Gnome on X11 as I don't have the xorg package installed (and don't want to just for this little exploration).
Last edited by rifaz_n (2024-09-20 16:28:46)
Offline
sudo -u gdm dbus-run-session gsettings set org.gnome.desktop.a11y.applications screen-keyboard-enabled false
Offline