https://bugs.kde.org/show_bug.cgi?id=432500
--- Comment #11 from jdvm <khin.n...@gmail.com> --- Hi again, guys. Sorry for the double comment, but I think I know where is the issue, at least in my case. The EDID for my screen is wrong, the DisplaySize in parse-edid says 160 and 90 and I think QScreen 'physical methods' use those values, because printing physicalSize().width() and height() outputs 16 and 9. Thus, the physicalDotsPerInchY and X used by Okular are 'wrong'. Maybe I should try to create a new EDID file and tell Xorg to use it, but Okular could use logicalDotsPerInch instead of physical or QX11Info's properties? Or maybe let the user choose which type to use for this cases? In my case, logicalDotsPerInch and QX11Info::appDpiY/X outputs 96, which is more accurate (I'm not sure if it's because I created a .Xresources file with the property Xft.dpi equal to 96). Could be that those properties were used by Okular years ago? I saw these commit: https://invent.kde.org/graphics/okular/-/commit/f42a3bad65200267cfe04cf584c203e70a3a6ec0 I saw the source code for QX11Info and it uses logical values, not physical: https://code.qt.io/cgit/qt/qtx11extras.git/tree/src/x11extras/qx11info_x11.cpp -- You are receiving this mail because: You are watching all bug changes.
