Comment # 60 on bug 1199020 from Stefan Hundhammer

AFAICS we have two heuristics which are now (since the introduction of that
scale factor rounding) defeating each other:

- We calculate a DPI value from the physical screen dimensions in millimeters
that "xrandr" reports and "clean it up", i.e. we make sure it's a number that
can be divided by 48 (but no less than 96), i.e. one of 96, 144, 192, 240, 288
(but no more than that) and set the "Xft.dpi" X resource to that value.

- Qt reads that X resource and stores the value as QXcbScreen::logicalDpi()

- It uses that value and a default dpi value of 96 to calculate a scaling
factor, e.g. 144 / 96 = 1.5 (which would be a reasonable factor)

- It uses its new default rounding policy for that factor to round it to the
next integer number; in this case 2.

- It now uses that nicely rounded scaling factor for everything: Window size,
widget sizes including borders and line widths; and fonts.

As a result, the fonts are now insanely oversized; no longer 150% of what we
previously used, but 200%. And since all other geometry values in our YaST Qt
UI depend on the font sizes, everything becomes way too large: Static texts,
buttons, list content, everything.