Bug 473552 - Undoing the removal of a Widget inside a panel leaves an additional "ghost" copy
Summary: Undoing the removal of a Widget inside a panel leaves an additional "ghost" copy
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (other bugs)
Version First Reported In: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-08-20 05:45 UTC by youkai
Modified: 2023-09-05 23:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Video recording of reproducing the bug (1.52 MB, video/webm)
2023-08-20 05:45 UTC, youkai 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description youkai 2023-08-20 05:45:50 UTC 
Created attachment 161064 [details]
Video recording of reproducing the bug

SUMMARY
When removing a widget inside a panel and undoing said removal by clicking undo in the removal-notification the original widget reappears plus an additional "ghost" copy (no icon/content/etc... visible).

STEPS TO REPRODUCE
1. Take any panel and add a widget onto that panel, e.g. the Analog Clock
2. Right-click on the panel and enter edit mode
3. Hover your mouse above the previously added widget and remove it
4. Undo the removal via the removal-notification

OBSERVED RESULT
The panel now has the restored widget and an additional "ghost" copy

EXPECTED RESULT
No ghosts should appear

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 38
(available in About System)
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.6.0
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-08-22 17:01:31 UTC 
Cannot reproduce with today's git master.
Comment 2 youkai 2023-09-05 23:44:22 UTC 
Although I was able to reproduce this consistently with my build up until a few days ago, I am happy to report that it is now fixed for me. Even rolling back plasma-desktop to the date of my original report does not introduce this bug again. It appears some other project might have fixed it for me or it was an error on my setup all along, but alas, I might never find out.