Description of problem: Each time you advance in a menu or sub-menu in kicker (default Mageia menu in Plasma), it opens a new "plasmashell" task in the taskbar. Version-Release number of selected component (if applicable): plasma-workspace-5.93.0-1 How reproducible: Always Steps to Reproduce: 1. Open a menu in kicker
Cannot reproduce. Plasma menus seem to behave normally here. Are you able to attach a screenshot of what you are reporting?
CC: (none) => lewyssmithSource RPM: plasma-workspace-5.93.0-1.mga10.src.rpm => plasma-workspace-5.93.0-1.mga10.src.rpm, plasma-desktop-5.27.5-2.mga9.src.rpm
Mistake on my part: I am on M9, this is about Cauldron. Screenshot request remains valid.
After discussion upstream, seems related to Bug32890
You can find a video of the bug here : https://bugsfiles.kde.org/attachment.cgi?id=166112
See the plasmashell task in the taskbar.
(In reply to Lewis Smith from comment #2) > Mistake on my part: I am on M9, this is about Cauldron. > Screenshot request remains valid. Lewis this is Cauldron and plasma 6 . I have vbox install Cauldron and plasma 6 rc...
This have to be Mageia bug as i booted Kde neon unstable iso real hw, have plasma 6 have no any bugs like this..
(In reply to Cyril Levet from comment #4) > You can find a video of the bug here : > https://bugsfiles.kde.org/attachment.cgi?id=166112 (In reply to Cyril Levet from comment #5) > See the plasmashell task in the taskbar. Good illustration. Interesting that it only shows going one leven down from the main menu; I wonder whether if you went into a lower level menu whether you would get another plasmashell task (I believe you that is what it is!). (In reply to Cyril Levet from comment #3) > After discussion upstream, seems related to Bug32890 (moving Plasma taskbar) "it's X11 only. Works fine on Wayland". Is this true also for *this* menu problem? (In reply to Otto Leipälä from comment #7) > This have to be Mageia bug as i booted Kde neon unstable iso real hw, have > plasma 6 have no any bugs like this.. This looks like bleeding edge stuff. Could it suggest that what you tried is more up-to-date than what we have? plasma-workspace-5.93.0 plasma-desktop-5.27.5 Can you say what your OK versions are?
(In reply to Cyril Levet from comment #3) > After discussion upstream, seems related to Bug32890 That bug is classified UPSTREAM; does this mean we can classify this bug likewise?
(In reply to Lewis Smith from comment #8) > Good illustration. Interesting that it only shows going one leven down from > the main menu; I wonder whether if you went into a lower level menu whether > you would get another plasmashell task (I believe you that is what it is!). Yes, it does create another plasmashell task if you go deeper on the sub menus. > > After discussion upstream, seems related to Bug32890 (moving Plasma taskbar) > "it's X11 only. Works fine on Wayland". > Is this true also for *this* menu problem? I think it's X11 only, too. I tested on the same Mageia Cauldron with Wayland and kicker works as expected without creating any "plasmashell" tasks. The KDE team hypothesis so far is : > 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 > defloat. Because menus are considered as windows touching the floating panel, it defloats. The two bugs seems linked. But this remains an untested hypothesis. (In reply to Lewis Smith from comment #9) > (In reply to Cyril Levet from comment #3) > > After discussion upstream, seems related to Bug32890 > That bug is classified UPSTREAM; does this mean we can classify this bug > likewise? Yes, it can be classified as upstream. It's the “mother” bug that causes the other one.
Thank you for all these clarifications. Assigning to Plasma people.
Keywords: (none) => UPSTREAMAssignee: bugsquad => kdeSummary: Moving into kicker sub-menus open a new task in taskbar => Moving into kicker sub-menus open a new task in taskbar (probably X11, not Wayland)CC: lewyssmith => (none)Status: NEW => UPSTREAM
One question: did you test with a fresh user profile to rule out a broken/borked profile?
I tested with a new user created in Cauldron and the bug remains. My default user is rather new. I just create a Mageia 9 VM in Virtual Box with one user and immediately update and upgrade to Cauldron.
Fixed in Plasma 6.0.3.
Status: UPSTREAM => RESOLVEDResolution: (none) => FIXED