-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Display changes lead to weird Xorg behaviour #9507
Comments
See the top of this guide -> https://www.qubes-os.org/doc/gui-troubleshooting/ |
On 10/13/24 12:12, Foppe wrote:
See the top of this guide -> https://www.qubes-os.org/doc/gui-troubleshooting/
Hm, interesting. I had never needed that, but it was working ~2-3 months ago.
Anyway I just tried it with (2560*1440 + 1920*1080)*4/1024 = 22500 as I have a 2k and a FHD monitor, but it unfortunately did not resolve the issue.
|
That's not enough, it's about rectangle covering them all. See the xrandr output (or the long xrandr command in the doc) to get the accurate number easily. |
The xrandr command returns 14400, i.e. even less.
But ok, I'll try the rectangle covering it all, i.e. |
No, that still didn't fix the issue. :( |
Btw I mirror the displays (and the larger one is sometimes disconnected) instead of extending them, i.e. 14400 is probably indeed the correct value. Nonetheless that value doesn't work either: |
How to file a helpful issue
Qubes OS release
4.2
Brief summary
Switching to a different display leads to areas of the new display becoming unusable. Clicking on certain areas leads to clicks on other areas of the screen.
Steps to reproduce
Expected behavior
Mouse clicks happen where the mouse is pointed at.
Actual behavior
Mouse clicks happen elswhere.
Notes
sys-net
to re-gain access to the tray icon functionality).The text was updated successfully, but these errors were encountered: