| Summary: | Panel popups are mis-positioned when using QT_USE_PHYSICAL_DPI=1 on Wayland | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Michael Hamilton <michael> |
| Component: | Panel | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | minor | CC: | kde, nate, niccolo.venerandi |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot | ||
|
Description
Michael Hamilton
2025-03-29 19:26:21 UTC
Created attachment 179846 [details]
Screenshot
Is this the only issue you see when using QT_USE_PHYSICAL_DPI=1? Or only the one that's severe enough to report, and there are lots of other issues that are smaller that you just grit your teeth and bear? Are other panel pop-ups also mis-positioned in similar ways, or only the one for Kickoff? Does the problem go away if you disable the floating panel feature? (In reply to Nate Graham from comment #2) > Is this the only issue you see when using QT_USE_PHYSICAL_DPI=1? Or only the > one that's severe enough to report, and there are lots of other issues that > are smaller that you just grit your teeth and bear? > > Are other panel pop-ups also mis-positioned in similar ways, or only the one > for Kickoff? > > Does the problem go away if you disable the floating panel feature? The popup issue is the only Plasma6 issue I see, otherwise things look good (except for the panel shadowing). You are correct, I just checked all popups from the panel, are popping up with the same offset - so it's not just the launcher. Changing to a non-floating panel doesn't alter the issue - neither the offset, nor the shadowing under the panel. There are non Plasma issues. I did had to tweak GTK, set it to scale fonts only (for gimp). I'm not sure what controls scaling for KDE3 kmail, I need to track that down. I am only kicking tires at this point, so maybe there are other issues I have not yet encountered. For the moment I'm staying with X11, where everything seems to just work fine with force font DPI. >1. echo 'export QT_USE_PHYSICAL_DPI=1' >> $HOME/.config/plasma-workspace/env/hidpi.sh
Then don't.
Scaling is already quite complicated, mixing wayland scaling with client-side-decided scaling makes it extremely complicated. I don't intend to support this. Sorry. (In reply to David Edmundson from comment #5) > Scaling is already quite complicated, mixing wayland scaling with > client-side-decided scaling makes it extremely complicated. I don't intend > to support this. Sorry. No worries, thanks for looking into it. I'm just trying to figure out a possible way to move to Wayland. I need to make sure that all document and image applications, those that are scaling aware as well as those that aren't, show content at true printed scale (1cm on screen = 1cm on paper). I had hoped to set QT_USE_PHYSICAL_DPI globally as a simple approach, possibly I can set it as a per application level. For the moment we will stay on X11, so this isn't an urgent issue. When considering the switch to Wayland, we're still undecided on what to do. We've been using KDE for more than two decades because of its flexibility, that would seem the easiest route. Perhaps we could stay with X11, maybe move to Trinity/KDE3. Or try something new like COSMIC. Wayland related Nvidia GPU driver changes seem to be creating a lot of paper cuts at the moment, we'll at least delay any further thought until they settle down. In case anyone is interested in a work-around for this issue, I found I that disabling scaling works for me I edited .config/plasma-workspace/env/hidpi.sh and added export QT_ENABLE_HIGHDPI_SCALING=0 Subsequent logins show panel popups where expected. Note, this is quite a hack. It reverts Qt6 spacing, scaling, and the look of some UI elements to match Qt5, so some might not be comfortable with the change in appearance. (Having recently ported a PyQt5 application to PyQt6, I can see the horrible complexity scaling introduces. What I did in the end was to look at the devicePixelRatio and made sure that if it was 1.0, the positioning math remained unscaled.) |