Hi i have this problem from plasma 5 and now on plasma 6 is same. some times when i suspend system or system suspend automatic after timeout. and wake my system up my second display that connected via vga port get the smallest resolution 640x480 and even monitor name change to DP-1 and i can not back that to default without disconnect cable and reconnect then resetting that in kde system settings its only happend on lockscreen i try sddm but it's not happend. i have hybrid gpus intel 520 mesa and nvidia 940mx with propriety driver. i disable nvidia-resume and nvidia-suspend because with those i get blackscreen every time on my both monitor SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.9 zen / 6.0.1 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2
Not a critical issue as there's no data loss; downgrading severity. Does this happen on X11, or Wayland, or both?
.
(In reply to Nate Graham from comment #1) > Not a critical issue as there's no data loss; downgrading severity. > > Does this happen on X11, or Wayland, or both? I use wayland and it's most of the time happend on wayland last time i try x11 was on plasma 5.27.10 and if i wasn't wrong never happend
OK i try x11 and on x11 desktop a little bit faster load than lock screen so you can see every things on desktop after a sec lock screen came up its wired, it wasn't happend in plasma 5 and about resolution nothing change but window on second display unable to close or minimize with buttons after i maximize with double click on title bar i can use that buttons
Can you please use punctuation and proper English sentences, and also stick to a single topic? Otherwise it's very difficult to tell what you're saying and unfortunately the bug report will not be actionable. Does this issue happen if you plug the affected screen into a different physical port on one of your GPUs? Or does it only happen when the screen is plugged into a VGA port?
(In reply to Nate Graham from comment #5) > Can you please use punctuation and proper English sentences, and also stick > to a single topic? Otherwise it's very difficult to tell what you're saying > and unfortunately the bug report will not be actionable. > > Does this issue happen if you plug the affected screen into a different > physical port on one of your GPUs? Or does it only happen when the screen is > plugged into a VGA port? ok sorry. my second monitor is old and only support vga and I don't use much hdmi port to tell about that
This sounds like a driver bug, it probably fails to read the EDID. To confirm that, please attach the output of drm_info when the resolution is correct, and again when the resolution is wrong.
Created attachment 167298 [details] after happend
Created attachment 167299 [details] before happend
(In reply to Zamundaaa from comment #7) > This sounds like a driver bug, it probably fails to read the EDID. To > confirm that, please attach the output of drm_info when the resolution is > correct, and again when the resolution is wrong. i make attachments for them. i didn't found drm_info in my system so i install that from aur i hope it was what you need
*** Bug 483028 has been marked as a duplicate of this bug. ***
(In reply to Nate Graham from comment #11) > *** Bug 483028 has been marked as a duplicate of this bug. *** Is there any hope this fix on next update
Sorry, I got a bit sidelined here. In your drm_info output, I see │ │ ├───1600x900@60.00 preferred driver phsync pvsync │ │ ├───1280x1024@60.02 driver phsync pvsync │ │ ├───1152x864@75.00 driver phsync pvsync │ │ ├───1024x768@75.03 driver phsync pvsync │ │ ├───1024x768@60.00 driver nhsync nvsync │ │ ├───832x624@74.55 driver nhsync nvsync │ │ ├───800x600@75.00 driver phsync pvsync │ │ ├───800x600@60.32 driver phsync pvsync │ │ ├───800x600@56.25 driver phsync pvsync │ │ ├───640x480@75.00 driver nhsync nvsync │ │ ├───640x480@59.94 driver nhsync nvsync │ │ └───720x400@70.08 driver nhsync pvsync as the mode list when it's correct, and │ │ ├───640x480@59.94 preferred driver nhsync nvsync │ │ ├───1024x768@60.00 driver nhsync nvsync │ │ ├───800x600@60.32 driver phsync pvsync │ │ ├───800x600@56.25 driver phsync pvsync │ │ └───848x480@60.00 driver phsync pvsync when it's wrong. So the driver changes the mode list, and we can't do anything about that - it's a driver bug. Please report it at https://forums.developer.nvidia.com/c/gpu-graphics/linux
(In reply to Zamundaaa from comment #13) > So the driver changes the mode list, and we can't do anything about that - sorry i reopen this, It's not driver issue i install gnome desktop and it's never happened i try many times (i suspend in gdm with second display connected or in gnomeshell) and it's only happened on plasma i use latest gnome 46
Working as expected on GNOME doesn't mean it's not a driver bug. The features of drivers can be used in different ways by different compositors. It's quite possible we're hitting this bug because we're using a feature of the driver that happens to be buggy, and GNOME's Mutter is using a different feature that's not buggy in the same way.