In Kscreen, trying to change the positioning, resolution, or nearly any setting of my secondary monitor causes the image displayed on the second monitor to be forcibly skewed, with the image of Plasma being stretched past the bounds of the monitor and black space is shown on the edges. If this happens, I have to end my session and log back in to Plasma to fix it.
Hi Buck, Thanks for the report! Could you generate some debugging information, which will hopefully help to narrow down the problem? Here's a small guide: https://community.kde.org/Solid/Projects/ScreenManagement Also, could you try killing (using kquitapp5) and restarting "plasmashell" when the display is distorted and see if that works around your problem?
Created attachment 100154 [details] kscreen .local file
Killing plasmashell doesn't work, the entire session has to be terminated. Output of kscreen-console bug: https://paste.kde.org/puowkrpni Output of kcmshell5 kcm_kscreen: https://paste.kde.org/pcl9lp8v6
can you try to disable compositing with Alt+Shift+F12 when the problem occurs? Does that fix the problem?
(In reply to Martin Gräßlin from comment #4) > can you try to disable compositing with Alt+Shift+F12 when the problem > occurs? Does that fix the problem? No. When I changed my display settings to cause the problem, KDE notified me that compositing settings had been reset due to a change in configuration. Pressing Alt+Shift+F12 would make it so nothing on my screen was movable or even usable.
> KDE notified me that compositing settings had been reset oh that's interesting. So probably this dialog: "Desktop effects were restarted due to a graphics reset" This means that the driver was not able to handle the situation properly and performed a "reset". That's probably very related to the problems you see and might indicate that they are rather in the X-Server and/or drivers. To verify: please have a look into /var/log/Xorg.0.log for anything which looks suspicious (e.g. warnings when changing screens). Also please provide the output of: * qdbus org.kde.KWin /KWin supportInformation * glxinfo -l
I changed my display settings to force the problem to happen and this is the output: https://paste.kde.org/pr1fgg136 The very bottom line is, what I believe to be, the display changing. This is the output for the qdbus command: https://paste.kde.org/ppkhz0euu And this is the output for the glxinfo command: https://paste.kde.org/ppjm68tkt Both of the commands were run while the issue was occurring.
That looks all fine: * xorg log doesn't have warnings * kwin debug output is correct - it detected the screens as printed in xorg log, compositor is active and happy * glxinfo doesn't show any "bad" limits My assumption currently is that also Plasma (and other applications) get the graphics reset from the NVIDIA driver. If that's the case you don't need to restart the complete session. A kquitapp5 plasmashell plasmashell from e.g. KRunner should also fix it.
(In reply to Martin Gräßlin from comment #8) > That looks all fine: > * xorg log doesn't have warnings > * kwin debug output is correct - it detected the screens as printed in xorg > log, compositor is active and happy > * glxinfo doesn't show any "bad" limits > > My assumption currently is that also Plasma (and other applications) get the > graphics reset from the NVIDIA driver. If that's the case you don't need to > restart the complete session. A > kquitapp5 plasmashell > plasmashell > > from e.g. KRunner should also fix it. See Comment 3. I don't know why, but a complete session restart works. However, I just realized, the only way to make the screen reset after restarting the session is disabling the Kscreen 2 startup service. I don't know if that is impacting these results.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!