Spectacle will not work but shows up in System Monitor applications pane.
All animations have switched to instant and i can’t switch them back .
window decorations do not appear on sides or bottom of windows .
Mouse movements appear jagged at times .
Seems a single root cause: KWin’s compositor has crashed/fallen back to software rendering.
Perhaps first some diags:
qdbus6 org.kde.KWin /Compositor active
if false, try kick it back on:
qdbus6 org.kde.KWin /Compositor resume
KWin journal logs:
journalctl --user -u plasma-kwin_wayland --boot -0 | grep -iE "compositor|opengl|egl|crash|fatal|gpu"
More broadly:
journalctl --user -b0 | grep -i kwin
OpenGL marked as unsafe after a compos. crash:
grep -i "OpenGLIsUnsafe\|Enabled\|Backend" ~/.config/kwinrc
Figure out what possibly broke the compositor 1st after updates:
# GPU hardware
lspci | grep -E "VGA|3D"
# Session type
echo $XDG_SESSION_TYPE
# Current kernel
uname -r
# Recent DNF transactions (look for mesa/nvidia/kwin/kernel changes)
dnf history list | head -5
Let’s first see if all above give some pointers.
Compositor returns true .
(base) rbarrett@phaedra:~$ journalctl --user -u plasma-kwin_wayland --boot -0 | grep -iE "compositor|opengl|egl|crash|fatal|gpu"
May 20 07:00:24 phaedra systemd[2237]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 20 07:00:24 phaedra systemd[2237]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 20 07:00:25 phaedra kwin_wayland[2579]: eglInitialize failed
May 20 07:00:25 phaedra kwin_wayland[2579]: Error during eglInitialize "EGL_NOT_INITIALIZED"
May 20 07:00:25 phaedra kwin_wayland[2579]: Creating the OpenGL rendering failed: "Could not initialize egl"
May 20 07:00:25 phaedra plasma-keyboard[2618]: qtvirtualkeyboard currently is not supported at client-side, use QT_IM_MODULES=qtvirtualkeyboard at compositor-side.
May 20 07:00:25 phaedra kwin_wayland_wrapper[2618]: libEGL warning: failed to get driver name for fd -1
May 20 07:00:25 phaedra kwin_wayland_wrapper[2618]: libEGL warning: MESA-LOADER: failed to retrieve device information
May 20 07:00:25 phaedra kwin_wayland_wrapper[2618]: libEGL warning: failed to get driver name for fd -1
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: Errors from xkbcomp are not fatal to the X server
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: Errors from xkbcomp are not fatal to the X server
(base) rbarrett@phaedra:~$ journalctl --user -b0 | grep -i kwin
May 20 07:00:24 phaedra systemd[2237]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 20 07:00:24 phaedra systemd[2237]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 20 07:00:25 phaedra kwin_wayland[2579]: Icon theme "oxygen" not found.
May 20 07:00:25 phaedra kwin_wayland[2579]: No backend specified, automatically choosing drm
May 20 07:00:25 phaedra kwin_wayland[2579]: eglInitialize failed
May 20 07:00:25 phaedra kwin_wayland[2579]: Error during eglInitialize "EGL_NOT_INITIALIZED"
May 20 07:00:25 phaedra kwin_wayland[2579]: Creating the OpenGL rendering failed: "Could not initialize egl"
May 20 07:00:25 phaedra kwin_wayland_wrapper[2618]: libEGL warning: failed to get driver name for fd -1
May 20 07:00:25 phaedra kwin_wayland_wrapper[2618]: libEGL warning: MESA-LOADER: failed to retrieve device information
May 20 07:00:25 phaedra kwin_wayland_wrapper[2618]: libEGL warning: failed to get driver name for fd -1
May 20 07:00:25 phaedra kwin_wayland_wrapper[2628]: Xwayland glamor: GBM Wayland interfaces not available
May 20 07:00:25 phaedra kwin_wayland_wrapper[2628]: Failed to initialize glamor, falling back to sw
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: > Warning: Multiple symbols for level 1/group 1 on key <FK23>
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: > Using F23, ignoring XF86TouchpadOff
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: > Warning: Symbol map for key <FK23> redefined
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: > Using last definition for conflicting fields
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: > Warning: Symbol map for key <FK24> redefined
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: > Using last definition for conflicting fields
May 20 07:00:26 phaedra kwin_wayland_wrapper[2637]: Errors from xkbcomp are not fatal to the X server
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: The XKEYBOARD keymap compiler (xkbcomp) reports:
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: > Warning: Unsupported maximum keycode 709, clipping.
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: > X11 cannot support keycodes above 255.
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: > Warning: Virtual modifier Hyper multiply defined
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: > Using 0, ignoring 0
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: > Warning: Virtual modifier ScrollLock multiply defined
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: > Using 0, ignoring 0
May 20 07:00:26 phaedra kwin_wayland_wrapper[2648]: Errors from xkbcomp are not fatal to the X server
May 20 07:00:40 phaedra kwin_wayland[2579]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/2579/root")
May 20 07:00:40 phaedra kwin_wayland[2579]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/2579/root")
May 20 07:30:17 phaedra systemsettings[10341]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations.
May 20 07:30:26 phaedra kded6[2674]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations.
May 20 07:30:26 phaedra kwin_wayland[2579]: Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations.
May 20 09:25:01 phaedra kwin_wayland[2579]: This plugin does not support grabbing the keyboard
May 20 09:25:05 phaedra kwin_wayland[2579]: This plugin does not support grabbing the keyboard
May 20 10:21:55 phaedra kwin_wayland[2579]: QDBusConnection: couldn't handle call to active, no slot matched
May 20 10:21:55 phaedra kwin_wayland[2579]: QDBusConnection: couldn't handle call to active, no slot matched
May 20 10:21:55 phaedra kwin_wayland[2579]: Could not find slot CompositingAdaptor::active
(base) rbarrett@phaedra:~$ grep -i "OpenGLIsUnsafe\|Enabled\|Backend" ~/.config/kwinrc
glideEnabled=true
scaleEnabled=false
(base) rbarrett@phaedra:~$ lspci | grep -E "VGA|3D"
01:00.0 VGA compatible controller: NVIDIA Corporation GA106 [Geforce RTX 3050] (rev a1)
06:00.0 Audio device: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D / Z-Series / Sound BlasterX AE-5 Plus] (rev 01)
0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c3)
echo $XDG_SESSION_TYPE
wayland
# Current kernel
uname -r
7.0.9-202.fc44.x86_64
(base) rbarrett@phaedra:~$ # Recent DNF transactions (look for mesa/nvidia/kwin/kernel changes)
dnf history list | head -5
ID Command line Date and time Action(s) Altered
32 dnf -y install --nogpgcheck --disabler 2026-05-19 22:03:32 1
31 2026-05-19 21:59:24 93
30 2026-05-19 03:22:50 28
29 2026-05-18 11:14:12 2
One thing stands out, EGL doesn’t initialize (at all) because it can’t open a GPU device = software rendering = most likely your symptoms.
You have a hybrid AMD/Nvidia setup, though it seems that none of the GPU’s is accessible to Kwin.
Check if DRM device nodes exist:
ls -la /dev/dri/
Should show card0, card1 and renderD128/renderD129. If this dir is empty or missing entries, that’s the problem.
NVIDIA driver loaded (can’t hurt to check):
nvidia-smi
AMD GPU kernel driver loaded:
lsmod | grep -E "amdgpu|nvidia"
Check what that (93) package update changed, re. Mesa/kernel packages:
dnf history info 31 | grep -iE "mesa|kernel|nvidia|drm|libgbm|wayland|kwin"
Check if your MESA install is intact:
rpm -qa | grep mesa | sort
This should (hopefully) pinpoint the issue.
My theory is the package update either bumped mesa or the kernel in a way that broke DRM device access for the AMD igpu. On Wayland, KWin talks directly to DRM and if Mesa’s GBM/EGL can’t find the AMD GPU, all collapses. The NVIDIA wouldn’t normally be used by KWin on this kind of hybrid setup (offload-only via PRIME), so the AMD side seems the critical factor here.
there is only one video card rtx3050
(base) rbarrett@phaedra:~$ ls -la /dev/dri/
total 0
drwxr-xr-x. 3 root root 140 May 20 06:59 .
drwxr-xr-x. 22 root root 4900 May 20 07:00 ..
drwxr-xr-x. 2 root root 140 May 20 06:59 by-path
crw-rw----+ 1 root video 226, 1 May 20 07:00 card1
crw-rw----+ 1 root video 226, 2 May 20 10:18 card2
crw-rw-rw-. 1 root render 226, 128 May 20 06:59 renderD128
crw-rw-rw-. 1 root render 226, 129 May 20 06:59 renderD129
(base) rbarrett@phaedra:~$ nvidia-smi
bash: nvidia-smi: command not found...
Packages providing this file are:
'xorg-x11-drv-nvidia-390xx-cuda'
'xorg-x11-drv-nvidia-470xx-cuda'
'xorg-x11-drv-nvidia-580xx-cuda'
'xorg-x11-drv-nvidia-cuda'
(base) rbarrett@phaedra:~$ lsmod | grep -E "amdgpu|nvidia"
nvidia_uvm 2699264 0
nvidia_drm 163840 30
nvidia_modeset 2183168 1 nvidia_drm
nvidia 16326656 23 nvidia_uvm,nvidia_modeset
amdgpu 22130688 0
amdxcp 12288 1 amdgpu
i2c_algo_bit 24576 1 amdgpu
drm_ttm_helper 20480 2 amdgpu,nvidia_drm
ttm 135168 2 amdgpu,drm_ttm_helper
drm_exec 12288 1 amdgpu
drm_panel_backlight_quirks 12288 1 amdgpu
gpu_sched 73728 1 amdgpu
drm_suballoc_helper 20480 1 amdgpu
drm_buddy 28672 1 amdgpu
drm_display_helper 348160 1 amdgpu
cec 110592 2 drm_display_helper,amdgpu
video 81920 3 asus_wmi,amdgpu,nvidia_modeset
(base) rbarrett@phaedra:~$ dnf history info 31 | grep -iE "mesa|kernel|nvidia|drm|libgbm|wayland|kwin"
Install kernel-devel-0:7.0.9-202.fc44.x86_64 User updates
Install kernel-modules-0:7.0.9-202.fc44.x86_64 User updates
Install kernel-modules-core-0:7.0.9-202.fc44.x86_64 User updates
Install kernel-core-0:7.0.9-202.fc44.x86_64 User updates
Install kernel-0:7.0.9-202.fc44.x86_64 User updates
Upgrade kernel-devel-matched-0:7.0.9-202.fc44.x86_64 Dependency updates
Upgrade kernel-tools-0:7.0.9-202.fc44.x86_64 Group updates
Upgrade kernel-tools-libs-0:7.0.9-202.fc44.x86_64 Dependency updates
Remove kernel-0:7.0.6-200.fc44.x86_64 User @System
Remove kernel-core-0:7.0.6-200.fc44.x86_64 User @System
Remove kernel-devel-0:7.0.6-200.fc44.x86_64 User @System
Remove kernel-modules-0:7.0.6-200.fc44.x86_64 User @System
Remove kernel-modules-core-0:7.0.6-200.fc44.x86_64 User @System
Remove kmod-nvidia-7.0.6-200.fc44.x86_64-3:595.71.05-1.fc44.x86_64 Dependency @System
Replaced kernel-devel-matched-0:7.0.8-200.fc44.x86_64 Dependency @System
Replaced kernel-tools-0:7.0.8-200.fc44.x86_64 Group @System
Replaced kernel-tools-libs-0:7.0.8-200.fc44.x86_64 Dependency @System
(base) rbarrett@phaedra:~$ rpm -qa | grep mesa | sort
mesa-compat-libxatracker-25.0.7-7.fc44.x86_64
mesa-dri-drivers-26.0.6-2.fc44.i686
mesa-dri-drivers-26.0.6-2.fc44.x86_64
mesa-filesystem-26.0.6-2.fc44.i686
mesa-filesystem-26.0.6-2.fc44.x86_64
mesa-libEGL-26.0.6-2.fc44.i686
mesa-libEGL-26.0.6-2.fc44.x86_64
mesa-libgbm-26.0.6-2.fc44.i686
mesa-libgbm-26.0.6-2.fc44.x86_64
mesa-libGL-26.0.6-2.fc44.i686
mesa-libGL-26.0.6-2.fc44.x86_64
mesa-libGLU-9.0.3-8.fc44.x86_64
mesa-vulkan-drivers-26.0.6-2.fc44.i686
mesa-vulkan-drivers-26.0.6-2.fc44.x86_64
You actually have 2 GPU’s, shown by yourlspci output:
01:00.0 VGA compatible controller: NVIDIA Corporation GA106 [Geforce RTX 3050]
0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael
The log show clearly that the KWIn can’t initialize EGL:
eglInitialize failed
failed to get driver name for fd -1
MESA-LOADER: failed to retrieve device information
DNF history points to the likely cause: kernel updated from 7.0.6 to 7.0.9, and the old Nvidia kernel module (kmod-nvidia for 7.0.6) was removed during that event. Also, nvidia-smi not being found means the Nvidia userspace packages apparently aren’t fully installed.
The AMD has an integrated GPU. On Wayland, KDE prefers using the AMD iGPU for desktop compositing and the Nvidia dGPU available for heavier loads. For that, both GPUs matter here. If the NVIDIA driver is partially installed and interfering with Mesa’s EGL path for the AMD GPU, for example, that would cause exactly what you’re experiencing.
Can you provide the next info for a full driver state?
# What Nvidia packages
rpm -qa | grep -i nvidia | sort
# Which driver handling each GPU
ls -la /sys/class/drm/card*/device/driver
# Which EGL libraries installed
ls -la /usr/lib64/libEGL*
# user in the right groups for GPU access?
groups
Based on that info is either a simple rebuild/re-install fix of the Nvidia driver but, lets first see what’s going on.
(base) rbarrett@phaedra:~$ # What Nvidia packages
rpm -qa | grep -i nvidia | sort
akmod-nvidia-595.71.05-1.fc44.x86_64
kmod-nvidia-7.0.7-200.fc44.x86_64-595.71.05-1.fc44.x86_64
kmod-nvidia-7.0.8-200.fc44.x86_64-595.71.05-1.fc44.x86_64
kmod-nvidia-7.0.9-202.fc44.x86_64-595.71.05-1.fc44.x86_64
nvidia-gpu-firmware-20260410-1.fc44.noarch
nvidia-modprobe-595.71.05-1.fc44.x86_64
nvidia-settings-595.71.05-1.fc44.x86_64
xorg-x11-drv-nvidia-595.71.05-1.fc44.x86_64
xorg-x11-drv-nvidia-cuda-libs-595.71.05-1.fc44.x86_64
xorg-x11-drv-nvidia-kmodsrc-595.71.05-1.fc44.x86_64
xorg-x11-drv-nvidia-libs-595.71.05-1.fc44.i686
xorg-x11-drv-nvidia-libs-595.71.05-1.fc44.x86_64
xorg-x11-drv-nvidia-power-595.71.05-1.fc44.x86_64
xorg-x11-drv-nvidia-xorg-libs-595.71.05-1.fc44.x86_64
(base) rbarrett@phaedra:~$
(base) rbarrett@phaedra:~$ # Which driver handling each GPU
ls -la /sys/class/drm/card*/device/driver
lrwxrwxrwx. 1 root root 0 May 20 07:00 /sys/class/drm/card1/device/driver -> ../../../../bus/pci/drivers/amdgpu
lrwxrwxrwx. 1 root root 0 May 20 07:00 /sys/class/drm/card2/device/driver -> ../../../../bus/pci/drivers/nvidia
(base) rbarrett@phaedra:~$ # Which EGL libraries installed
ls -la /usr/lib64/libEGL*
lrwxrwxrwx. 1 root root 20 Apr 29 20:00 /usr/lib64/libEGL_mesa.so.0 -> libEGL_mesa.so.0.0.0
-rwxr-xr-x. 1 root root 403688 Apr 29 20:00 /usr/lib64/libEGL_mesa.so.0.0.0
lrwxrwxrwx. 1 root root 26 Apr 27 20:00 /usr/lib64/libEGL_nvidia.so.0 -> libEGL_nvidia.so.595.71.05
-rwxr-xr-x. 1 root root 1288448 Apr 24 02:28 /usr/lib64/libEGL_nvidia.so.595.71.05
lrwxrwxrwx. 1 root root 15 Jan 15 19:00 /usr/lib64/libEGL.so.1 -> libEGL.so.1.1.0
-rwxr-xr-x. 1 root root 70184 Jan 15 19:00 /usr/lib64/libEGL.so.1.1.0
(base) rbarrett@phaedra:~$
(base) rbarrett@phaedra:~$ # user in the right groups for GPU access?
groups
rbarrett wheel
That looks OK re. GPU’s, however, the NVIDIA kernel module was rebuilt for the new kernel, but the userspace EGL/initramfs state likely never caught up for some reason.
For the next step, although a relative low risk, we all know certain laws. Make a backup if you have snapper, etc.
I suggest to rebuild and regenerate first:
# Force NVIDIA module rebuild for the running kernel
sudo akmods --force
# Verify the module version matches what's installed
modinfo -F version nvidia
# Expected: 595.71.05
# Regenerate initramfs to ensure all GPU modules are properly included
sudo dracut --force
# Reboot
sudo reboot
When back, verify:
# Compositor should now be active
qdbus6 org.kde.KWin /Compositor active
# Expected: true
# Re-check the KWin log for EGL errors
journalctl --user -u plasma-kwin_wayland --boot -0 | grep -iE "egl|opengl"
# Expected: no "eglInitialize failed" lines
Check animations, window decoration and Spectacle. Hopefully good, otherwise there are some next steps to take, but lets see how this goes.
(base) rbarrett@phaedra:~$ sudo akmods --force
[sudo] password for rbarrett:
Checking kmods exist for 7.0.9-202.fc44.x86_64 [ OK ]
(base) rbarrett@phaedra:~$ modinfo -F version nvidia
595.71.05
(base) rbarrett@phaedra:~$ sudo dracut --force
(base) rbarrett@phaedra:~$
----reboots
(base) rbarrett@phaedra:~$ qdbus6 org.kde.KWin /Compositor active
true
(base) rbarrett@phaedra:~$ journalctl --user -u plasma-kwin_wayland --boot -0 | grep -iE "egl|opengl"
May 20 13:29:49 phaedra kwin_wayland[2572]: eglInitialize failed
May 20 13:29:49 phaedra kwin_wayland[2572]: Error during eglInitialize "EGL_NOT_INITIALIZED"
May 20 13:29:49 phaedra kwin_wayland[2572]: Creating the OpenGL rendering failed: "Could not initialize egl"
May 20 13:29:49 phaedra kwin_wayland_wrapper[2616]: libEGL warning: failed to get driver name for fd -1
May 20 13:29:49 phaedra kwin_wayland_wrapper[2616]: libEGL warning: MESA-LOADER: failed to retrieve device information
May 20 13:29:49 phaedra kwin_wayland_wrapper[2616]: libEGL warning: failed to get driver name for fd -1
Nothing changed .
Ruled out the the kernel/initramfs path.
Comes to mind that the 595.71.05 driver commonly doesn’t play nice with kernel 7.0.x, according to Github bug tracker and Nvidia (regression branch). Your system shows similarities and it wouldn’t surprise me if that’s the cause.
Let’s first try to force KWin to use the AMD iGPU for compositing (the NVIDIA card stays available for offload).
mkdir -p ~/.config/environment.d
echo "KWIN_DRM_DEVICES=/dev/dri/card1" > ~/.config/environment.d/kwin.conf
Then log out completely and log back in.
Verify:
journalctl --user -u plasma-kwin_wayland --boot -0 | grep -iE "egl|opengl"
If the “eglInitialize failed” lines are gone, you should immediately see animations return, decorations come and Spectacle work.
If no dice, roll back:
rm ~/.config/environment.d/kwin.conf
Log out and back in, then post the output of:
ls -la /usr/lib64/libEGL*
ls -la /usr/share/glvnd/egl_vendor.d/
eglinfo 2>&1 | head -50
(eglinfo may need sudo dnf install glx-utils first.)
So i did :
mkdir -p ~/.config/environment.d
echo "KWIN_DRM_DEVICES=/dev/dri/card1" > ~/.config/environment.d/kwin.conf
And then i logged in to a blank screen .
At this point i want to do a fresh install . i backed up everything .
The installation was only a week old and i did not do much with it .
i’ll wait till friday to do the install and see how it goes .
thanks for the help , i may be back . 
this is incomplete, package xorg-x11-drv-nvidia-libs-595.71.05-1.fc44.i686 is installed but xorg-x11-drv-nvidia-cuda-libs-595.71.05-1.fc44.i686 is missing.
try sudo dnf install xorg-x11-drv-nvidia-cuda-libs.i686
for nvidia-smi, install xorg-x11-drv-nvidia-cuda
what does eglinfo -B give? ( install egl-utils if not available)
If you want/need to rebuild nvidia kernel modules use sudo akmods --rebuild
dracut is NOT required at all. The drivers are not included in the initramfs.
the issue might be caused by this mesa bug
mesa exposes its own nvidia egl driver for nouveau as device #1 which fails ofc on systems with installed nvidia drivers.
device #0 is nvidia gpu via nvidia drivers
Device #1:
Platform Device platform:
libEGL warning: pci id for fd 25: 10de:1f15, driver (null)
pci id for fd 27: 10de:1f15, driver (null)
pci id for fd 28: 10de:1f15, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 25: 10de:1f15, driver (null)
pci id for fd 27: 10de:1f15, driver (null)
pci id for fd 28: 10de:1f15, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 25: 10de:1f15, driver (null)
eglinfo: eglInitialize failed
renaming 50_mesa.json in /usr/share/glvnd/egl_vendor.d/ to 50_mesa.json_OFF could be a workaround.
@anotheruser
That’s actually a very good finding. A fresh installation will most likely also have the same issue.
@reid-barrett
Switch to console: Ctrl+Alt+F3 (or F4/F5) at the login screen, log in and then run:
# remove the kwin override if not done already)
rm ~/.config/environment.d/kwin.conf
# Disable mesa's EGL vendor entry
sudo mv /usr/share/glvnd/egl_vendor.d/50_mesa.json /usr/share/glvnd/egl_vendor.d/50_mesa.json.disabled
# Reboot
sudo reboot
Then log in normally. If that works we owe Mark a beer 
yet, this should not really matter, because nvidia drivers should take care of that.
And here the missing cuda-libs i686 rpm might be the culprit if 32bit codepaths are involved. The OP has mesa i686 packages installed.
so I would suggest to try this first.
rm ~/.config/environment.d/kwin.conf
sudo dnf install xorg-x11-drv-nvidia-cuda-libs.i686
@reid-barrett pls post output of
eglinfo -B and rpm -qa egl\*
Well worth to do first and with the 50_mesa.json rename as a possible fallback (workaround).
After a clean install i installed software slowly a few at a time .
everythin was working good .
I installed GIMP and Krename . i did a reboot and installed
updates for Krename and GIMP 3.0.8 micro update . i rebooted and i
am back to having the same problems . i think GIMP is the cause .
eglinfo -B
GBM platform:
eglinfo: eglInitialize failed
Wayland platform:
libEGL warning: failed to get driver name for fd -1
libEGL warning: MESA-LOADER: failed to retrieve device information
libEGL warning: failed to get driver name for fd -1
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 26.0.6
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 26.0.6
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
X11 platform:
libEGL warning: DRI3 error: Could not get DRI3 device
libEGL warning: Ensure your X server supports DRI3 to get accelerated rendering
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 26.0.6
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 26.0.6
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Surfaceless platform:
libEGL warning: pci id for fd 3: 10de:2507, driver (null)
pci id for fd 4: 10de:2507, driver (null)
pci id for fd 5: 10de:2507, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: DRI2: failed to create screen
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Ryzen 7 7700X 8-Core Processor (radeonsi, raphael_mendocino, ACO, DRM 3.64, 7.0.9-205.fc44.x86_64)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.6
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Ryzen 7 7700X 8-Core Processor (radeonsi, raphael_mendocino, ACO, DRM 3.64, 7.0.9-205.fc44.x86_64)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.6
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Ryzen 7 7700X 8-Core Processor (radeonsi, raphael_mendocino, ACO, DRM 3.64, 7.0.9-205.fc44.x86_64)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Device platform:
Device #0:
Platform Device platform:
libEGL warning: pci id for fd 3: 10de:2507, driver (null)
pci id for fd 4: 10de:2507, driver (null)
pci id for fd 5: 10de:2507, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 3: 10de:2507, driver (null)
pci id for fd 4: 10de:2507, driver (null)
pci id for fd 5: 10de:2507, driver (null)
libEGL warning: egl: failed to create dri2 screen
libEGL warning: pci id for fd 3: 10de:2507, driver (null)
eglinfo: eglInitialize failed
Device #1:
Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Ryzen 7 7700X 8-Core Processor (radeonsi, raphael_mendocino, ACO, DRM 3.64, 7.0.9-205.fc44.x86_64)
OpenGL core profile version: 4.6 (Core Profile) Mesa 26.0.6
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Ryzen 7 7700X 8-Core Processor (radeonsi, raphael_mendocino, ACO, DRM 3.64, 7.0.9-205.fc44.x86_64)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 26.0.6
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Ryzen 7 7700X 8-Core Processor (radeonsi, raphael_mendocino, ACO, DRM 3.64, 7.0.9-205.fc44.x86_64)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Device #2:
Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 26.0.6
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 26.0.6
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 22.1.4, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 26.0.6
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20de here
rpm -qa egl\*
egl-utils-9.0.0-11.fc44.x86_64
egl-x11-1.0.5-1.fc44.x86_64
egl-wayland2-1.0.1-1.fc44.x86_64
egl-wayland-1.1.21-2.fc44.x86_64
egl-gbm-1.1.3-2.fc44.x86_64
egl-wayland-1.1.21-2.fc44.i686
egl-wayland2-1.0.1-1.fc44.i686
egl-x11-1.0.5-1.fc44.i686
egl-gbm-1.1.3-2.fc44.i686
it looks like you did not install the nvidia drivers correctly. You want to look into that first. This has nothing to do with gimp3 or any other application.
$ journalctl -b -g nvrm --no-hostname
May 23 20:57:13 kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64 595.71.05 Release Build (dvs-builder@U22-I3-G08-03-1) Fri Apr 24 06:42:30 UTC 2026
I just went through every setting in bios a found that integrated graphics
was turned on , and i don’t want that .
Is this a desktop or laptop? On most desktops, the iGPU won’t drive a monitor that is plugged into the dGPU’s port. (Laptops are different, both GPUs are capable of outputting to the same monitor.)