Bug#871542: [Pkg-chromium-maint] Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

[Ralf Jung]

Hi,

> > As of Chromium 60.x, the browser UI (address bar, back buttons, etc) is
> > drawn at a disproportionately large size on my MS Surface Pro 3
> > (2160x1440). See this screenshot:
> >
> > https://ssl.tiker.net/nextcloud/index.php/s/ItjkFlldaL0zJpD
> >
> > vs Chromium 59 for comparison:
> >
> > https://ssl.tiker.net/nextcloud/index.php/s/gmn2xQAXvcrQbhW
> 
> This version does not support fractional scale factors:
>  https://bugs.chromium.org/p/chromium/issues/detail?id=723931
> 
> As a workaround, I use --force-device-scale-factor=1.5.
> -- 
> Test input for validity and plausibility.
> - The Elements of Programming Style (Kernighan & Plauger)

I am having the same problem with version 61.0.3163.100-2 on a 4K
screen.  So it doesn't seem like fractional scaling factors are the
problem, it looks more like Chromium applies the scaling factor *twice*.

Kind regards,
Ralf

Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

[Yuri D'Elia]

Package: chromium
Version: 61.0.3163.100-2
Followup-For: Bug #871542

I was also hit by this bug with Chromium 61.
At 2560x1440 the UI is just overblown.

Using an 1.5 scale factor fixes the size to something acceptable, but
only when I'm using the laptop's screen. When booting with an external
screen, the DPI is lower, and thus the environment variable needs to be
changed.

I don't understand why Chromium is not using the reported DPI setting
(values reported by XRandR are correct!) and instead is introducing
another useless scaling factor!

-- System Information:
Debian Release: buster/sid
 APT prefers unstable
 APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  chromium-common  61.0.3163.100-2
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.26.0-2
ii  libavcodec57 10:3.3.4-dmo1
ii  libavformat5710:3.3.4-dmo1
ii  libavutil55  10:3.3.4-dmo1
ii  libc62.24-17
ii  libcairo21.14.10-1
ii  libcups2 2.2.4-7
ii  libdbus-1-3  1.11.18-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.3-1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libgcc1  1:7.2.0-10.0+really6~reproducible1
ii  libgdk-pixbuf2.0-0   2.36.10-2
ii  libglib2.0-0 2.54.0-1
ii  libgtk2.0-0  2.24.31-2
ii  libharfbuzz0b1.4.2-1
ii  libicu57 57.1-6
ii  libjpeg62-turbo  1:1.5.2-2
ii  liblcms2-2   2.8-4
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.16-1
ii  libnss3  2:3.32-2
ii  libopus0 1.2.1-1
ii  libpango-1.0-0   1.40.12-1
ii  libpangocairo-1.0-0  1.40.12-1
ii  libpng16-16  1.6.32-3
ii  libpulse011.1-1
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   7.2.0-10.0+really6~reproducible1
ii  libvpx4  1.6.1-3
ii  libwebp6 0.6.0-3
ii  libwebpdemux20.6.0-3
ii  libwebpmux3  0.6.0-3
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-3
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-4
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2.1
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
pn  chromium-l10n  
pn  chromium-shell 
pn  chromium-widevine  

Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

[gregor herrmann]

On Tue, 05 Sep 2017 20:49:33 +0200, gregor herrmann wrote:

> FWIW, this happens as well on a totally harmless 1920x1080 TFT (no
> HiDPI, no changes with DPI, no gnome(-ttols), ...); and it makes not
> only the UI ugly but also more or less breaks some websites because
> chromium thinks and says it has only about 2/3 of the real screen
> pixels.

# cat /etc/chromium.d/dpi
# #871542
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --force-device-scale-factor=0.75"

makes chromium usable again for me.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Funny van Dannen: Schilddrüsenunterfunktion


signature.asc
Description: Digital Signature

Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

[gregor herrmann]

On Tue, 08 Aug 2017 18:29:13 -0500, Andreas Kloeckner wrote:

> As of Chromium 60.x, the browser UI (address bar, back buttons, etc) is
> drawn at a disproportionately large size on my MS Surface Pro 3
> (2160x1440).

FWIW, this happens as well on a totally harmless 1920x1080 TFT (no
HiDPI, no changes with DPI, no gnome(-ttols), ...); and it makes not
only the UI ugly but also more or less breaks some websites because
chromium thinks and says it has only about 2/3 of the real screen
pixels.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: La Tresca: Caravanserraglio


signature.asc
Description: Digital Signature

Bug#871542: [Pkg-chromium-maint] Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

[Mourad De Clerck]

On Wed, 09 Aug 2017 07:36:45 +0200 Vincent Bernat  wrote:
> This version does not support fractional scale factors:
>  https://bugs.chromium.org/p/chromium/issues/detail?id=723931
> 
> As a workaround, I use --force-device-scale-factor=1.5.

Strange: on my machine it shows the UI by default in
device-scale-factor=3, and I need to use --force-device-scale-factor=2
to get it back to normal. No fractional scale factors required.

-- M

Bug#871542: [Pkg-chromium-maint] Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

[Vincent Bernat]

 ❦  8 août 2017 18:29 -0500, Andreas Kloeckner  :

> As of Chromium 60.x, the browser UI (address bar, back buttons, etc) is
> drawn at a disproportionately large size on my MS Surface Pro 3
> (2160x1440). See this screenshot:
>
> https://ssl.tiker.net/nextcloud/index.php/s/ItjkFlldaL0zJpD
>
> vs Chromium 59 for comparison:
>
> https://ssl.tiker.net/nextcloud/index.php/s/gmn2xQAXvcrQbhW

This version does not support fractional scale factors:
 https://bugs.chromium.org/p/chromium/issues/detail?id=723931

As a workaround, I use --force-device-scale-factor=1.5.
-- 
Test input for validity and plausibility.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature

Bug#871542: chromium: Chromium 60 UI is huge on HiDPI displays

[Andreas Kloeckner]

Package: chromium
Version: 60.0.3112.78-1
Severity: important

Dear Maintainer,

As of Chromium 60.x, the browser UI (address bar, back buttons, etc) is
drawn at a disproportionately large size on my MS Surface Pro 3
(2160x1440). See this screenshot:

https://ssl.tiker.net/nextcloud/index.php/s/ItjkFlldaL0zJpD

vs Chromium 59 for comparison:

https://ssl.tiker.net/nextcloud/index.php/s/gmn2xQAXvcrQbhW

Google Chrome 60.0.3112.90 is unaffected, i.e. drawn at roughly the same
size as Chromium 59.x.

I'd be much obliged for any advice.

Thanks!
Andreas

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  chromium-common  60.0.3112.78-1
ii  libasound2   1.1.3-5
ii  libatk1.0-0  2.24.0-1
ii  libavcodec57 7:3.3.3-1
ii  libavformat577:3.3.3-1
ii  libavutil55  7:3.3.3-1
ii  libc62.24-12
ii  libcairo21.14.10-1
ii  libcups2 2.2.4-3
ii  libdbus-1-3  1.11.16+really1.10.22-1
ii  libevent-2.0-5   2.0.21-stable-3
ii  libexpat12.2.3-1
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.12.3-0.2
ii  libfreetype6 2.8-0.2
ii  libgcc1  1:7.1.0-10
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.52.3-1
ii  libgtk2.0-0  2.24.31-2
ii  libharfbuzz0b1.4.2-1
ii  libicu57 57.1-6
ii  libjpeg62-turbo  1:1.5.1-2
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.15-1
ii  libnss3  2:3.31-1
ii  libopus0 1.2~alpha2-1
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libpng16-16  1.6.30-2
ii  libpulse010.0-2
ii  libre2-3 20170101+dfsg-1
ii  libsnappy1v5 1.1.6-2
ii  libstdc++6   7.1.0-10
ii  libvpx4  1.6.1-3
ii  libwebp6 0.6.0-3
ii  libwebpdemux20.6.0-3
ii  libwebpmux3  0.6.0-3
ii  libx11-6 2:1.6.4-3
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.12-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.14-1+b4
ii  libxdamage1  1:1.1.4-2+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-2.1
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-driver
ii  chromium-l10n  60.0.3112.78-1
pn  chromium-shell 
ii  chromium-widevine  60.0.3112.78-1

-- Configuration Files:
/etc/chromium.d/default-flags changed:
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --show-component-extension-options"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ignore-gpu-blacklist"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --no-default-browser-check"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --disable-pings"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --disable-background-networking"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --media-router=0"
export CHROMIUM_FLAGS="$CHROMIUM_FLAGS --enable-remote-extensions"


-- no debconf information