http://bugzilla.opensuse.org/show_bug.cgi?id=1051151
http://bugzilla.opensuse.org/show_bug.cgi?id=1051151#c7
Max Staudt changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
CC| |mstaudt@suse.com
Resolution|--- |INVALID
--- Comment #7 from Max Staudt ---
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.