xpra icon
Bug tracker and wiki

DPI


Introduction

We try to synchronize the DPI from the client to the server, so that applications will render with the correct settings and "look right" on the client. This may affect fonts, window sizes, cursors sizes, etc.

Caveats:

  • support varies greatly depending on the operating system and version, desktop environment, number of monitors attached and their resolution, etc
  • with X11, there are far too many places where the DPI can be looked up, many places where it can be overriden
  • for virtualized "hardware DPI" which some applications calculate from the virtual monitor dimensions, you will need a patched wiki/Xdummy driver and wiki/FakeXinerama - without a patched dummy driver, the hardware DPI (as reported by xdpyinfo) cannot be updated at runtime and must be set in advance, either in the xorg.conf file or on the xvfb command line
  • many applications will not reload the DPI settings, so they must be started after the client connects to get the correct DPI value

Debugging

For wiki/Debugging, some relevant information can be collected from:

  • client and server debug output with "-d dpi" command line switch
  • xdpyinfo output
  • xrandr output

Related xpra tickets

  • #697 gtk screen dimension detection is broken with high dpi displays on windows7 and later
  • #163 pass client DPI preference to server (and use sane defaults of 96dpi)
  • #976 client display scaling
  • #919 frame extents synchronization
  • #887 chrome DPI
  • #882 DPI with Ubuntu (not fixable as Ubuntu does not use wiki/Xdummy)
  • #1086 DPI handling improvements, OSX support
  • #1215 patched dummy driver for Debian and Ubuntu
  • #1193 bug with client command line switch handling
  • #1526 per-monitor DPI with MS Windows clients
Last modified 3 months ago Last modified on 06/25/17 22:32:11