Bug 493001

Summary: On Wayland with Nvidia, setting all windows to position themselves maximized also maximizes panel popups
Product: [Plasma] plasmashell Reporter: jm <farina.jeanmarie>
Component: Edit ModeAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: cwo.kde, kdedev, nate, niccolo, plasma-bugs-null, xaver.hugl
Priority: NOR    
Version First Reported In: 6.1.5   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 6.3.0
Sentry Crash Report:
Attachments: picture of glitched popups
log file

Description jm 2024-09-12 05:18:50 UTC
Created attachment 173573 [details]
picture of glitched popups

STEPS TO REPRODUCE
1.  In settings > window management >window behavior > advanced select window placement maximized and apply 
2.  Then right click on panel > show panel configuration
3.  Hover in and out of the panel

OBSERVED RESULT
Th popups are now maximized and have a buggy display 

EXPECTED RESULT
Should stay a popup with the right size

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 cwo 2024-09-12 19:18:53 UTC
Thank you for the bug report!

I can't reproduce this on Plasma 6.1 nor the current development release of Plasma 6.2. Windows are correctly maximized, but the panel pop-ups in Edit mode are using the normal size.

Are you using X11 or Wayland? Do you have any kwin rules that might interfere with this? Can you create a new user account and see if the issue still happens if you have everything else at default settings?
Comment 2 jm 2024-09-13 04:48:35 UTC
I'm using wayland and i don't have kwin rules. I'll try with a blank user asap
Comment 3 jm 2024-09-14 07:03:02 UTC
I cannot reproduce this bug on X11. By the way i also use nvidia proprietary driver on wayland
Comment 4 cwo 2024-09-14 09:20:19 UTC
OK, thanks. It's not unreasonable I guess that a driver bug may be involved; I can't replicate and I'm not on nvidia. It's already good to know that it's Wayland only. Knowing whether it appears on a new user account with otherwise default settings would still be relevant, but I'm removing the NEEDSINFO for now.
Comment 5 jm 2024-09-14 10:21:27 UTC
Yes  i confirm it still happen on a blank install with a new user
Comment 6 TraceyC 2024-09-30 20:42:19 UTC
I'm also not able to replicate the bug on git-master on a laptop with an AMD GPU
I *am* able to replicate this on 6.1.5 on a laptop with an nVidia GPU and the proprietary drivers.
Comment 7 TraceyC 2024-09-30 20:57:01 UTC
Confirming. Waiting to see if this is something we can do something about, or it's an upstream nVidia driver problem
Comment 8 TraceyC 2024-09-30 21:11:52 UTC
jm,

Could you please run this, while you reproduce the bug? Then attach the logs to this bug report. It will help our developers understand what's causing this problem. Thanks!

WAYLAND_DEBUG=1 plasmashell > log.txt 2>&1
Comment 9 jm 2024-10-01 13:50:36 UTC
Created attachment 174283 [details]
log file

Hello, i don't know if i've done it right. Here is the file
Comment 10 TraceyC 2024-10-01 17:02:24 UTC
Thanks for the file!
Comment 11 Nate Graham 2025-04-08 19:45:58 UTC
Can you check again in Plasma 6.3 or later and see if this is still happening?

Thanks a lot!
Comment 12 jm 2025-04-09 05:18:25 UTC
(In reply to Nate Graham from comment #11)
> Can you check again in Plasma 6.3 or later and see if this is still
> happening?
> 
> Thanks a lot!

Hello, it seems to be fixed now. Thanks a lot!
Comment 13 Nate Graham 2025-04-09 14:02:32 UTC
That's great news! Thanks for checking.