| Summary: | On X11, Plasma taskbar move depending on the length of the menu in kicker | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | cyril.yuusha |
| Component: | Application Menu (Kicker) widget | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | Keywords: | qt6 |
| Version First Reported In: | 5.93.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Mageia RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 6.0.3 | |
| Sentry Crash Report: | |||
| Attachments: | Video of the bug | ||
|
Description
cyril.yuusha
2024-02-24 12:49:55 UTC
I'm guessing there's a very specific panel configuration in step 0 that was not reported, since I can't reproduce this with either a default panel or a small content-filling panel. Can you describe your panel settings? Or even better, attach a screen recording? I use the default configuration for Mageia Cauldron. However, I'm not the maintainer, so I don't know which specific configuration is applied. I think it's the same configuration as the one in Mageia 9 with Plasma 5.27.5. The bug declared in Mageia bug tracker is here : https://bugs.mageia.org/show_bug.cgi?id=32890 I will add a screen recording. Created attachment 166112 [details]
Video of the bug
Thanks for the screen recording, it's fascinating. It looks like the submenus are being counted as windows for the purpose of determining if any windows are touching a floating panel, which makes it de-float. That said, I cannot reproduce the issue on Wayland. Are you seeing it on X11 only? I confirm this bug is X11 only. I tested on Wayland and kicker works fine. Still valid on X11 with : Linux/KDE Plasma: Mageia 10 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Pretty sure this was fixed by another fix that went into 6.0.2. Can you re-test? The bug is still present with this version: Operating System: Mageia 10 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.22-desktop-1.mga10 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4790 CPU @ 3.60GHz Memory: 7.8 Gio of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 I have tested it (Plasma 6.0.2, X11, kicker) on an OpenSUSE Tumbleweed and I have got the same problem. Operating System: openSUSE Tumbleweed 20240321 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4790 CPU @ 3.60GHz Memory: 7.8 Gio of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; Manufacturer: innotek GmbH Product Name: VirtualBox System Version: 1.2 Can you see if Plasma 6.0.3 fixed this? There was a commit that I think has the possibility to. (In reply to Nate Graham from comment #11) > Can you see if Plasma 6.0.3 fixed this? There was a commit that I think has > the possibility to. Yes, I confirm, it is fixed in Plasma 6.0.3 Great! |