Ubuntu
gnome-shell package

Scaling resets on gnome shell after reboot (Scaling is still set to 1.20 in Gnome Tweaks but the shell displays like 1.0)

Bug #1896092 reported by Hrishikesh Gogoi on 2020-09-17

This bug report is a duplicate of: Bug #1892440: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-shell (Ubuntu)	New	Undecided	Unassigned

Bug Description

Gnome shell(top bar, notifications etc) shows very small text on 15.6 inch laptop after reboot. Text-Scaling is still set to 1.20 in Gnome Tweaks but the shell displays like 1.0. But if we again change the scaling in tweaks it gets okay and again after reboot it goes back to 1.0

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 17 22:43:10 2020
DisplayManager: gdm3
ProcEnviron:
LANGUAGE=en_IN:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_IN
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Hrishikesh Gogoi (hrishikesh27) wrote on 2020-09-17:

Dependencies.txt Edit (21.9 KiB, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ShellJournal.txt Edit (20.6 KiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2020-09-18:

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 1892440, 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.