-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panel appears on wrong display after sleep #444
Comments
Hey Aral, please make sure to use descriptive bug titles. It makes it harder to triage issues when the descriptions aren't clear |
I also often experience this issue after a suspend. The panel appears partly on the left (secondary) screen. It's width is that of the wider right (primary) screen, meaning it partly overlaps the right (primary) screen. It doesn't always happen. I'll try to look into this further. Any tips on debugging this are appreciated. Build in display: 2256x1504 (left) I often manually initiate suspend through the applications menu. The external monitor isn't disconnected during suspend. After a reboot the wingpanel appears normally. I often use xrandr to use display scaling, because the Framework laptop screen has a terrible resolution, but this also happens when I don't do this. Because I had issues just killing wingpanel in the past I often just move the build-in display to a different location relative to the Dell Inc. display in the Display settings to fix the wingpanel position. Using Scaling factor: HiDPI (2x). |
What Happened?
Honey, I just woke up like this :)
(Main display: 4K, laptop screen 1080p. This is what the screen looked like when it woke from screen. I opened the menu manually afterwards to show that it was active.)
Steps to Reproduce
First time I’m seeing this particular layout bug.
Expected Behavior
It should lay out properly when returning from sleep.
OS Version
6.x (Odin)
Software Version
Latest release (I have run all updates)
Log Output
No response
Hardware Info
No response
The text was updated successfully, but these errors were encountered: