Regression: text scaling factor lost for GNOME Shell when logging out
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
As of a few weeks ago or so, GNOME Shell loses the text scaling factor (it's set back to 1) when logging out and logging back in again. It is preserved for other programs, just not the shell (top bar, menus, dash). Setting it to another value and then back to the desired value changes it until the next log out. I tried with a new user account and a second machine, and I see the same thing.
Steps to reproduce:
1. Set a text scaling factor. (Something larger is easier to notice the change for.)
$ gsettings set org.gnome.
2. Notice apps and the shell have larger fonts now.
3. Log out and log back in (or restart).
4. Notice now that the top bar and other parts of the Shell are back to a scale factor of 1, while other apps still have larger fonts.
5. Change the text scaling factor to something else (like 1) and then back to the desired number.
$ gsettings set org.gnome.
$ gsettings set org.gnome.
6. Now the Shell does have large fonts, until step 3 is repeated.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-
ProcVersionSign
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 9 17:10:02 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-01 (160 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
RelatedPackageV
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
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.