Chromium stopped understanding HiDPI in GNOME?Wayland

[Richard]

On upgrade to 55.0.2883.87-0ubuntu1.16.10.1330
Chromium stopped understanding that it was on a low DPI display in a HiDPI environment
- impact: all fonts 2x too high
- this used to work
- getaround: launch like: chromium-browser --force-device-scale-factor=0.5
  - causes chrome and popups to be 50% too small
  - browsed content is correct size on low DPI displays

Chromium also decides to launch all windows on display 3, which is the lowest resolution display
- It used to open windows at the location they were last at

I think this worked in 55.0.2883.87-0ubuntu0.16.10.1328
It certainly worked in 53.0.2785.143-0ubuntu1.1307

dpkg --status chromium-browser | egrep "^(V|Pa)"
Package: chromium-browser
Version: 55.0.2883.87-0ubuntu1.16.10.1330

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: chromium-browser 55.0.2883.87-0ubuntu1.16.10.1330
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
DRM.card0-DP-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-DP-2:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAQrGNATDk1MAUWAQOAQCh46o2FrU81sSUOUFSlSwBxT4EAgYCpQNEA0UABAQEB4mgAoKBALmAwIDYAgZEhAAAaAAAA/wBQSDVOWTIyMjA1OUwKAAAA/ABERUxMIFUzMDExCiAgAAAA/QAxVh1xHAAKICAgICAgAMc=
 modes: 2560x1600 1920x1440 1920x1200 1600x1200 1280x1024 1280x1024 1280x800 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400
DRM.card0-HDMI-A-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAEchck6AEAADIQAQOANCB4Ku+Vo1RMmyYPUFS/7wBhRnFAcU+BT4GAqUCzANEAKDyAoHCwI0AwIDYABkQhAAAaAR2AGHEcFiBYLCUABkQhAACeAAAA/QAxSw9QEQAKICAgICAgAAAA/ABBY2VyIEFMMjQxNlcKAS4CAQQAAR0AclHQHiBuKFUABkQhAAAejArQiiDgLRAQPpYABkQhAAAYjAqgFFHwFgAmfEMABkQhAACYAR2A0HIcFiAQLCWABkQhAACejArQkCBAMSAMQFUABkQhAAAYAR0AvFLQHiC4KFVABkQhAAAeAAAAAAAAAAAAAAAAAAAAWg==
 modes: 1920x1200 1920x1080i 1920x1080i 1920x1080i 1600x1200 1680x1050 1280x1024 1280x1024 1280x960 1152x864 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 1024x768 1440x480i 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAGECmgAAAAADIXAQSlHRJ4Am+xp1VMniUMUFQAAAABAQEBAQEBAQEBAQEBAQEB4mgAoKBALmAwIDYAHrMQAAAaAAAA/ABDb2xvciBMQ0QKICAgAAAAEAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAAAAE8=
 modes: 2560x1600
Date: Fri Dec 30 20:09:09 2016
Desktop-Session:
 'gnome-wayland'
 '/etc/xdg/xdg-gnome-wayland:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
 '/usr/share/gnome-wayland:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
Env:
 'None'
 'None'
Load-Avg-1min: 2.78
Load-Processes-Running-Percent: 0.1%
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic root=/dev/mapper/C89-RFS ro i915.enable_rc6=0
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to yakkety on 2016-11-16 (44 days ago)
dmi.bios.date: 10/26/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B15.1510261437
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B15.1510261437:bd10/26/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
etcconfigcpepperflashpluginnonfree:
 flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
 flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"`
 CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion"
gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.chromium-browser.default: [modified]
modified.conffile..etc.default.chromium-browser: [deleted]
mtime.conffile..etc.chromium-browser.default: 2016-04-19T12:23:06.859241

[Olivier Tilloy (osomon)]

@Richard: has this bug been corrected in more recent versions of chromium (the latest release in the ubuntu repositories is 60.0.3112.78)?

Note that this bug was initially reported on Ubuntu 16.10 which has reached end of life and is not supported any longer, so if you haven't done so already, you will want to upgrade to zesty (17.04) in order to get the latest chromium package.

[Launchpad Janitor (janitor)]

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]