Bug 428875

Summary: Multi monitor setup dialog scale is wrong
Product: [Plasma] plasmashell Reporter: Nathan Colinet <colinetnathan98>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, plasma-bugs
Priority: NOR    
Version: 5.20.2   
Target Milestone: 1.0   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Here's a gif that illustrates the issue

Description Nathan Colinet 2020-11-09 09:11:59 UTC
Created attachment 133162 [details]
Here's a gif that illustrates the issue

SUMMARY

Since maybe 2 years the multi monitor setup dialog doesn't scale well on my screen (1920x1080). If I attach another monitor or press Meta-p the dialog appears then gets huge (unusable). 


STEPS TO REPRODUCE

1. Attach a monitor or press Meta-p

OBSERVED RESULT

The multi monitor setup dialog appears then it gets huge, unusable.

EXPECTED RESULT

I expect the dialog to scale well.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.4.74-1-MANJARO
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION

I have an optimus enabled laptop. It does happen on both nvidia and intel GPU.
Comment 1 Nate Graham 2020-11-09 18:02:01 UTC
Are you using Wayland and/or the "Maximized" window placement style?
Comment 2 Nathan Colinet 2020-11-09 19:19:03 UTC
(In reply to Nate Graham from comment #1)
> Are you using Wayland and/or the "Maximized" window placement style?

I'm on xorg and yes I'm using the Maximized window placement style. If I change it to "centered" it works well.
Comment 3 Nate Graham 2020-11-09 19:24:35 UTC
Ah, so the bug is that this OSD is inappropriately respecting the Maximized window placement mode. Duplicate of Bug 428859.

*** This bug has been marked as a duplicate of bug 428859 ***
Comment 4 Nathan Colinet 2020-11-10 09:49:06 UTC
(In reply to Nate Graham from comment #3)
> Ah, so the bug is that this OSD is inappropriately respecting the Maximized
> window placement mode. Duplicate of Bug 428859.
> 
> *** This bug has been marked as a duplicate of bug 428859 ***

Yes, I didn't find it, sorry about that and thanks for the support.