Hi,
this topic following this one : Problems with wayland after updating to fedora 39 - #57 by gnwiii
summary :
wayland does not execute. Xorg launches instead, but the display is degraded (latency of about 2 seconds).
in previous post, @Thomas points out :
@thomas :
could you give us your GPU config ? (how many GPU ? one ? two ? optimus config ? AMD/nvidia .)
this is my configuration (when wayland is OK) :
inxi -G
Graphics:
Device-1: NVIDIA GA104M [GeForce RTX 3070 Mobile / Max-Q] driver: nvidia
v: 535.129.03
Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
driver: amdgpu v: kernel
Device-3: Chicony [] driver: uvcvideo type: USB
Display: wayland server: X.Org v: 23.2.2 with: Xwayland v: 23.2.2
compositor: gnome-shell v: 45.1 driver: X: loaded: amdgpu,nvidia
unloaded: fbdev,modesetting,nouveau,vesa dri: radeonsi
gpu: amdgpu,nvidia,nvidia-nvswitch resolution: 1: 1920x1080~60Hz
2: 1920x1080~60Hz
API: OpenGL v: 4.6 vendor: amd mesa v: 23.2.1 renderer: AMD Radeon
Graphics (renoir LLVM 16.0.6 DRM 3.54 6.6.2-201.fc39.x86_64)
API: EGL Message: EGL data requires eglinfo. Check --recommends.
also i notice thoses messages in /var/lib/gdm/.local/share/xorg/Xorg.0.log file :
211.263] (WW) NVIDIA(G0): Failed to set the display configuration
[ 211.263] (WW) NVIDIA(G0): - Setting a mode on head 0 failed: Insufficient permissions
[ 211.263] (WW) NVIDIA(G0): - Setting a mode on head 1 failed: Insufficient permissions
[ 211.263] (WW) NVIDIA(G0): - Setting a mode on head 2 failed: Insufficient permissions
[ 211.263] (WW) NVIDIA(G0): - Setting a mode on head 3 failed: Insufficient permissions
[ 211.268] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 211.269] (II) Server terminated successfully (0). Closing log file.
it seems to be appear when wayland failed and when Xorg is executed with latency
new updates available today :
akmod-nvidia-3:545.29.06-1.fc39.x86_64
nvidia-settings-3:545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-3:545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-cuda-libs-3:545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-kmodsrc-3:545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-libs-3:545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-power-3:545.29.06-1.fc39.x86_64
nvidia-modprobe-3:545.29.06-1.fc39.x86_64
no change for me, same behavior 
Thank you very much @newsnews for creating this new topic and for taking care!
I am running an i5 with a NVidia 3060Ti:
# Systemdetailsbericht
---
## Berichtdetails
- **Erstellungsdatum:** 2023-12-01 14:03:35
## Hardware Information:
- **Hardware-Modell:** ASUS TUF GAMING B660-PLUS WIFI D4
- **Speicher:** 48,0 GiB
- **Prozessor:** 12th Gen Intel® Core™ i5-12400F × 12
- **Grafik:** NVIDIA GeForce RTX™ 3060 Ti
- **Festplattenkapazität:** 20,0 TB
## Software Information:
- **Firmware-Version:** 2801
- **Name des Betriebssystems:** Fedora Linux 39 (Workstation Edition)
- **Betriebssystem-Build:** (null)
- **Betriebssystem-Typ:** 64-bit
- **GNOME-Version:** 45.1
- **Fenstermanager:** X11
- **Kernel-Version:** Linux 6.6.2-201.fc39.x86_64
Here is my graphics config:
[root@wlg3060 gdm]# inxi -G
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] driver: nvidia
v: 535.129.03
Device-2: Logitech HD Webcam C615 driver: snd-usb-audio,uvcvideo type: USB
Display: server: X.Org v: 1.20.14 with: Xwayland v: 23.2.2 driver: X:
loaded: nvidia gpu: nvidia,nvidia-nvswitch resolution: 1: 2560x1440~60Hz
2: N/A
API: EGL v: 1.5 drivers: nvidia platforms: gbm
API: OpenGL v: 4.6.0 vendor: nvidia v: 535.129.03 renderer: NVIDIA
GeForce RTX 3060 Ti/PCIe/SSE2
API: Vulkan v: 1.3.250 drivers: nvidia,llvmpipe surfaces: xcb,xlib
As you can see I am currently running under X11 as my Wayland sessions are very unstable. I will continue testing later today or during the weekend, when I have more time.
In the meantime I have activated GDM debugging in /etc/gdm/custom.conf.
EDIT:
Looking into /var/lib/gdm/.local/share/xorg/Xorg.0.log I find the following warnings:
[ 19.447] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 19.863] (WW) NVIDIA: Failed to bind sideband socket to
[ 19.863] (WW) NVIDIA: '/var/run/nvidia-xdriver-46948357' Permission denied
Does this help?
/EDIT
@gnwiii suggested to turn on Gnome Setting Notification. What is this and how to activate it? I am probably lacking experience in troubleshooting Gnome issues…
Just a final remark for now: With the current update (Kernel 6.6.2. etc.) Wayland based sessions became even more unstable for me again. I would love to get back my relyable system as used to on FC38 and earlier.
Thank you very much in advance.
Thomas
I am still on NVidia 535 and will try and report this later today.
See: Gnome Shell Notifications. In Gnome Settings, chose the Notifications tab. You get a list of apps. I set everything to “On” (I think that is the default for fresh installs) for upgrades. “Problem Reporting” is what you need when there are problems.
Thank you George! Now I see, what you mean. Everything was enabled already.
I have updated to NVidia 545 drivers now and everything seems to be worse. There is heavy flickering, when windows are updated (e.g. Chrome browser here right whike typing). Quite annoying!
Today the first login to wayland failed, the second did work.
After turning on all recommnded debug option my journal contains the following error:
Dez 02 18:55:00 wlg3060 gnome-shell[1784]: Connection to xwayland lost
Dez 02 18:55:00 wlg3060 gnome-shell[1784]: Xwayland terminated, exiting since it was mandatory
Dez 02 18:55:00 wlg3060 gnome-shell[1784]: (../src/core/meta-context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop))
Dez 02 18:55:00 wlg3060 gnome-shell[1784]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly
@resource:///org/gnome/shell/ui/init.js:21:20
Dez 02 18:55:00 wlg3060 gnome-shell[1784]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
Dez 02 18:55:00 wlg3060 /usr/libexec/gdm-wayland-session[1772]: gnome-session-binary[1772]: DEBUG(+): Caught SIGINT/SIGTERM, shutting down normally.
Dez 02 18:55:00 wlg3060 /usr/libexec/gdm-wayland-session[1772]: gnome-session-binary[1772]: DEBUG(+): GsmManager: requesting logout
Dez 02 18:55:00 wlg3060 /usr/libexec/gdm-wayland-session[1772]: gnome-session-binary[1772]: DEBUG(+): GsmManager: ending phase RUNNING
ui/init.js threw an exception? Does this help?
There are tons of debug information in the file. Please let me know, if and how I should publish/upload this.
Does anybody habe an idea?
Thank you in advance!
Thomas
the problem seems to be feixed on my system.
no problem in the last 5 days.
many updates in this period (kernel / nvidia drivers) so i can’t say what update is useful.
below, the list of my actual kernel / nvidia drivers :
kernel-modules-core-6.6.4-200.fc39.x86_64
kernel-core-6.6.4-200.fc39.x86_64
kernel-modules-6.6.4-200.fc39.x86_64
kernel-devel-6.6.4-200.fc39.x86_64
kernel-devel-matched-6.6.4-200.fc39.x86_64
kernel-6.6.4-200.fc39.x86_64
kernel-modules-extra-6.6.4-200.fc39.x86_64
saisissez ou collez du code ici
nvidia-gpu-firmware-20231111-1.fc39.noarch
xorg-x11-drv-nvidia-libs-545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-kmodsrc-545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-cuda-libs-545.29.06-1.fc39.x86_64
nvidia-modprobe-545.29.06-1.fc39.x86_64
akmod-nvidia-545.29.06-1.fc39.x86_64
nvidia-settings-545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-power-545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-545.29.06-1.fc39.x86_64
nvidia-persistenced-545.29.06-1.fc39.x86_64
xorg-x11-drv-nvidia-cuda-545.29.06-1.fc39.x86_64
kmod-nvidia-6.6.4-200.fc39.x86_64-545.29.06-1.fc39.x86_64
Regards
It would be useful to mention whether you are using Xorg or Wayland or whether both now work.
Dear friends,
I have waited for some time to see, whether the problem stabilizes with some updates or not. For me there is no relieve. The problem persists: Gnome/Wayland sessions do not start, or if they start occasionally, they are very unstable, screen flickers or is not updated or session crashes. I am close to reinstalling Fedora, which I would love to avoid…
In the meantime I am running all updates of FC39 until today, e.g. especially Gnome 45.2, NVidia 545, Kernel 6.6.4, but no change.
It became quite silent here, so I assume there are changes for others. Can yyou please tell, whether somebody had a chance to fight this problems?
Furthermore (since Kernel 6.6.4 or similar) I have problems with my resolver, which does not start correctly and needs to be restarted after each boot. I will report this in a seperate thread.
Thank you in advance!
Thomas
Reinstalling linux (unlike Windows) rarely fixes problems. and does nothting to help understand the cause of the issue. Much of the power of linux comes from the community of users who contribute useful problem/bug reports and the others who can suggest solutions, so you will do better by taking advantage of the community. We know that for every user who posts a problem report here there and many others with the same problem who never go beyond web searches, so
you should know that a good, searchable, post will benefit others and is a valuable contribution to the community.
Before reinstalling, you should attempt to collect some data that could help resolve your issue and also allow others with the same issue find your posts with web searches.
Have you verified that the problem occurs for a freshly created user login?
Have you installed vendor firmware updates? Large vendors use fwupd, others provide either bootable images or Windows updaters.
Collecting error messages and posting here may allow others to recognize the issue and provide a solution. Best practice is to post inxi -Fzxx output from a terminal along with excerpts from journalctl for the time the problem occurred. Journalctl provides enormous levels of details, so it is an art to extract relevant details. You can use time, keywords, and priorities to narrow down the output. Watch for very long lines when copying terminal output. Once you have found a way to limit the output you can use redirection to capture the output in a file. Use an editor to remove remaining irrelevant lines and then paste the text into your post (as text using the </> button) .
I am having the same issue still, with still no solution. Wayland starts occasionally but often kicks me out randomly, and I have to log back in with X11. Or Wayland does not start at all and I am stuck with X11. They clearly screwed something up with the F39 release, fortunately I dual boot with Ubuntu which seems to be working fine for now.
I have already tried a reinstall as a last resort, and that did not fix the problem either, but it convinced me that the problem is not on my end.
The post just above your last asks for output from inxi -Fzxx.
That is a very common starting point that we may use to have a baseline from which to work on analyzing the issues. Please provide at least that much information.
Many Fedora users are not having problems, and those who had problems with Wayland after installing Fedora 39 now have Wayland working reliably on fully updated Fedora 39. Some issues may still exist with Gnome extensions.
Comparisons with Ubuntu aren’t meaningful as Ubuntu generally lags behind software versions found in Fedora (so benefits from bugs that were found and fixed in Fedora).
The time required for a reinstall is much better spent collecting and posting data.
I am running Fedora KDE, with AMD Ryzen 5 5600G with Radeon Graphics (12) @ 4.464GHz and have an identical problem, so probably it is not a Gnome/nvidia specific thing, or there is an identical unrelated issue.
When running journalctl -g wayland i get
gru 16 00:05:45 fedora sddm-helper[1505]: Starting Wayland user session: "/etc/sddm/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland"
gru 16 00:05:47 fedora sddm-helper-start-wayland[1575]: "kf.service.services: The desktop entry file \"/usr/share/applications/org.freedesktop.Xwayland.desktop\" has Type= \"Application\" but has no Exec field.\n"
gru 16 00:05:47 fedora sddm-greeter[1578]: Wayland does not support QWindow::requestActivate()
gru 16 00:05:47 fedora sddm-greeter[1578]: Wayland does not support QWindow::requestActivate()
gru 16 00:05:59 fedora sddm-helper-start-wayland[1575]: Stopping... "kwin_wayland"
gru 16 00:06:48 fedora plasmashell[2333]: kf.service.services: The desktop entry file "/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type= "Application" but has no Exec field.
gru 16 00:06:48 fedora plasmashell[2333]: kf.service.services: The desktop entry file "/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type= "Application" but has no Exec field.
I accidentally changed sddm to autologin on wayland and just got a black screen on startup, had to change config files from liveboot, not fun.
This is KDE bug 430157: “Fixed in 5.113” with a long discussion.
Thanks for info, I’m shocked as i thought i have searched everywhere. Sadly it is only “fixed”, as i have plasma 5.27, will probably bring it up there.
Still not working for me:
Output of inxi -Fzxx
System:
Kernel: 6.6.9-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.40-13.fc39 Desktop: GNOME v: 45.3 tk: GTK v: 3.24.39 wm: gnome-shell
dm: GDM Distro: Fedora release 39 (Thirty Nine)
Machine:
Type: Desktop System: Gigabyte product: Z390 AORUS PRO WIFI v: N/A
serial: <superuser required>
Mobo: Gigabyte model: Z390 AORUS PRO WIFI-CF serial: <superuser required>
UEFI: American Megatrends v: F12 date: 11/05/2021
CPU:
Info: 8-core model: Intel Core i7-9700K bits: 64 type: MCP arch: Coffee Lake
rev: D cache: L1: 512 KiB L2: 2 MiB L3: 12 MiB
Speed (MHz): avg: 800 min/max: 800/4900 cores: 1: 800 2: 800 3: 800 4: 800
5: 800 6: 800 7: 800 8: 800 bogomips: 57600
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: NVIDIA TU104 [GeForce RTX 2080 Rev. A] vendor: Gigabyte
driver: nvidia v: 545.29.06 arch: Turing pcie: speed: 2.5 GT/s lanes: 16
ports: active: none off: DP-2, DP-3, HDMI-A-1, Unknown-2 empty: DP-1
bus-ID: 01:00.0 chip-ID: 10de:1e87
Device-2: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 046d:085c
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.2.3
compositor: gnome-shell driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
gpu: nvidia,nvidia-nvswitch display-ID: :1 screens: 1
Screen-1: 0 s-res: 15360x2160 s-dpi: 96
Monitor-1: DP-2 note: disabled pos: primary,left model: Philips PHL 278E1
res: 3840x2160 dpi: 163 diag: 685mm (27")
Monitor-2: not-matched mapped: DP-4 pos: center-l res: 3840x2160 dpi: 163
diag: 685mm (26.97")
Monitor-3: HDMI-A-1 mapped: HDMI-0 note: disabled pos: center-r
model: Philips PHL 278E1 res: 3840x2160 dpi: 163 diag: 685mm (27")
Monitor-4: not-matched mapped: USB-C-0 pos: right res: 3840x2160 dpi: 163
diag: 685mm (26.97")
API: OpenGL v: 4.6.0 vendor: nvidia v: 545.29.06 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a348
Device-2: NVIDIA TU104 HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f8
Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-3:2 chip-ID: 046d:085c
Device-4: Texas Instruments PCM2704 16-bit stereo audio DAC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 bus-ID: 1-7:5 chip-ID: 08bb:2704
API: ALSA v: k6.6.9-200.fc39.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:a370
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-14:11
chip-ID: 8087:0aaa
Report: btmgmt ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 5.1
lmp-v: 10
Device-2: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-9:6 chip-ID: 0b05:17cb
Report: ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6
Drives:
Local Storage: total: 2.89 TiB used: 28.75 GiB (1.0%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB
speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 35.9 C
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB
speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
ID-3: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50
size: 465.76 GiB speed: 6.0 Gb/s serial: <filter>
ID-4: /dev/sdb vendor: Intel model: SSDSA2CW080G3 size: 74.53 GiB
speed: 3.0 Gb/s serial: <filter>
ID-5: /dev/sdc vendor: Intel model: SSDSC2BB300G4 size: 279.46 GiB
speed: 6.0 Gb/s serial: <filter>
ID-6: /dev/sdd vendor: Intel model: SSDSC2BB300G4 size: 279.46 GiB
speed: 6.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 929.91 GiB used: 28.44 GiB (3.1%) fs: btrfs dev: /dev/dm-0
mapped: luks-8baf9b3b-1659-4eb0-b023-6b144a124426
ID-2: /boot size: 973.4 MiB used: 299.1 MiB (30.7%) fs: ext4
dev: /dev/nvme1n1p2
ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
dev: /dev/nvme1n1p1
ID-4: /home size: 929.91 GiB used: 28.44 GiB (3.1%) fs: btrfs
dev: /dev/dm-0 mapped: luks-8baf9b3b-1659-4eb0-b023-6b144a124426
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 30.0 C pch: 51.0 C mobo: N/A gpu: nvidia
temp: 54 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Processes: 397 Uptime: 12m Memory: total: 16 GiB available: 15.53 GiB
used: 3.15 GiB (20.3%) Init: systemd v: 254 target: graphical (5)
default: graphical Compilers: gcc: 13.2.1 Packages: pm: rpm pkgs: N/A
note: see --rpm pm: flatpak pkgs: 12 Shell: Bash v: 5.2.21
running-in: gnome-terminal inxi: 3.3.31
Please confirm that Fedora 39 is fully updated and that you have the current firmware (I think Gigabyte tells you to got to the AMI site), but your can try fwupdtool. This is important a) so you aren’t chasing a problem that has already been fixed, and b) means others with access to the same hardware will be able to match your software environment.
Please describe the Waland errors can you start a Wayland session or only Xorg? Can you get a console (<Ctrl-Atl F3>) if the GUI is dead?
You can try lookiing for relevant errors with journalctl -b N -p 3, where N is the number of the boot (bank for the current session, -1 for the previous boot session).