My entire monitor freezes when I adjust the temperature slider

Help
,
1

My entire monitor freezes when I adjust the temperature slider. The only way to fix it was by performing a system reboot. I’m posting here to check if this issue happens only on my system or if others are experiencing it as well. Thank you!

System Information:

2

Hi! I don’t use the feature myself, but just for possible troubleshooting ideas:

  • Does the freeze-up occur if you have the switching times set manually, by chance?
  • Does it occur whether it’s currently day or night, or only if the adjustment happens while the night light is already active?
3

Hello! I’m searching around because I’m encountering a similar issue involving this, as well as maybe something related. (Check my post history for the other post CorrectPoke titled “Some issues with screen lock/sleep and freezing desktop”. I can’t post links because my account is so new.)

The freeze happens whenever I manually adjust the temp, or turn NL on or off AND when doing so causes the temp to change (turning it on or off during daytime does not cause the freeze). I haven’t noticed a freeze during a normal transition, but I’m also dealing with either a related or similar bug (detailed in the post in my history) so I can’t properly troubleshoot this one.

Unless it’s the same bug?

OS: EndeavourOS x86_64
Display (DELD10F): 2560x1440 @ 165 Hz in 31" [External] *
Display (GN246HL): 1920x1080 @ 60 Hz in 24" [External]
DE: KDE Plasma 6.3.3
CPU: AMD Ryzen 7 5800X (16) @ 4.85 GHz
GPU: NVIDIA GeForce RTX 3080 Ti [Discrete]

4

Hmm - to maybe help narrow things down, @LeafOfLuthien2276 do your freeze-up issues disappear if Night Light is completely turned off? Basically, in that other thread, you mentioned turning off both Screen Locking and Night Light, but what if the former is left on - thinking that maybe just Night Light is the culprit?

And @Zakki , can you let us know what graphics card you have, in case there’s a connection there?

5

I left the computer locked and alone since the evening of the 24th. I successfully unlocked it with no issues after disabling Night Light.

Perhaps it is just the Night Light?

6

That does seem like it narrows it down! For you or for @Zakki , does switching to another virtual console (Ctrl+Alt+F3 would usually accomplish that) unfreeze things after a little while?

Could you also check your system journal after the issue occurs? For example, if you triggered the freeze at 4:30 PM today, you could use sudo journalctl --since="2025-03-26 16:29:00" --until="2025-03-26 16:31:00" to look at the surrounding couple of minutes.

I’m asking since I think I can reproduce the issue you’re having, and if it’s the same one, then looking in the system journal should show a ton of lines with:

kwin_wayland_drm: Failed to create a framebuffer:

Followed by a few of:

kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux

Are you seeing that on your device too?

7

Apologies! I’ve been quite occupied the last day.

I unlocked the computer without sleep nor Night Light today with no issued, and then immediately triggered it by turning on NL and adjusting color temp. The freeze happened ~0.5 seconds after.

Mar 28 18:25:33 Artemis systemsettings[176248]: qml: Page SubCategoryPage_QMLTYPE_2(0x621831a3e4f0) is already in the PageRow
Mar 28 18:25:33 Artemis systemsettings[176248]: qml: Pushed pages do not conform to the rules. Please check the documentation.
Mar 28 18:25:33 Artemis systemsettings[176248]: qml: push (file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:223)
                                                onActiveSubCategoryRowChanged (qrc:/qt/qml/org/kde/systemsettings/SubCategoryPage.qml:180)
Mar 28 18:25:38 Artemis systemsettings[176248]: qt.positioning.geoclue2: Unable to obtain the client: "org.freedesktop.DBus.Error.ServiceUnknown" "The n>
Mar 28 18:25:40 Artemis kwin_wayland[938]: kwin_wayland_drm: Pageflip timed out! This is a bug in the nvidia-drm kernel driver
Mar 28 18:25:40 Artemis kwin_wayland[938]: kwin_wayland_drm: Please report this at https://forums.developer.nvidia.com/c/gpu-graphics/linux
Mar 28 18:25:40 Artemis kwin_wayland[938]: kwin_wayland_drm: With the output of 'sudo dmesg' and 'journalctl --user-unit plasma-kwin_wayland --boot 0'

The last three lines repeat.

Ctrl+Alt+F3 fixed the issue, but now NL is on. So I turned it off. This time the issue was fixed again but mouse and keyboard commands no longer worked, CapsLock and NumLock lights also didn’t respond on the keyboard either. I unplugged them both, plugged them in, and then they worked. I ran that sudo command again:

Mar 28 18:28:24 Artemis login[144395]: pam_unix(login:session): session closed for user leaf
Mar 28 18:28:24 Artemis systemd[1]: getty@tty3.service: Deactivated successfully.
Mar 28 18:28:24 Artemis systemd[1]: session-4.scope: Deactivated successfully.
Mar 28 18:28:24 Artemis systemd-logind[695]: Session 4 logged out. Waiting for processes to exit.
Mar 28 18:28:24 Artemis systemd[1]: getty@tty3.service: Scheduled restart job, restart counter is at 1.
Mar 28 18:28:24 Artemis systemd[1]: Started Getty on tty3.
Mar 28 18:28:24 Artemis systemd-logind[695]: Removed session 4.
Mar 28 18:28:24 Artemis kded6[1062]: org.kde.pulseaudio: No object for name "alsa_input.usb-Corsair_CORSAIR_VOID_ELITE_Wireless_Gaming_Dongle-00.mono-fa>
Mar 28 18:28:24 Artemis kded6[1062]: org.kde.pulseaudio: No object for name "alsa_output.usb-Corsair_CORSAIR_VOID_ELITE_Wireless_Gaming_Dongle-00.iec958>
Mar 28 18:28:24 Artemis kded6[1062]: org.kde.pulseaudio: No object for name "alsa_input.usb-Corsair_CORSAIR_VOID_ELITE_Wireless_Gaming_Dongle-00.mono-fa>
Mar 28 18:28:24 Artemis kded6[1062]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Mar 28 18:28:24 Artemis kded6[1062]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Mar 28 18:28:24 Artemis kdeconnectd[1243]: 2025-03-28T18:28:24 org.kde.pulseaudio: No object for name "alsa_input.usb-Corsair_CORSAIR_VOID_ELITE_Wireles>
Mar 28 18:28:24 Artemis kdeconnectd[1243]: 2025-03-28T18:28:24 org.kde.pulseaudio: No object for name "alsa_output.usb-Corsair_CORSAIR_VOID_ELITE_Wirele>
Mar 28 18:28:24 Artemis kdeconnectd[1243]: 2025-03-28T18:28:24 org.kde.pulseaudio: No object for name "alsa_input.usb-Corsair_CORSAIR_VOID_ELITE_Wireles>
Mar 28 18:28:24 Artemis plasmashell[1083]: org.kde.pulseaudio: No object for name "alsa_input.usb-Corsair_CORSAIR_VOID_ELITE_Wireless_Gaming_Dongle-00.m>
Mar 28 18:28:24 Artemis kdeconnectd[1243]: 2025-03-28T18:28:24 org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Mar 28 18:28:24 Artemis kdeconnectd[1243]: 2025-03-28T18:28:24 org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"

There’s a LOT of lines like this talking about me KB+M, This is from the first time I triggered the freeze and when I did Ctrl+Alt+F3. If I paste the command results here for showing how they were fixed, it’ll be a huge wall of text. If you want it, I’m happy to paste it though!

In the mean time it looks like Nvidia is the problem, or at least involved in it. I’ll try rolling back the driver this Sunday. That’ll be a new process on Linux for me, so I want to dedicate a day to experimenting in case I bork the computer.

1 Like
8

this might seem obvious to some; have you tried booting without wayland? Using the boot flag “- -hint-no-wayland”. This solved several plasma issues for me cos perhaps hardware is bad.

9

Success! I only borked my computer twice.

First, re: “- -hint-no-wayland”. I’m specifically using Wayland because I use this computer primarily for gaming. X11 has awful, awful screen tearing as I play.

For the Night Light causing freezes, downgrading from nvidia 570.133.07-2 and nvidia-utils 570.133.07-1 to nvidia-open-dkms 570.86.16-2 and nvidia-utils 570.86.16-2 fixed it. I tried nvidia-dkms, and each version from the current releases before 570.86.16-2 no longer caused the issue.

I suppose that means that either Plasma/Night Light updated and doesn’t play with Nvidia well, or visa versa. I’ll be out of my league troubleshooting Plasma issues, I think, since there’s a lot more moving parts with dependencies if I start rolling that back. I’m going to stick with this downgraded Nvidia for now.

10

Ok, i’m having this same problem. Fresh arch install. will try the downgrades i guess.

11

i didn’t rollback, but found where to set this in my kwinrc…

[NightColor]
Active=true
Mode=Constant
NightTemperature=3500