https://bugs.kde.org/show_bug.cgi?id=415421
--- Comment #32 from Andrew Udvare <audv...@gmail.com> --- (In reply to Fabian Vogt from comment #31) > Git commit ea66bff2af8466f2bb5acafcc43ac8f79b1f447f by Fabian Vogt. > Committed on 21/01/2020 at 10:56. > Pushed by fvogt into branch 'Plasma/5.18'. > > Also disable automatic scaling on Qt >= 5.14 > > Summary: > Applications which set `Qt::AA_EnableHighDpiScaling` use the DPI of the > monitor the window is on to calculate an additional scaling factor. > Plasma sets `QT_SCREEN_SCALE_FACTORS` in the environment for manual > specification of per-monitor scale, which combined with the automatic > scaling may result in double scaling. > To disable the automatic scaling, `QT_AUTO_SCREEN_SCALE_FACTOR=0` has to be > set, even on Qt 5.14. > > As a side effect, this works around QTBUG-80967 as well. > > Test Plan: On X11, with a >144dpi monitor and a scaling factor of 2 set > manually, scaling was doubled previously. Now it works as expected. > > Reviewers: #plasma, apol, davidedmundson, fvogt > > Reviewed By: #plasma, davidedmundson, fvogt > > Subscribers: acooligan, fvogt, asturmlechner, dfaure, davidedmundson, > anthonyfieroni, plasma-devel > > Tags: #plasma > > Differential Revision: https://phabricator.kde.org/D26185 > > M +0 -2 startkde/startplasma.cpp > > https://commits.kde.org/plasma-workspace/ > ea66bff2af8466f2bb5acafcc43ac8f79b1f447f That fix resolves most of the issue but Chrome seems to now run with a reduced environment. /proc/<chrome PID>/environ shows a very minimal environment. As a result, when Chrome launches Ark (click on item in the download bar) I get the same issue. I modified the .desktop file to force the QT_AUTO_SCREEN_SCALE_FACTOR=0 value and it works. I wouldn't want to have to create custom .desktop files just for Chrome. Should I file another ticket? -- You are receiving this mail because: You are watching all bug changes.
