Created attachment 129352 [details] Screenshot with KRunner popup offset to the left. SUMMARY KRunner popup opens in the wrong place (too far left) on scaled HiDPI screen. STEPS TO REPRODUCE 1. Invoke KRunner using the keyboard shortcut OBSERVED RESULT See screenshot: KRunner popup opens offset to the left. Actually it seems centered to the left half of the screen, as if there was a coordinate transformation somewhere that did not respect display scaling. EXPECTED RESULT KRunner popup opens in center of screen. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20200611 KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Thinkpad X1 Yoga, 2560x1440 screen Global scaling 200% in display SDDM, PLASMA_USE_QT_SCALING=1 in environment
I checked briefly whether this is the same bug as Yakuake bug 389448, by adding and removing a virtual desktop. This fixes the behaviour with Yakuake, but not with KRunner.
Wayland doesn't have this issue, it's X11 only.
Maybe related to BUG 422578? I don't have this issue KDE Neon with same device and scaling.
(In reply to Alexander Lohnau from comment #3) > Maybe related to BUG 422578? > > I don't have this issue KDE Neon with same device and scaling. Possible. Under Kubuntu with Plasma 5.18 and Qt 5.12 I also didn't have this issue. But then, under OpenSUSE with Plasma 5.19 and Qt 5.15 I had to set PLASMA_USE_QT_SCALING=1 manually, which I didn't under Kubuntu. I'm not sure whether that is because Kubuntu doesn't need it, or whether it silently sets it itself. After this, I am seeing this behaviour with KRunner and a similar issue with Yakuake, which I didn't before. I assume that could have to do with how there are too many different ways to try and achieve a good-looking UI on HiDPI screens (Global scaling, QT_SCALE_FACTOR, QT_AUTO_SCREEN_SCALE_FACTOR, Force font DPI, QT_ENABLE_HIGHDPI_SCALING, Xft.dpi and so on).
Seems like a duplicate of bug 422578. Sorry, I was looking for "HiDPI" as a keyword, which Nate's bug report didn't contain. *** This bug has been marked as a duplicate of bug 422578 ***