[nvidia] 175% fractional scaling on X11 results in often unaccessible desktop after suspend / re-login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mutter (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
Having enabled fractional scaling on X11, I have a lot of issues with returning to a hw-suspended session, re-login screen becomes a black rectangle, and windows are being resized and there are black rectangular artifacts and a lot of weird stuff with resizing going on. Sometimes I am able to reach the login screen, but often I have to killall -HUP gnome-shell from the terminal. I will try to attach X logs etc when this happens again.
Which are the most relevant log files to look into?
Ubuntu 19.04, gnome-shell 3.32.0, mutter 3.32.0+
Screen at 3840x2160 and 175% scaling
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2018-07-04 (310 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NonfreeKernelMo
Package: mutter 3.32.0+
PackageArchitec
ProcVersionSign
Tags: disco
Uname: Linux 5.0.0-13-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-04-17 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
mtime.conffile.
summary: |
- 175% fractional scaling on X11 results in often unaccessible desktop - after suspend / re-login + [nvidia] 175% fractional scaling on X11 results in often unaccessible + desktop after suspend / re-login |
Changed in mutter (Ubuntu): | |
status: | Incomplete → New |
importance: | Undecided → High |
tags: | added: xrandr-scaling |
tags: | added: resume suspend-resume |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1809407, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.