mrmax
March 11, 2025, 8:58am
1
Dear Fedora Community,
As a long-time user of Debian-based distributions, I recently transitioned to Fedora 41 and opted for the Hyprland window manager. However, I’ve encountered significant challenges with GNOME applications failing to render correctly under Wayland.
System Setup:
Distribution: Fedora Linux 41 (Workstation Edition) x86_64Kernel: Linux 6.11.4-301.fc41.x86_64Window Manager: Hyprland 0.47.2Graphics Card: NVIDIA GeForce RTX 3070 Lite Hash Ratehyprland version 0.47.2gnome shell version 47.4
Issues Encountered:
GNOME applications, such as Nautilus and GNOME Calendar, open but display blank or unresponsive windows.
Troubleshooting Steps Taken:
Created a New User Profile:
Established a new user with default settings to rule out configuration issues; the problem persisted.
Investigated Hyprland Configuration:
Reviewed system-wide Hyprland settings but found no anomalies affecting GNOME applications.
Forced Applications to Use X11:
Set the environment variable GDK_BACKEND=x11, which allowed applications to run but case other problem with apps that are need wayland to work, for example “waybar”
Reinstalled GNOME:
Removed and reinstalled GNOME components; the rendering issues remained.
Installed GNOME Applications via Flatpak:
Installed GNOME apps using Flatpak for isolated environments; the issues persisted.
Observations:
The rendering issues are not exclusive to NVIDIA graphics cards; users with AMD and Intel GPUs have reported similar problems.
Discussions on Fedora forums suggest that these issues have arisen following recent updates to GNOME 47.
I am seeking guidance on resolving these GNOME application rendering issues under Hyprland on Fedora 41. Any insights or recommendations from the community would be greatly appreciated.
Best regards,
Ali Mussa
Welcome to the forums @mrmax
I just tried installing from hyprland from scratch on a Gnome system and everything worked as expected. This is on an AMD system.
Perhaps you could try starting hyprland with an empty / auto-generated config and no other panels or widgets loaded, to see if that makes a difference?
Is there anything visible in the logs that could indicate an issue?
mrmax
March 11, 2025, 9:38am
3
I tried installing only hyprland on fresh system, just hyprland without any other additional software and I faced the same problem.
Do you see anything in the logs that could indicate a problem?
$ journalctl --since=today -p 3
This will show all lines in today’s log with a level of 3 (error) or higher.
mrmax
March 11, 2025, 8:59pm
5
"I don’t know what I should look for, but this is my log
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0000 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0100 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0200 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0300 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0400 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0500 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0600 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0700 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0800 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0011 address=0xffec0b0900 flags=0x0000]
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: sec2(gsp): mbox 0000009f 00007fff
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: sec2(gsp):booter-unload: boot failed: -5
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: sec2(gsp): mbox 00000098 00007fff
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: sec2(gsp):booter-load: boot failed: -5
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: gsp: init failed, -5
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: init failed with -5
Mar 11 08:17:44 fedora kernel: nouveau: DRM-master:00000000:00000080: init failed with -5
Mar 11 08:17:44 fedora kernel: nouveau: DRM-master:00000000:00000000: init failed with -5
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: DRM: Client resume failed with error: -5
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: PM: dpm_run_callback(): pci_pm_resume returns -5
Mar 11 08:17:44 fedora kernel: nouveau 0000:0a:00.0: PM: failed to resume async: error -5
-- Boot 390d8e6e8807409585b5e0912fce4c76 --
Mar 11 11:33:57 fedora kernel: call_irq_handler: 1.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 2.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 3.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 4.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 5.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 6.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 7.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 8.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 9.55 No irq handler for vector
Mar 11 11:33:57 fedora kernel: call_irq_handler: 10.55 No irq handler for vector
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 11:34:00 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:02 fedora /usr/bin/nvidia-powerd[974]: Allocate client failed 89
Mar 11 08:34:02 fedora /usr/bin/nvidia-powerd[974]: Failed to initialize RM Client
Mar 11 08:34:06 fedora dbus-broker-launch[1318]: Invalid D-Bus name 'hyprpolkitagent' in service file '/usr/share//dbus-1/services/hyprpolkitagent.service'
Mar 11 08:34:06 fedora dbus-broker-launch[1318]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
Mar 11 08:34:06 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:06 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:06 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: mmu fault queued
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: rc engn:00000001 chid:32 type:31 scope:1 part:233
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: fifo:c00000:0004:0020:[gst-plugin-scan[1415]] errored - disabling channel
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: mmu fault queued
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: rc engn:00000001 chid:32 type:31 scope:1 part:233
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: fifo:c00000:0004:0020:[gst-plugin-scan[1415]] errored - disabling channel
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: mmu fault queued
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: rc engn:00000001 chid:32 type:31 scope:1 part:233
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: fifo:c00000:0004:0020:[gst-plugin-scan[1415]] errored - disabling channel
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:07 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:18 fedora gdm-password][1981]: gkr-pam: unable to locate daemon control file
Mar 11 08:34:19 fedora dbus-broker-launch[2049]: Invalid D-Bus name 'hyprpolkitagent' in service file '/usr/share//dbus-1/services/hyprpolkitagent.service'
Mar 11 08:34:19 fedora dbus-broker-launch[2049]: Ignoring duplicate name 'org.freedesktop.FileManager1' in service file '/usr/share//dbus-1/services/org.xfce.Thunar.FileManager1.service'
Mar 11 08:34:19 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:19 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:19 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:19 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:19 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
Mar 11 08:34:19 fedora kernel: nouveau 0000:0a:00.0: gsp: cli:0xc1d00002 obj:0x00730000 ctrl cmd:0x00731341 failed: 0x0000ffff
litemotiv
March 11, 2025, 10:19pm
6
These are mostly gpu errors, but not really of the kind that could explain your issue well. So i’m not sure whether they could be related, perhaps not likely.
mrmax
March 11, 2025, 11:39pm
7
What system are you running? If you’re on Fedora 41, could you try installing Hyprland from the official repo and confirm whether the issue is caused by a recent update or if it’s a hardware-related problem? I’ve already reinstalled Fedora, so it’s not a configuration or installation issue.
litemotiv
March 11, 2025, 11:43pm
8
I’m currently on the F42 prerelease, so a slightly different version.
mrmax
March 12, 2025, 11:24pm
9
I finally found the fix for the GNOME app rendering issue on Hyprland with an NVIDIA GPU.
I noticed a slight delay when opening Alacritty, which made me suspect a GPU-related issue. After some investigation, I removed the komod driver:
sudo dnf remove akmod-nvidia kmod-nvidia-6.13.5-200.fc41.x86_64
Immediately, my system became much faster. I tested GNOME apps, and they started working correctly. To fully resolve the issue, I installed the proper NVIDIA driver:
sudo dnf update -y
sudo dnf install xorg-x11-drv-nvidia-cuda
After a reboot, everything worked fine. Hopefully, this helps others facing the same problem!
