Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55701 - [gnome-shell] DPI scaling reset/forgotten after logout

Attached to Project: Arch Linux
Opened by Sebastiaan Lokhorst (lonaowna) - Thursday, 21 September 2017, 21:33 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 08 October 2017, 15:58 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I set the right display scaling (2x for me) in Display Settings, everything looks nice. After I relogin, the settings seems to be forgotten and scaling is back at 1x.

This was fine before in GNOME 3.24, but broken since 3.26 (currently in [gnome-unstable]). I use GNOME on Xorg, launched from GDM, with the NVIDIA driver.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 08 October 2017, 15:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  OP requested: seems to be mostly fixed after 3.26.1; remaining issues are upstream
Comment by Sebastiaan Lokhorst (lonaowna) - Thursday, 21 September 2017, 21:44 GMT
I just noticed that after I've selected the right DPI in Display Settings and closed the window, after a few minutes the DPI is reset to 1x. So it doesn't only happen on logout.

Forgot to mention the exact packages I'm using:
gnome-shell 3.26.0+14+g9f0bb526f-1
mutter 3.26.0+6+g26cd031be-2
Comment by Jan de Groot (JGC) - Thursday, 21 September 2017, 21:53 GMT
Probably https://bugzilla.gnome.org/show_bug.cgi?id=787477 upstream

Git master has fixes for this.
Comment by Sebastiaan Lokhorst (lonaowna) - Thursday, 21 September 2017, 22:09 GMT
Ah yes, that looks like it. I also recognize some of the other problems.

Should I try to build master myself, or are you going to bump the package anyway?
Comment by Sebastiaan Lokhorst (lonaowna) - Thursday, 21 September 2017, 22:20 GMT
Hm, I just tried mutter at commit f0c6c4eb1fa2b21e3806a31bbae0f210b029907e (current master), but that doesn't seem to fix it.

Edit: commented upstream that I still have the problem with git master

Loading...