SUMMARY I have a 1080p 144hz MSI monitor. Sometimes (but not always), when I wake my computer after putting it into suspend, it will be set to 480p. The system settings app does not recognize it as a 1080p monitor, and it cannot be set to 1080p again. Rebooting my computer fixes the issue, and turning my monitor off and back on again also fixes the issue. It appears that this bug only occurs after a few hours of the system being suspended, such as after returning home from work or after waking up in the morning. Simply suspending the system and then immediately turning it back on does not reproduce the bug. STEPS TO REPRODUCE 1. Suspend system 2. Wait for roughly 8 hours 3. Press power button to turn computer back on OBSERVED RESULT The monitor is set to 480p and is no longer recognized as a 1080p monitor by KDE System Settings. EXPECTED RESULT The monitor should be set to 1080p and recognized as such by the System Settings app. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.5.3 KDE Frameworks Version: 6.20.0 Qt Version: 6.10.1 Kernel Version: 6.17.9-zen1-1-zen (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Current known workarounds are to reboot the PC itself and to turn the monitor off and back on again.
Thanks for the bug report. Usually, seeing a 640x480 resolution means the graphics driver is failing to read the EDID from the screen. What GPU do you have? Also, can you paste the output of this command in the report? kscreen-doctor -o Thanks.
GPU is an XFX Radeon 6600XT. I tried to reproduce the bug, but was unsuccessful. Here is the output of the command while the bug has not triggered. (I will do my best to reproduce the bug again and run the command while the bug is active) ❯ kscreen-doctor -o Output: 1 DP-2 7dfb7fe6-2cb9-4c83-a3a6-9c5097df2269 enabled connected priority 1 DisplayPort replication source:0 Modes: 1:1920x1080@60.00! 2:1920x1080@144.00* 3:1920x1080@120.00 4:1920x1080@119.88 5:1920x1080@120.00 6:1920x1080@100.00 7:1920x1080@60.00 8:1920x1080@59.94 9:1920x1080@50.00 10:1680x1050@59.95 11:1280x1024@75.03 12:1280x1024@60.02 13:1440x900@59.89 14:1280x800@60.00 15:1280x720@60.00 16:1280x720@59.94 17:1280x720@50.00 18:1024x768@75.03 19:1024x768@70.07 20:1024x768@60.00 21:800x600@75.00 22:800x600@72.19 23:800x600@60.32 24:800x600@56.25 25:720x576@50.00 26:720x576@50.00 27:720x480@60.00 28:720x480@60.00 29:720x480@59.94 30:720x480@59.94 31:640x480@75.00 32:640x480@72.81 33:640x480@66.67 34:640x480@60.00 35:640x480@59.94 36:640x480@59.94 37:1280x1024@143.79 38:1024x768@143.87 39:1280x800@143.84 40:1600x900@59.95 41:1600x900@143.93 42:1368x768@59.88 43:1368x768@143.77 44:1280x720@143.67 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: Automatic RgbRange: Automatic HDR: disabled Wide Color Gamut: disabled ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 0% and dimming to 100% DDC/CI: allowed Color resolution: automatic (10), range: [8; 16] bits per color Allow EDR: unsupported Sharpness control: unsupported
Thanks for the details. The kscreen-doctor output when the bug happens will also be useful. I've corrected the product and Version First Reported in fields again. Please do not change these.
I was able to trigger the bug again, here is the output of the command while it is active. ❯ kscreen-doctor -o Output: 1 DP-2 9fd6b89d-51e1-49db-9180-2bfe2c271538 enabled connected priority 1 DisplayPort replication source:0 Modes: 1:640x480@59.94*! Geometry: 0,0 640x480 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic HDR: incapable Wide Color Gamut: incapable ICC profile: none Color profile source: sRGB Color power preference: prefer efficiency and performance Brightness control: supported, set to 100% and dimming to 100% Color resolution: automatic (10), range: [8; 16] bits per color Allow EDR: unsupported Sharpness control: unsupported
Thanks for the additional details. The output shows that the only resolution being offered by your graphics driver is 480p, so that's why Plasma is setting your display to that resolution. This has to be fixed in the driver. You can open a bug report about this at [https://gitlab.freedesktop.org/drm/amd/-/issues](https://gitlab.freedesktop.org/drm/amd/-/issues) so the AMD developers can take a look.