SUMMARY If I drag a widget from the desktop to my hidden top panel then that widget gets stuck on the desktop and I am no longer able to interact with it. If I drag it to the hidden bottom panel it gets added correctly. However dragging off of the hidden bottom panel and back to the desktop causes it to outright disappear. Restarting plasmashell fixes all the issues except for when the widget completely disappears. When that happens I just have to edit the config file and remove the widget from there. I've tested this with the network speed widget. Related to https://bugs.kde.org/show_bug.cgi?id=482371 STEPS TO REPRODUCE 1. Have a top and bottom panel. 2. Set them both to authide. 3. Drag a widget to and from the hidden panels. OBSERVED RESULT Widget either gets stuck on the desktop in the case of dragging to the top panel or disappears forever in the case of dragging from the bottom panel. EXPECTED RESULT Widgets should migrate to and from panels without with getting stuck or disappearing. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.8.2-zen2-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C95 System Version: 1.0
Cannot reproduce in current git master; dragging an Analog Clock from the desktop to a hidden top panel works fine for me. Any chance you could attach a screen recording that shows the issue?
Created attachment 168293 [details] Video of the Issue
(In reply to Nate Graham from comment #1) > Cannot reproduce in current git master; dragging an Analog Clock from the > desktop to a hidden top panel works fine for me. > > Any chance you could attach a screen recording that shows the issue? I've added a screen recording. Hope this helps. Perhaps this could be a case of something wrong with the arch package or some commit not being backported?
Thanks. How extremely strange. There's something I'm confused about in your video: when you enter edit mode, the screen flashes. Do you have any kwin effects or kwin rules active that could explain this? Also, can you test in a clean user account to see if it reproduces there, or only in your currently customized user account?
(In reply to Nate Graham from comment #4) > Thanks. How extremely strange. > > There's something I'm confused about in your video: when you enter edit > mode, the screen flashes. Do you have any kwin effects or kwin rules active > that could explain this? > > Also, can you test in a clean user account to see if it reproduces there, or > only in your currently customized user account? I believe the flash is the eye on screen effect. I liked that one better than the default window aperture. I'll test with a new user and see what happens give me just a few minutes.
Hi Nate, I tried with a new user and was still able to reproduce. Upon entering the clean environment, I performed the following steps: 1. Add an empty top panel. 2. Set the top panel to autohide. 3. Add analog clock widget to the desktop. 4. Drag analog clock widget to top panel which is currently in the hidden state. The result is the same as my current environment. Perhaps I should test with a different widget.
I tried with the binary clock widget and got the same result as well. One thing that I just noticed is that when I was recording the video to show the issue, I didn't exit edit mode. When in edit mode, the panels do not autohide, the issue still occurred though. Perhaps the auto-hide setting being active at all causes the issue?
Decided to beta test plasma 6.1. Loving the new edit mode, but unfortunately it does not prevent or solve this bug.
Well now it doesn't get stuck on the desktop. It instead disappears entirely. If I drag the widget onto a panel whether in edit mode or not. That widget will disappear.
Thank you for your bug report! There is another report covering the same root cause in a slightly different setting, with a fix being actively worked on. Please follow that report for further updates. If the fix (once released) does not resolve this issue after all, please feel free to reopen this or report it as a new bug. *** This bug has been marked as a duplicate of bug 487825 ***
(In reply to cwo from comment #10) > Thank you for your bug report! There is another report covering the same > root cause in a slightly different setting, with a fix being actively worked > on. Please follow that report for further updates. If the fix (once > released) does not resolve this issue after all, please feel free to reopen > this or report it as a new bug. > > *** This bug has been marked as a duplicate of bug 487825 *** Thank you for linking me to the right place. I know it must be a lot of work to sort through so many duplicates.