Hi! I fixed this problem by deleting the
~/.local/share/kscreen/ folder, and restarted my pc. Now my second display works!
Hi! I fixed this problem by deleting the
Nevermind, after the computer got into lock mode, and i typed in my password, the second display won’t work anymore.
Coming back to this thread because I think I did actually face the issue you were dealing with while I was testing out another monitor (turns out none of the previous issues I had were remotely technically related to yours). When I plugged my main display back in, nothing came through. I tried enabling the monitor in the settings, but no dice. Not even a reset could help. But once I deleted the kscreen folder and reset, everything was back to how it was before. I guess you can just delete that folder everytime you face this issue (even though this apparently happens when your computer goes into lock mode, it doesn’t occur for me even after a reset), and you’ll be good until an update hopefully eventually rolls around fixing this.
Thanks, I’ll use this as the solution temporarily until a update comes out to fix it.
So, I installed the lts kernel, and deleted the kscreen folder, restarted, and now it apparently works??? It dosen’t stop working after the lock screen pops up.
And there it happened again. This is very random so i won’t post anymore on this post until the problem is fixed.
Are you using an AMD Ryzen CPU? Found two other forum posts with similar issue. Seems plasma needs to iron out a new bug but wondering if it affects only amd users.
Yes, I am using an AMD Ryzen CPU. Specifically AMD Ryzen 5800X.
Hopefully gets fixed soon. Maybe worth submitting a bug report to KDE, the more people do it the faster it will hopefully get fixed. Why it affects AMD is strange, if it is related. I would try main and lts kernels. If problem persist might really be related to recent plasma update.
The problem persists on both main and lts kernels, I will see if i can send a bug report to KDE.
Plasma has now released a new version with some fixes, I will use it and mark this post as fixed if it works now.
Still no luck for me. My system recognizes that there’s another screen, but once I enable it, there’s just a black area added to my main display. I can actually move my whole desktop like the map in an RTS game, by hitting the screen’s edges with my cursor. The second display that I just enabled in the settings, though? Still no signal.
KDE Plasma 5.26.1 with Nvidia and Intel here.
I have opened a kde bug report, and it got merged with multiple others.
An easier temporary fix instead of deleting the kscreen folder, is to find out what your displays are called with
xrandr | grep connected, and issuing the following command
Note that in your case the
--right-of flag may be
--left-of depending on where your second display is.
HDMI-0 with what your xrandr identifies your second display as.
DP-0 with your main display.
--rate you put your screens refresh rate (most commonly 60)
xrandr --output HDMI-0 --right-of DP-0 --rate 144 --mode 1920x1080
Then, the screen will be working temporarily.
Just wondering if you could then use
autorandr to save that profile and start it automatically by placing the command
autorandr --change, similar to what I use for i3wm.
Not sure where you do this in KDE with sddm, perhaps
~/.xprofile or similar in the user home folder.
Until reboot or logout/in?
Well, It’s really random. Sometimes the screen dosen’t work after the computer has been in lock mode on sddm, and sometimes after restart.
Perhaps the idea I posted above could work because it automatically recognizes your current monitor layout you saved upon login from your display manager. I also use this on other wm like dwm and qtile. It simply uses xrandr and starts this profile at login. But autorandr is a bit easier/flexible to my opinion.
That would probably work.
The direct instructions are here. It’s also similar to arandr, but I personally prefer autorandr…
It’s also in the arch repo and can be installed with
sudo pacman -S autorandr