https://bugzilla.suse.com/show_bug.cgi?id=1199020 https://bugzilla.suse.com/show_bug.cgi?id=1199020#c57 --- Comment #57 from Fabian Vogt <fvogt@suse.com> --- (In reply to Stefan Hundhammer from comment #55)

Now for the font sizes.

Analyzing the first set of y2logs from comment #2 (jsudermann):

Xorg.0.log:

[ 82.995] (II) modeset(0): clock: 152.8 MHz Image Size: 344 x 193 mm

[ 82.995] (II) modeset(0): h_active: 1920 h_sync: 2000 h_sync_end 2054 h_blank_end 2250 h_border: 0

[ 82.995] (II) modeset(0): v_active: 1080 v_sync: 1086 v_sync_end 1094 v_blanking: 1132 v_border: 0

y2start.log:

Stage [call]: Monitor size: eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm

Stage [call]: Monitor width mm: 344 Stage [call]: Monitor width px: 1920 Stage [call]: Monitor dpi: 144 Stage [call]: Xft.dpi set to: 144

y2log:

2022-04-29 14:43:46 <1> install(4700) [qt-ui]

YQApplication.cc(pickAutoFonts):471 Selecting auto fonts - normal: 10, heading: 12 (bold)

YQApplication.cc(currentFont):339 Loaded 10 pixel font: Sans Serif,-1,10,5,50,0,0,0,0,0

This sounds very reasonable so far. Except for this:

YQUI.cc(calcDefaultSize):370 -fullscreen: using 960 x 540 for `opt(`defaultsize)

YQUI.cc(calcDefaultSize):404 Default size: 960 x 540

?!? Why does it use 960 x 540 for -fullscreen?

https://github.com/libyui/libyui/blob/master/libyui-qt/src/YQUI.cc#L370

QSize availableSize = screen->availableSize();

So Qt thinks we are in HiDPI mode, scaling everything?

Yes, QScreen::availableSize returns "device-independent pixels", so physical pixels / scale factor.

It's using half the resolution values of 1920 x 1080 in both dimensions.

Which sounds wrong. With 1080 horizontal pixels HiDPI scaling should not be enabled, or at most use 1.5x scaling.

And we also requested only a moderate font size: 10 px for normal text, 12 px for headings. Yet the screenshots show that those are massively scaled up; probably to 20 px for normal text (I can only guess).

-- You are receiving this mail because: You are on the CC list for the bug.