Bug 372012

Summary: Window Decoration Context Menu does Not Respect QT_SCREEN_SCALE_FACTORS=2
Product: [Plasma] kwin Reporter: Jason A. Donenfeld <Jason>
Component: coreAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: battaglia01, jan, kde, nate
Priority: NOR    
Version: 5.8.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: bad-context-menu-padding-on-kwin-window-border.png
good-context-menu-padding-in-dolphin.png

Description Jason A. Donenfeld 2016-11-03 09:52:41 UTC
Despite having QT_SCREEN_SCALE_FACTORS=2 set, kwin does not respect this for some reason. See the two attached screenshots comparing dolphin and kwin context menu padding.
Comment 1 Jason A. Donenfeld 2016-11-03 09:53:06 UTC
Created attachment 101994 [details]
bad-context-menu-padding-on-kwin-window-border.png
Comment 2 Jason A. Donenfeld 2016-11-03 09:53:28 UTC
Created attachment 101995 [details]
good-context-menu-padding-in-dolphin.png
Comment 3 Jason A. Donenfeld 2016-11-03 09:56:36 UTC
This is similar to bug #372013, which involves plasmashell.
Comment 4 Martin Flöser 2016-11-03 10:20:42 UTC
@David: opinions?
Comment 5 David Edmundson 2017-02-20 16:35:35 UTC
He's correct, Qt scaling in kwin is turned off. Unfortunately turning it on would cause havoc, and require changes all over kwin. It isn't worth it right now, and we can't do scaling on a per-window basis.

Plasmashell also has the same issue with context menus. I can see us making a pure QtQuick menu at some point in the near future which can then use Plasma scaling.

With the current wayland scaling patchset the situation is different, but not perfect. The menu will be scaled so all icons look normal but it will have the resolution of a normal DPI device.
Comment 6 David Edmundson 2017-05-12 21:30:55 UTC
Wayland scaling patchset merged. 
My drop down looks fine.

Fixed in 5.10 /if/ you're using the proper wayland scaling.
Comment 7 David Edmundson 2018-03-16 15:39:18 UTC
*** Bug 391904 has been marked as a duplicate of this bug. ***