Bug 511014

Summary: Dialog doesn't appear when legacy applications (X11) apply scaling themselves
Product: [Plasma] kwin Reporter: Michael Tsang <miklcct>
Component: xwaylandAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal    
Priority: NOR    
Version First Reported In: 6.3.4   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Michael Tsang 2025-10-24 12:20:08 UTC
SUMMARY

Dialog doesn't appear when legacy applications (X11) apply scaling themselves

STEPS TO REPRODUCE
1. Connect two screens, the primary at 1920x1080@95.8333, the other at 1920x1080@164.167%.
2. Set Legacy application (X11) to "Apply scaling themselves".
3. Use an affected application and perform an operation which will show a dialog.

OBSERVED RESULT
The dialog doesn't appear anywhere and an icon aren't shown on the task bar. However. Alt+Tab list contains the dialog. If I switch to it, it doesn't appear anywhere on any of the screens.


EXPECTED RESULT
The dialog is shown on the screen.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.3

ADDITIONAL INFORMATION
Affected applications include at least JOSM and LibreOffice (in X11 mode by unsetting WAYLAND_DISPLAY). This problem doesn't appear when scaled by the system.
Comment 1 Bug Janitor Service 2025-10-24 12:33:43 UTC
Thank you for the bug report!

However Plasma 6.3.4 no longer receives updates or maintenance from KDE; active versions are 6.4 or newer. Please upgrade to an active version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one.

If you need help with Plasma 6.3.4, please contact your distribution, who bears the responsibility of providing help for older releases that are no longer receiving updates from KDE.

If you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.