So, as it says in the title, I am experiencing some very weird behavior of my system after updating to f39 workstation, which still persists after the next system update. What happens is that when I boot my system the only 2 options I see in gdm are gnome and gnome classic, both of which are x11. When i sign in I therefore end up in x11 session. Sometimes it takes a few attempts to log in (it just returns to the login page without showing my desktop). In order to use wayland i need to log out and only then I see the option to use wayland which becomes selected by default. Also when I live my computer for some time I can end up logged out and without wayland option, although unlike when I boot my system I haven’t been able to reliably reproduce this behavior
I’ve tried to find similar issues on forums, but most of them are either about kde specific bugs or being unable to use wayland session at all. I’ve tried running this command, taken from another thread while in the “forced” x11 session. Here’s the output:
$ sudo dbus-run-session -- gnome-shell --display-server --wayland
dbus-daemon[6182]: [session uid=0 pid=6182] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=0 pid=6183 comm="gnome-shell --display-server --wayland" label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
dbus-daemon[6182]: [session uid=0 pid=6182] Successfully activated service 'org.gtk.vfs.Daemon'
libmutter-Message: 19:01:46.357: Running GNOME Shell (using mutter 45.1) as a Wayland display server
Failed to setup: Could not get session ID: User 0 has no sessions
A connection to the bus can't be made
Also I tried looking through journalctl output, but i’m not familiar with that utility and it is kinda hard to look through 300,000+ lines of logs, also I noticed some errors regarding many things uncluding dbus and nvidia drivers
Nov 20 19:19:43 moon-d kernel: nvidia: loading out-of-tree module taints kernel.
Nov 20 19:19:43 moon-d kernel: nvidia: module license 'NVIDIA' taints kernel.
Nov 20 19:19:43 moon-d kernel: Disabling lock debugging due to kernel taint
Nov 20 19:19:43 moon-d kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Nov 20 19:19:43 moon-d kernel: nvidia: module license taints kernel.
Nov 20 19:19:43 moon-d kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 234
Nov 20 19:19:43 moon-d kernel:
Nov 20 19:19:43 moon-d kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Nov 20 19:19:44 moon-d kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023
Nov 20 19:19:44 moon-d (udev-worker)[788]: nvidia: Process '/usr/bin/bash -c '/usr/bin/mknod -Z -m 666 /dev/nvidiactl c $(grep nvidia-frontend /proc/devices | cut -d \ -f 1) 255'' failed with exit code 1.
Nov 20 19:19:44 moon-d (udev-worker)[788]: nvidia: Process '/usr/bin/bash -c 'for i in $(cat /proc/driver/nvidia/gpus/*/information | grep Minor | cut -d \ -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontens/*/information | grep Minor | cut -d \ -f 4); do /usr/bin/mknod -Z -m 666 /dev/nvidia${i} c $(grep nvidia-frontend /proc/devices | cut -d \ -f 1) ${i}; done'' failed with exit code 1.
[...]
Nov 20 19:19:44 moon-d kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[...]
Nov 20 19:19:44 moon-d kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 535.129.03 Thu Oct 19 18:42:12 UTC 2023
Nov 20 19:19:44 moon-d kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
To give some context, I had some problems installing nvidia drivers about 6 month ago: they were running alongside nouveau driver which caused one additional screen to appear in settings, but which wasn’t detected by nvidia control panel. i resolved it by adding a kernel parameter in grub customizer that prevented the second driver from booting (now it is not showing up there for some reason, but everything works). other then that i didn’t make any changes to kernel or base system.
Speaking about my current issues, I tried to enable developer mode in gdm config to get more logs from it. After editing config and restarting I got something that I have never seen before in fedora
First this appeared on the second screen, then on the main one, but I cold still use the os more or less fine on the second screen and bring activities view on both. Also, looking into the screenshot utility this error existed in 2 instances
Also, I didn’t get any logs in gdm in /var/log/gdm
I would much appreciate any help troubleshooting this as I just don’t have any ideas left. I use linux for less then a year, so I don’t really know if the info i provided was useful, so if not, or if you need more, I will happily give it
System specs:
Hardware Information:
- Hardware Model: Gigabyte Technology Co., Ltd. Z390 AORUS MASTER
- Memory: 32.0 GiB
- Processor: Intel® Core™ i9-9900KF × 16
- Graphics: NVIDIA GeForce RTX™ 2080 SUPER
- Disk Capacity: 3.5 TB
Software Information:
- Firmware Version: F10
- OS Name: Fedora Linux 39 (Workstation Edition)
- OS Type: 64-bit
- GNOME Version: 45.1 (this part for some reason was missing from the settings app this boot)
- Windowing System: Wayland
- Kernel Version: Linux 6.5.11-300.fc39.x86_64