I have a laptop with an RTX 3060 mobile graphics card. I’ve upgraded from Fedora 43 to 44, and whilst there are no issues with the built-in display, my secondary screen is experiencing severe lag and even freezes. I’ve tried a few solutions but nothing’s worked—could you help?
Which drivers are you using, nvidia, nouveau? Is there an integrated graphic chipset too, and if so which card is driving which monitor.
Post the output from inxi -Fzxx and that’ll give us many of the answers in one hit.
System:
Kernel: 6.19.14-300.fc44.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 16.0.1
Desktop: KDE Plasma v: 6.6.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 44 (KDE Plasma Desktop Edition)
Machine:
Type: Laptop System: Dell product: Dell G15 5520 v: N/A
serial: <superuser required> Chassis: type: 10 serial: <superuser required>
Mobo: Dell model: 05J7DY v: A07 serial: <superuser required> part-nu: 0B58
Firmware: UEFI vendor: Dell v: 1.39.0 date: 12/23/2025
PU:
Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i7-12700H bits: 64
type: MST AMCP arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB
L3: 24 MiB
Speed (MHz): avg: 400 min/max: 400/4600:4700:3500 cores: 1: 400 2: 400
3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
13: 400 14: 400 15: 400 16: 400 17: 400 18: 400 19: 400 20: 400
bogomips: 107520
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
raphics:
Device-1: Intel Alder Lake-P Integrated Graphics vendor: Dell driver: i915
v: kernel arch: Xe ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0
chip-ID: 8086:4626
Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] vendor: Dell
driver: nvidia v: 595.71.05 arch: Ampere pcie: speed: 2.5 GT/s lanes: 8
ports: active: HDMI-A-1 empty: none bus-ID: 01:00.0 chip-ID: 10de:2560
Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-5:4 chip-ID: 0c45:6a14
Display: wayland server: Xwayland v: 24.1.11 compositor: kwin_wayland
driver: gpu: i915,nv_platform,nvidia,nvidia-nvswitch d-rect: 3840x1080
display-ID: 0
Monitor-1: HDMI-A-1 pos: primary,left model: ViewSonic VX2418C SER
res: 1920x1080 hz: 144 dpi: 94 diag: 600mm (23.6")
Monitor-2: eDP-1 pos: right model: LG Display 0x0738 res: 1920x1080
hz: 120 dpi: 142 diag: 395mm (15.5")
API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: iris
device: 3 drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland:
drv: iris x11: drv: iris inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 26.0.5 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
device-ID: 8086:4626 display-ID: :0.0
API: Vulkan v: 1.4.341 surfaces: N/A device: 0 type: integrated-gpu
driver: mesa intel device-ID: 8086:4626 device: 1 type: discrete-gpu
driver: nvidia device-ID: 10de:2560 device: 2 type: cpu
driver: mesa llvmpipe device-ID: 10005:0000
RTX 3060 Mobile → ViewSonic VX2418C SER (This is the screen where the freezes occur.)
Intel Alder Lake-P Integrated Graphics → Internal display
When my cursor is on the main screen, the stuttering and freezing on my second screen stop.
I edited your post above to add the preformatted text tags so it reads exactly as seen on your screen. I did note that some of the text has the first character of the line clipped, such as [G]raphics and [C]PU
Making the pasted text appear that way involves highlighting the text after it is pasted then click the </> button on the toolbar of the text entry screen.
I do have a hunch, does logging into an X11 plasma session solve the problem?
Or try adding the line KWIN_FORCE_SW_CURSOR=1 to the file /etc/environment and restart.
Please post output of modinfo -l nvidia.
check journal for lines similar to these:
Apr 01 20:26:33 fedora kwin_wayland[2351]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Apr 01 20:26:33 fedora kwin_wayland[2351]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Apr 01 20:26:33 fedora kwin_wayland[2351]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Apr 01 20:26:33 fedora kwin_wayland[2351]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Sorry mate, I haven’t been able to switch to a Linux environment for a while, so I only saw your reply now.
The new kernel update didn’t change a thing for me either; I tried setting KWIN_FORCE_SW_CURSOR=1. Thank you so much, it worked. I’m really grateful for your help.
that’s a workaround only not a solution!
Please post output of modinfo -l nvidia.
and check older journals for lines similar to these:
Apr 01 20:26:33 fedora kwin_wayland[2351]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Apr 01 20:26:33 fedora kwin_wayland[2351]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Apr 01 20:26:33 fedora kwin_wayland[2351]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Apr 01 20:26:33 fedora kwin_wayland[2351]: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
journalctl -g kwin_wayland --no-hostname --no-pager
As it covered a very long period, I took a section of it.
journalctl -g kwin_wayland --no-hostname --no-pager
-- Boot 896ee7aa1c954d9f80da6994290e9229 --
May 05 20:25:19 sddm-helper-start-wayland[1829]: Stopping... "kwin_wayland"
May 05 20:25:20 systemd[1969]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 05 20:25:20 systemd[1969]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 05 20:27:15 rsyslogd[1745]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 05 20:36:56 rsyslogd[1745]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 05 20:47:08 rsyslogd[1745]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 05 21:22:54 sddm[1758]: Auth: sddm-helper (--socket /tmp/sddm-auth-3cd7e388-ffdb-48d9-81ef-72b9e4bfc4f5 --id 4 --start /usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--UJOaZJ --theme /usr/share/sddm/themes/WhiteSur-dark --user sddm --display-server kwin_wayland --no-global-shortcuts --no-lockscreen --inputmethod plasma-keyboard --locale1 --greeter) crashed (exit code 1)
May 05 21:22:54 systemd[1969]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 05 21:22:54 systemd[1969]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 05 21:22:54 systemd[1969]: plasma-kwin_wayland.service: Consumed 5min 24.740s CPU time over 57min 34.137s wall clock time, 727.1M memory peak.
-- Boot 812d01806bdd4cb5b413b77552526d5f --
May 07 19:53:21 sddm-helper-start-wayland[1821]: Stopping... "kwin_wayland"
May 07 19:53:22 systemd[1967]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 19:53:22 systemd[1967]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 19:54:55 systemd[1967]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 19:54:55 systemd[1967]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 19:54:55 systemd[1967]: plasma-kwin_wayland.service: Consumed 12.163s CPU time over 1min 33.267s wall clock time, 453.8M memory peak.
-- Boot efe553c1842440039722daf86a5e7544 --
-- Boot 3dfa3464a9274e10bb5ad650119a823e --
May 07 19:58:16 sddm-helper-start-wayland[1820]: Stopping... "kwin_wayland"
May 07 19:58:16 systemd[1962]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 19:58:16 systemd[1962]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 19:59:11 sddm[1750]: Auth: sddm-helper (--socket /tmp/sddm-auth-a8fcba0c-1b2e-4f2b-ac61-0cfb93996f24 --id 4 --start /usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--KYJnXc --theme /usr/share/sddm/themes/WhiteSur-dark --user sddm --display-server kwin_wayland --no-global-shortcuts --no-lockscreen --inputmethod plasma-keyboard --locale1 --greeter) crashed (exit code 1)
May 07 19:59:11 systemd[1962]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 19:59:11 systemd[1962]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 19:59:11 systemd[1962]: plasma-kwin_wayland.service: Consumed 11.233s CPU time over 54.606s wall clock time, 442.5M memory peak.
-- Boot 6fe44f29d53144feba74e636ce48a07d --
-- Boot a6dd6c632d4a4d9c8bb9e757cb221d6a --
May 07 20:00:35 sddm-helper-start-wayland[1821]: Stopping... "kwin_wayland"
May 07 20:00:36 systemd[1958]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 20:00:36 systemd[1958]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 20:01:32 systemd[1958]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 20:01:32 systemd[1958]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 20:01:32 systemd[1958]: plasma-kwin_wayland.service: Consumed 7.211s CPU time over 55.749s wall clock time, 435.6M memory peak.
-- Boot 0a801667044740858a83816d67d51ac2 --
-- Boot 4c3217ff3425483080e8450f964694c0 --
May 07 20:02:59 sddm-helper-start-wayland[1816]: Stopping... "kwin_wayland"
May 07 20:03:00 systemd[1956]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 20:03:00 systemd[1956]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 20:04:52 rsyslogd[1732]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 20:11:20 sddm[1745]: Auth: sddm-helper (--socket /tmp/sddm-auth-1e342c07-1f58-40c5-9721-b09699bd29c1 --id 4 --start /usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--VyWQkT --theme /usr/share/sddm/themes/WhiteSur-dark --user sddm --display-server kwin_wayland --no-global-shortcuts --no-lockscreen --inputmethod plasma-keyboard --locale1 --greeter) crashed (exit code 1)
May 07 20:11:20 systemd[1956]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 20:11:20 systemd[1956]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 20:11:20 systemd[1956]: plasma-kwin_wayland.service: Consumed 1min 11.201s CPU time over 8min 20.390s wall clock time, 480.4M memory peak.
-- Boot 30738952ee764fb98e4627f162896379 --
May 07 20:12:32 sddm-helper-start-wayland[1828]: Stopping... "kwin_wayland"
May 07 20:12:33 systemd[1976]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 20:12:33 systemd[1976]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 20:14:34 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 20:36:58 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 20:53:10 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 20:59:34 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 21:05:31 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 21:21:26 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 21:28:09 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 21:51:33 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 22:02:42 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 22:07:53 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 22:29:49 rsyslogd[1741]: imjournal from <fedora:kwin_wayland>: begin to drop messages due to rate-limiting
May 07 22:36:13 sddm[1755]: Auth: sddm-helper (--socket /tmp/sddm-auth-ba4a6e39-3706-4fbb-8c87-9180ddd5da7a --id 4 --start /usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--XGnUTf --theme /usr/share/sddm/themes/WhiteSur-dark --user sddm --display-server kwin_wayland --no-global-shortcuts --no-lockscreen --inputmethod plasma-keyboard --locale1 --greeter) crashed (exit code 1)
May 07 22:36:14 systemd[1976]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 07 22:36:14 systemd[1976]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 07 22:36:14 systemd[1976]: plasma-kwin_wayland.service: Consumed 31min 51.890s CPU time over 2h 23min 40.514s wall clock time, 841.3M memory peak.
-- Boot 982f93bf35ad4cd59afa4b1cc70b9757 --
May 15 20:29:51 sddm-helper-start-wayland[1837]: Stopping... "kwin_wayland"
May 15 20:29:52 systemd[1983]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 15 20:29:52 systemd[1983]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 15 20:34:12 systemd[1983]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 15 20:34:13 systemd[1983]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 15 20:34:13 systemd[1983]: plasma-kwin_wayland.service: Consumed 11.764s CPU time over 4min 20.295s wall clock time, 431.6M memory peak.
-- Boot e566f84c0d8346788d7ead94d3effcbf --
-- Boot 6add793779e246869421fddc8a4db721 --
May 15 20:41:31 sddm-helper-start-wayland[14386]: "kwin_wayland_drm: Atomic modeset test failed! Eri\xC5\x9Fim engellendi\nkwin_core: Applying output configuration failed!\n"
May 15 20:41:31 sddm-helper-start-wayland[14386]: Stopping... "kwin_wayland"
May 15 20:41:31 systemd[14533]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 15 20:41:31 systemd[14533]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 15 20:46:54 systemd[14533]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 15 20:46:55 systemd[14533]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 15 20:46:55 systemd[14533]: plasma-kwin_wayland.service: Consumed 41.606s CPU time over 5min 23.506s wall clock time, 391.9M memory peak.
May 15 20:47:33 sddm-helper-start-wayland[21015]: Stopping... "kwin_wayland"
May 15 20:47:34 systemd[21376]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 15 20:47:34 systemd[21376]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
May 15 20:49:23 sddm[14311]: Auth: sddm-helper (--socket /tmp/sddm-auth-b0484a3b-e608-46b0-b8ab-e1e93a09fa69 --id 6 --start /usr/bin/sddm-greeter-qt6 --socket /tmp/sddm--NYGRAs --theme /usr/share/sddm/themes/WhiteSur-dark --user sddm --display-server kwin_wayland --no-global-shortcuts --no-lockscreen --inputmethod plasma-keyboard --locale1 --greeter) crashed (exit code 1)
May 15 20:49:24 systemd[21376]: Stopping plasma-kwin_wayland.service - KDE Wayland Compositor...
May 15 20:49:24 systemd[21376]: Stopped plasma-kwin_wayland.service - KDE Wayland Compositor.
May 15 20:49:24 systemd[21376]: plasma-kwin_wayland.service: Consumed 14.136s CPU time over 1min 49.624s wall clock time, 658.1M memory peak.
-- Boot b4523c7cf5094540bf2e37ee2097e6eb --
May 15 20:50:12 sddm-helper-start-wayland[1832]: Stopping... "kwin_wayland"
May 15 20:50:13 systemd[1969]: Starting plasma-kwin_wayland.service - KDE Wayland Compositor...
May 15 20:50:13 systemd[1969]: Started plasma-kwin_wayland.service - KDE Wayland Compositor.
modinfo -l nvidia This command did not return an error.
berguven@fedora:~$ modinfo -l nvidia
Dual MIT/GPL
unfortunately that does not show anything useful.
pls reproduce the issues with the stuttering and freezing on the second screen
- remove the line in /etc/environment
- restart and reproduce the errors
- then run
journalctl --no-hostname --no-pager -b |fpaste
and please post the url.
here it is…
May 15 21:23:44 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
May 15 21:24:01 sddm-helper-start-wayland[1834]: "kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.\nkwin_scene_opengl: Invalid framebuffer status: \"GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT\"\n"
May 15 21:24:01 sddm-helper-start-wayland[1834]: "kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.\n"
May 15 21:24:01 sddm-helper-start-wayland[1834]: "kwin_scene_opengl: Invalid framebuffer status: \"GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT\"\n"
May 15 21:24:01 sddm-helper-start-wayland[1834]: "kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.\nkwin_scene_opengl: Invalid framebuffer status: \"GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT\"\n"
May 15 21:24:01 sddm-helper-start-wayland[1834]: "kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.\nkwin_scene_opengl: Invalid framebuffer status: \"GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT\"\n"
Yes, I noticed that too whilst looking into it, but what’s the solution?
It’s a nvidia driver bug, please report Linux - NVIDIA Developer Forums
sudo nvidia-bug-report.sh
creates a file that you can attach to the bug report.
There may be a patch, that rpmfusion uses on 580.xx drivers for pascal GPUs.
It seems to be the same issue with hw cursors.
@sergiomb , looks like current 590 595 drivers are causing a similar issue on some systems.
Thank you so much for your help, mate. I’ll have a go on the NVIDIA Forum.
check again tomorrow, maybe there is a patched version that you could test.
Having looked into it a bit, it seems to be a problem that’s been around for a while. Some people experienced this issue in Fedora 43 back in March, others in Arch in April, and I’m experiencing it now in May. It seems they aren’t trying to fix it; in fact, some say the situation is getting worse by the day.
In fact, there are even people experiencing this problem in 2024.
But for now, until a permanent solution is found, I’m thinking of using KWIN_FORCE_SW_CURSOR=1.
let me try something… give me an hour
see the link in the priv. message and instructions.
SW cursor is lagging. It may be better to switch to X11 instead.
Ah, here the problem is with NVIDIA 595 and not with 580xx. , yes https://forums.developer.nvidia.com/t/kernel-null-pointer-dereference-when-using-the-580-142-driver/363409/9 in the last comment the same thing is mentioned.