New issue
Advanced search Search tips

Issue 882223 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 10
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome does not respect Xorg Screen dimensions / DPI

Reported by oleksii....@gmail.com, Sep 9

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Steps to reproduce the problem:
1. Launch `google-chrome-stable` on a screen ("screen" in this bug report means Xorg Screen) which is at 182x184 DPI.
2. Witness the application to be sized as if it was 96 DPI.

What is the expected behavior?
Respect Xorg's screen dimensions and calculate DPI based on them.

What went wrong?
Chrome does not respect Xorg Screen dimensions / DPI.

% xdpyinfo | grep -B2 resolution
screen #0:
  dimensions:    1920x1080 pixels (483x272 millimeters)
  resolution:    101x101 dots per inch
--
screen #1:
  dimensions:    2160x3840 pixels (301x530 millimeters)
  resolution:    182x184 dots per inch

When launched on the screen 1 (via DISPLAY=:0.1 google-chrome-stable), the screen dimensions reported by X server are not respected. See <https://gitlab.freedesktop.org/xorg/app/xdpyinfo/blob/master/xdpyinfo.c#L446> for how `xdpyinfo` calculates the DPI (dimensions are provided by nvidia driver).

Attached:
* Xorg log (from `exec /usr/bin/X -nolisten local "$@" vt$XDG_VTNR -keeptty -logverbose 9`)
* Xorg config (`/etc/X11/xorg.conf`)
* full output of `xdpyinfo`

Did this work before? N/A 

Chrome version: 69.0.3497.81 (Official Build) (64-bit)  Channel: stable
OS Version: 4.18.6-arch1-1-ARCH
Flash Version: 24.0.0.189 internal-not-yet-present
 
xorg.conf
6.0 KB Download
Xorg.0.log
897 KB View Download
xdpyinfo.out
111 KB Download
Never mind, for some reason XFCE had the font DPI enforcement option set to 96 by default in Appearance -> Fonts -> DPI -> Custom DPI Setting.

Please, close.
Labels: Needs-Triage-M69
Labels: Triaged-ET
Status: WontFix (was: Unconfirmed)
oleksii.vilchanskyi@ Thanks for the update.

As per comment #1, marking this issue as WontFix, as the reporter has confirmed to close this issue.

Thanks..

Sign in to add a comment