Bug 485492

Summary: Dragging widget from panel to desktop makes applet disappear forever
Product: [Plasma] plasmashell Reporter: joey.joey586
Component: Desktop ContainmentAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: minor CC: nate, notmart
Priority: NOR    
Version: 6.0.3   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description joey.joey586 2024-04-13 15:24:49 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY


STEPS TO REPRODUCE
1. Drag a widget from a panel to the desktop (area outside the panel)
2. Widget disappears, nowhere to be found on the desktop
3. Going to the Add Widgets menu shows that the widget still exists on the desktop (there is still a number next to the widget)

(Have to manually edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc to remove the ghost widget)

OBSERVED RESULT
Widget disappears instead of appearing as a resizable applet on the desktop
Logging out and back in to Plasma does not bring widget back
Rebooting system also does not bring widget back

EXPECTED RESULT
Widget should appear as a resizable applet on the desktop, just like if adding widget to desktop directly from Add Widgets menu

OR

If dragging widget out of panel is intended to delete it, the Add Widgets menu should not show the widget as in use

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.0
Kernel Version: 6.8.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 2 × AMD A9-9420e RADEON R5, 5 COMPUTE CORES 2C+3G
Memory: 3.7 GiB of RAM
Graphics Processor: AMD Radeon R5 Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 3180
System Version: 1.1.0

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-06-26 21:24:39 UTC

*** This bug has been marked as a duplicate of bug 487825 ***