You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let me preface this by saying I'm running the nvidia proprietary driver and an ultrawide screen in PIP mode (picture-in-picture), which simulates having two displays. One is connected with DP and the other with HDMI, both connected to the same screen and my nvidia card.
When the screen is turned off by the power manager after some inactivity, the window manager blows up. When the monitors are turned back on, one of the displays is broken and the other stops rendering windows correctly. When windows are moved around, they create this "replication" effect, where instead of moving the window, parts of it are copied into the direction of the move. I don't have screenshots of this since the WM is not usable.
Description
Let me preface this by saying I'm running the nvidia proprietary driver and an ultrawide screen in PIP mode (picture-in-picture), which simulates having two displays. One is connected with DP and the other with HDMI, both connected to the same screen and my nvidia card.
When the screen is turned off by the power manager after some inactivity, the window manager blows up. When the monitors are turned back on, one of the displays is broken and the other stops rendering windows correctly. When windows are moved around, they create this "replication" effect, where instead of moving the window, parts of it are copied into the direction of the move. I don't have screenshots of this since the WM is not usable.
Budgie version
budgie-desktop 10.9.1
Operating System
Arch (
6.8.9-arch1-2 #1 SMP PREEMPT_DYNAMIC x86_64
)Steps to reproduce the issue
Actual result
One of the displays is black, the other isn't rendering windows correctly.
Expected result
Both displays working just fine.
Additional information
rrandr
Xorg.0.log
Xorg.log
budgie-wm
journal entriesbudgie.log
The text was updated successfully, but these errors were encountered: