Since 0.51.1 update, external monitor comes back from DPMS at low resolution #11816
-
|
I'm on a laptop (Framework 13) with a HiDPI primary display and an external monitor (TV actually) plugged in via HDMI on an external USB-C based port adapter. This arrangement worked fine using the following config: This arrangement also still works now on first boot or any time I unplug and reattatch the external monitor. The issue is every time that since upgrading from 0.15.0 to 0.15.1 (I'm the Arch Linux package maintainer), every time the external display gets sent to sleep via DPMS it comes back on at low resolution (something like 680p instead of 1080p). This is managed via hypridle like so: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
only thing I could imagine doing this would be 941f35c Can you pass a log from the bug happening, or try to revert this one commit? |
Beta Was this translation helpful? Give feedback.
-
|
I'm going to mark this as closed for now because I can't reproduce it myself today. It is possible that I updated packages for Hyprland and then never restarted Wayland. Having done a reboot (for a kernel update) today, I tried turning on logging and replicating this problem and an unable to do so. Given it happened 5+ times in a row before, obviously something changed in the mean time and I suspect it might have to do with an old Wayland session being paired with newer on-disk linked libraries. Unless I or somebody else has this problem again to debug, there is nothing actionable here. |
Beta Was this translation helpful? Give feedback.
I'm going to mark this as closed for now because I can't reproduce it myself today.
It is possible that I updated packages for Hyprland and then never restarted Wayland. Having done a reboot (for a kernel update) today, I tried turning on logging and replicating this problem and an unable to do so. Given it happened 5+ times in a row before, obviously something changed in the mean time and I suspect it might have to do with an old Wayland session being paired with newer on-disk linked libraries. Unless I or somebody else has this problem again to debug, there is nothing actionable here.