Mailinglist Archive: opensuse-bugs (4794 mails)

< Previous Next >
[Bug 1051151] DPI auto-detection works incorrectly
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 31 Jul 2017 13:13:26 +0000
  • Message-id: <bug-1051151-21960-pmtXoexdh0@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1051151
http://bugzilla.opensuse.org/show_bug.cgi?id=1051151#c7

Max Staudt <mstaudt@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
CC| |mstaudt@xxxxxxxx
Resolution|--- |INVALID

--- Comment #7 from Max Staudt <mstaudt@xxxxxxxx> ---
Hmm. Sorry, this is intended behavior with modern cards/drivers.

The DPI info in xdpyinfo is a legacy metric. It fails as soon as the system
consists of a mixed setup, with monitors with different DPIs. That's why xrandr
now provides DPI information for each monitor separately, and the legacy metric
is forced to a fallback value:

https://bugs.freedesktop.org/show_bug.cgi?id=23705#c6

The 96 DPI default is there in order to make older software behave consistently
in such a setup - i.e. to have it render text with enough pixels to be legible
in all configurations.

If you wish, you can still change that setting via a manual xorg.conf setting.
Or you can see whether you applications react to e.g. a setting in
~/.Xresources:

Xft.dpi: 120
Xft.hinting: 1
Xft.hintstyle: hintfull

...and then run:

xrdb -merge ~/.Xresources

...and restart your application.

Your desktop environment will often also have a DPI setting somewhere - try
setting that as well. Different programs read different settings, and forcing
DPI has always been a bit of a pain. If after all this, your applications are
still not rendering nicely (yes, even Firefox could have a problem, and I know
that Chrome currently has a bug, always rendering in HiDPI), then that is a
problem with those applications.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References