** Description changed:
+ [ Impact ]
+
scaling changes when closing/re-opening the lid. Seen in bionic.
- Mz scaling is set to 100%, but the laptop is considered highdpi by
+ My scaling is set to 100%, but the laptop is considered highdpi by
mutter, and during suspend/resume it changes back to default ignoring
settings.
$ xprop -spy -root RESOURCE_MANAGER
[...]
RESOURCE_MANAGER(STRING) =
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
RESOURCE_MANAGER(STRING) =
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"
xrandr
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y
axis) 309mm x 174mm
2560x1440 60.00*+ 59.99 59.99 59.96 59.95
+
+ [ Test case ]
+
+ In a laptop with HiDPI screen, force the scaling to 1:
+
+ Run this and close the lid:
+ xprop -spy -root RESOURCE_MANAGER
+
+ Once reopened the value should not change and if it does the
+ `Xft.dpi:\t96` value should stay constant, and not change to 192.
+
+ [ Regression potential ]
+
+ Wrong resolution is set for the laptop lid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1793496
Title:
scaling changes when closing/re-opening the lid
Status in Mutter:
New
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Bionic:
Confirmed
Status in mutter source package in Focal:
Fix Released
Bug description:
[ Impact ]
scaling changes when closing/re-opening the lid. Seen in bionic.
My scaling is set to 100%, but the laptop is considered highdpi by
mutter, and during suspend/resume it changes back to default ignoring
settings.
$ xprop -spy -root RESOURCE_MANAGER
[...]
RESOURCE_MANAGER(STRING) =
"*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n"
RESOURCE_MANAGER(STRING) =
"*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n"
xrandr
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y
axis) 309mm x 174mm
2560x1440 60.00*+ 59.99 59.99 59.96 59.95
[ Test case ]
In a laptop with HiDPI screen, force the scaling to 1:
Run this and close the lid:
xprop -spy -root RESOURCE_MANAGER
Once reopened the value should not change and if it does the
`Xft.dpi:\t96` value should stay constant, and not change to 192.
[ Regression potential ]
Wrong resolution is set for the laptop lid
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1793496/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
