GDM refuses to start using wayland

D1j1t · 2024-04-17 08:43:36

As the title states GDM is refusing to use wayland.

I have managed to get it to work temporarily by deleting /run/gdm/custom.conf and systemctl restarting gdm, then after that it works.

But after each boot the /run/gdm/custom.conf file returns

Here are my logs:
http://0x0.st/XozU.txt

Any help would be massively appreciated. Also I have already tried following the archwiki pages on GNOME and GDM and Wayland.

Last edited by D1j1t (2024-04-17 21:07:48)

V1del · 2024-04-17 09:17:26

https://wiki.archlinux.org/title/GDM#Wa … DIA_driver -- for the additional stipulations to be configured to enable this "properly", or the rule override you can apply to tell GDM to stop trying to know better.

D1j1t · 2024-04-17 09:46:02

My NVIDIA driver is on 550 so will this symlink still work fine and not break anything?

V1del · 2024-04-17 10:05:39

The symlink disables GDMs checks for whether it should enable wayland or not, so it will simply try to start it regardless. You likely haven't setup the nvidia suspension configs that it defaults to xorg anyway.

D1j1t · 2024-04-17 20:22:31

Just tested this now and IT WORKED!!! Thank you so so so much, I hope that anyone also having this issue will find this thread helpful!

D1j1t · 2024-04-17 21:07:29

Actually one last thing, wayland is acting strangely now and I am getting errors to do with NVIDIA on startup. Any explanation of how to fix the errors would be appreciated.

Logs here: http://0x0.st/Xo8P.txt

V1del · 2024-04-17 21:19:26

Drop nvidia_drm.fbdev=1 it's not quite there yet and on record for similar issues. Generally speaking some good improvements to wayland on nvidia should be expected for the 555 release slated for may.

D1j1t · 2024-04-18 17:52:03

That still didn't fix it, wayland seems very unstable and keeps crashing.

seth · 2024-04-18 20:39:26

Apr 17 22:00:03 elissa kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1

is fbdev - does that still show up in your journal?

D1j1t · 2024-04-18 20:45:24

Yes that is still in the logs even after removing the nvidia_drm.fbdev=1 from my kernel parameters

seth · 2024-04-18 20:49:33

cat /sys/module/nvidia_drm/parameters/fbdev
modprobe -c | grep -v alias | grep nvidia

and post an updated journal.
In doubt try to explicitly add "nvidia_drm.fbdev=0" to the kernel parameters.

D1j1t · 2024-04-18 21:25:14

The output of the first command was "N"

An the second output was:
options nvidia_drm modeset=1
softdep nvidia pre: vfio vfio_pci

edit: here is updated journal http://0x0.st/XouY.txt

Last edited by D1j1t (2024-04-18 21:28:56)

seth · 2024-04-18 21:37:23

fbdev is disabled, but you're running GDM on wayland but gnome on X11?

D1j1t · 2024-04-18 22:07:32

I'm trying to run gnome on wayland but because it keeps acting weird and crashing so in the mean time I am using gnome on x11 since that runs fine as a temporary solution.

seth · 2024-04-18 22:08:59

Ok, but it's hard to tell what's wrong w/ gnome on wayland if we only see gnome on X11

D1j1t · 2024-04-18 22:10:06

I'll switch over and resend the logs

D1j1t · 2024-04-18 22:15:03

First command: "N"
Second command:
options nvidia_drm modeset=1
options nvidia_drm fbdev=0
softdep nvidia pre: vfio vfio_pci

Logs: http://0x0.st/XoSH.txt

seth · 2024-04-18 23:07:40

Apr 18 23:14:09 elissa systemd-coredump[2625]: Process 1159 (gnome-shell) of user 1000 dumped core.
                                               
                                               Stack trace of thread 1159:
                                               #0  0x00007501d7295490 n/a (libgobject-2.0.so.0 + 0x37490)
                                               #1  0x00007501d7295803 g_type_is_a (libgobject-2.0.so.0 + 0x37803)
                                               #2  0x00007501d729ba6a g_value_type_compatible (libgobject-2.0.so.0 + 0x3da6a)
                                               #3  0x00007501d727cd4e n/a (libgobject-2.0.so.0 + 0x1ed4e)
                                               #4  0x00007501d728efe4 n/a (libgobject-2.0.so.0 + 0x30fe4)
                                               #5  0x00007501d728f9d7 g_signal_emit_valist (libgobject-2.0.so.0 + 0x319d7)
                                               #6  0x00007501d728fa94 g_signal_emit (libgobject-2.0.so.0 + 0x31a94)
                                               #7  0x00007501d761b1e9 n/a (libshell-14.so + 0x1b1e9)
                                               #8  0x00007501d6cd16bc n/a (libmutter-14.so.0 + 0xd16bc)
                                               #9  0x00007501d70005c9 _clutter_event_process_filters (libmutter-clutter-14.so.0 + 0x625c9)
                                               #10 0x00007501d702052b clutter_stage_handle_event (libmutter-clutter-14.so.0 + 0x8252b)
                                               #11 0x00007501d6c7acb5 n/a (libmutter-14.so.0 + 0x7acb5)
                                               #12 0x00007501d7318199 n/a (libglib-2.0.so.0 + 0x5a199)
                                               #13 0x00007501d73773bf n/a (libglib-2.0.so.0 + 0xb93bf)
                                               #14 0x00007501d7318dc7 g_main_loop_run (libglib-2.0.so.0 + 0x5adc7)
                                               #15 0x00007501d6cded5b meta_context_run_main_loop (libmutter-14.so.0 + 0xded5b)
                                               #16 0x00007501d6100596 n/a (libffi.so.8 + 0x7596)
                                               #17 0x00007501d60fd00e n/a (libffi.so.8 + 0x400e)
                                               #18 0x00007501d60ffbd3 ffi_call (libffi.so.8 + 0x6bd3)
                                               #19 0x00007501d7105fe1 n/a (libgjs.so.0 + 0x4bfe1)
                                               #20 0x00007501d7106688 n/a (libgjs.so.0 + 0x4c688)
                                               #21 0x00007501d57652da n/a (libmozjs-115.so + 0x15652da)
                                               #22 0x00007501d53d8b01 n/a (libmozjs-115.so + 0x11d8b01)
                                               #23 0x00007501d53d3ec5 n/a (libmozjs-115.so + 0x11d3ec5)
                                               #24 0x00007501d58ba1b1 _ZN2JS4CallEP9JSContextNS_6HandleINS_5ValueEEES4_RKNS_16HandleValueArrayENS_13MutableHandleIS3_EE (libmozjs-115.so + 0x16ba1b1)
                                               #25 0x00007501d713cf02 n/a (libgjs.so.0 + 0x82f02)
                                               #26 0x00007501d714517f gjs_context_eval_module (libgjs.so.0 + 0x8b17f)
                                               #27 0x00007501d7145481 gjs_context_eval_module_file (libgjs.so.0 + 0x8b481)
                                               #28 0x00005b89f501857f n/a (gnome-shell + 0x357f)
                                               #29 0x00007501d6a43cd0 n/a (libc.so.6 + 0x25cd0)
                                               #30 0x00007501d6a43d8a __libc_start_main (libc.so.6 + 0x25d8a)
                                               #31 0x00005b89f50189e5 n/a (gnome-shell + 0x39e5)

https://wiki.archlinux.org/title/Core_d … _core_dump
https://wiki.archlinux.org/title/Debuginfod might shed more light onto that.

D1j1t · 2024-04-19 05:14:59

Sorry but I don't understand what you want me to do next?

seth · 2024-04-19 07:38:52

Look at the coredump and install the debug symbols when suggested by gdb.
We want to have better information than "n/a" and the compromised chain.

D1j1t · 2024-04-19 16:43:34

coredumpctl debug match: No match found.
coredumpctl info match: No coredumps found.

V1del · 2024-04-19 16:45:06

you don't literally write match, but the PID you get from listing the coredumps with coredumpctl list

D1j1t · 2024-04-19 16:58:32

coredumpctl info: http://0x0.st/Xo_G.txt
coredumpctl debug: http://0x0.st/Xo_5.txt

debug also outputted: Failed to invoke gdb: No such file or directory

V1del · 2024-04-19 17:11:33

Install gdb and debuginfod and (might have to relog/reboot after so that environments are properly loaded) retry the command

Last edited by V1del (2024-04-19 17:18:13)

D1j1t · 2024-04-19 17:46:53

info: http://0x0.st/XoL_.txt
also what should I do in debug

edit: nevermind I just checked the wiki

Last edited by D1j1t (2024-04-19 17:48:05)

Arch Linux

#1 2024-04-17 08:43:36

GDM refuses to start using wayland

#2 2024-04-17 09:17:26

Re: GDM refuses to start using wayland

#3 2024-04-17 09:46:02

Re: GDM refuses to start using wayland

#4 2024-04-17 10:05:39

Re: GDM refuses to start using wayland

#5 2024-04-17 20:22:31

Re: GDM refuses to start using wayland

#6 2024-04-17 21:07:29

Re: GDM refuses to start using wayland

#7 2024-04-17 21:19:26

Re: GDM refuses to start using wayland

#8 2024-04-18 17:52:03

Re: GDM refuses to start using wayland

#9 2024-04-18 20:39:26

Re: GDM refuses to start using wayland

#10 2024-04-18 20:45:24

Re: GDM refuses to start using wayland

#11 2024-04-18 20:49:33

Re: GDM refuses to start using wayland

#12 2024-04-18 21:25:14

Re: GDM refuses to start using wayland

#13 2024-04-18 21:37:23

Re: GDM refuses to start using wayland

#14 2024-04-18 22:07:32

Re: GDM refuses to start using wayland

#15 2024-04-18 22:08:59

Re: GDM refuses to start using wayland

#16 2024-04-18 22:10:06

Re: GDM refuses to start using wayland

#17 2024-04-18 22:15:03

Re: GDM refuses to start using wayland

#18 2024-04-18 23:07:40

Re: GDM refuses to start using wayland

#19 2024-04-19 05:14:59

Re: GDM refuses to start using wayland

#20 2024-04-19 07:38:52

Re: GDM refuses to start using wayland

#21 2024-04-19 16:43:34

Re: GDM refuses to start using wayland

#22 2024-04-19 16:45:06

Re: GDM refuses to start using wayland

#23 2024-04-19 16:58:32

Re: GDM refuses to start using wayland

#24 2024-04-19 17:11:33

Re: GDM refuses to start using wayland

#25 2024-04-19 17:46:53

Re: GDM refuses to start using wayland

Board footer