this post was submitted on 10 Jul 2025
8 points (100.0% liked)

Linux 101 stuff. Questions are encouraged, noobs are welcome!

1396 readers
1 users here now

Linux introductions, tips and tutorials. Questions are encouraged. Any distro, any platform! Explicitly noob-friendly.

founded 2 years ago
MODERATORS
 

I have a 144Hz ultrawide monitor, and recently I bought another little monitor for music/Discord. However, even though I'm running it on Wayland, If I try to change the framerate of the big monitor in KDE settings, it spits out an error (something about the framerate not being compatible with the driver - unfortunately I can't check it anymore) and doesn't change it. This is on Arch running the latest plasma-meta, and an AMD GPU.

I've tried looking for a solution to this problem, but practically all of them just say "use Wayland", which I already am. I found a Debian Bookworm USB I had lying around and thought I'd see if the issue persisted. It turns out that it doesn't - It works perfectly.

Does anybody have any ideas as to why this doesn't work on a newer version of Plasma?

I'm not necessarily against switching to Debian to get this working, it's just that Arch is what I'm used to.

top 2 comments
sorted by: hot top controversial new old
[โ€“] Cort@lemmy.world 2 points 2 months ago* (last edited 2 months ago)

I have a 60hz and 144hz monitors on my desk, and I've found that sometimes the frame rate only changes for the monitor where the settings window was opened from.

If you right click on the desired monitor's desktop and change screen settings/refresh rate from there, it'll actually work, usually.

[โ€“] First_Thunder@lemmy.zip 1 points 4 months ago

It could be some temporary regression, either on AMD or plasma side?