Bug 420326

Summary: Window Titlbar not scaling correctly on Wayland
Product: [Plasma] kwin Reporter: smit <smit17xp>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde
Priority: NOR Flags: vlad.zahorodnii: Wayland+
Version: 5.18.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: All   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: screenshot

Description smit 2020-04-20 06:59:31 UTC
Created attachment 127703 [details]
screenshot

I have 1360x768 monitor scaled to 80% (1700x960) on Wayland (I not sure if this possible on Xorg). everything works great except title bar don't scale. it goes back to its original size for windows of 1360x768 which displays misplaced buttons. I can still click button but I have to guess their location as actually shown buttons do nothing. I've attached a zip of screenshots.

When I drag a Window from normal screen to Scaled screen and hold it looks as expected but when I let go of the hold, it immediately becomes large

STEPS TO REPRODUCE
1. scall
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 smit 2020-04-20 07:01:53 UTC
Sorry for above incomplete submission 

STEPS TO REPRODUCE
1. scale display down 
2. drag windows from non-scaled display to scaled display
Comment 2 Vlad Zahorodnii 2020-10-15 06:10:49 UTC
> I have 1360x768 monitor scaled to 80%
Are you using a scale factor that is less than 1?
Comment 3 smit 2020-10-17 03:03:26 UTC
(In reply to Vlad Zahorodnii from comment #2)
> > I have 1360x768 monitor scaled to 80%
> Are you using a scale factor that is less than 1?

yes. 0.80
Comment 4 Vlad Zahorodnii 2020-10-26 08:51:48 UTC
We don't really support scale factors less than 1, so visual artifacts are kind of expected. However, we won't reject patches that try to fix it.
Comment 5 David Edmundson 2023-01-17 13:03:32 UTC
This seems to work now. Please reopen if an issue persists with 5.27