Personal scaling settings not used on the unlock screen

Bug #1774177 reported by Pedro Côrte-Real
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
New
Undecided
Unassigned
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

https://gitlab.gnome.org/GNOME/gnome-shell/issues/331

---

I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again.

I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 30 13:21:49 2018
InstallationDate: Installed on 2016-10-27 (579 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gdm3
UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago)
mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169

Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The lock screen and login screen graphics are provided by the the gnome-shell package.

I think the problem here may be that some instances may be running as a different user (gdm), so your own personal settings won't apply to those.

summary: - Screen size is wrong on resume from suspend
+ Personal scaling settings not used on the unlock screen
tags: added: hidpi
Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :

But what's strange is that the issue only happens momentarily and when returning from suspend. If I lock the screen it's correct and after a few moments after suspend it's correct again.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please see: https://gitlab.gnome.org/GNOME/gnome-shell/issues/142

and if you think it's not the same issue then please log a new one and let us know the new issue ID.

Changed in gdm3 (Ubuntu):
status: New → Incomplete
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :

This is not the same bug. I can't reproduce it anymore since gdm is no longer slow on resume. But is it really Ubuntu process to have the user submit bug reports upstream?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Yes, upstream requires bug reports from someone who experiences the bug.

Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :

Just had the same thing happen even with gdm not being slow. Flashes for less than a second and now my pointer is at 200% when over the top bar. Trying to take a screenshot resets it again so I can't show it.

Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :
Changed in gdm3 (Ubuntu):
status: Incomplete → New
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
description: updated
Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :

This happens to me 100% of the time now and is extremely annoying. Issues like this have made the 18.04 GNOME transition a clear step back in desktop polish.

Revision history for this message
Pedro Côrte-Real (pedrocr) wrote :

This bug doesn't exist on Wayland. It does seem like GNOME developers don't care about Xorg anymore and these kinds of bugs won't get fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.