Bug 380357

Summary: Doubling of plasmoids in plasmoidviewer (after dismissing plasma notification "Widget removed)
Product: [Plasma] Plasma SDK Reporter: AiwendilH
Component: plasmoidviewerAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: minor CC: AiwendilH, bizyaev, giorgos.tsiapaliokas, kdedev
Priority: NOR    
Version First Reported In: 5.9.5   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description AiwendilH 2017-05-30 14:53:09 UTC
If I close a plasmoid in plasmaviewer I get a desktop notification about about a widget being removed and if to want to revert this. No matter what I do (Use the "x" to close the notification or just wait for it to timeout) plasmoidviewer adds a second plasmoid again. First one is added at once after closing (makes sense), second one as soon as the notification is closed.

Step to reproduce:
- "plasmoidviewer -a org.kde.plasma.analogclock"
- closing of the clock inside plasmoidviewer
- A new clock is opened at once and I get a plasma notification about removing a plasmoid
- Either waiting for the notification to timeout or closing it with "x"
- A second clock plasmoid is opened in plasmoidviewer

Expected behaviour:
Dismissing the notification should not lead to a second plasmoid being opened.
I like that plasmoidviewer issues the notification in the first place, makes it more a "real world" behaviour. Overall a pretty minor issue (well, except that it made be question my sanity and wth I did in my code to always restart it again after about a minute before I managed to make the connection with the notification ;)) just thought I report it.
Comment 1 TraceyC 2025-06-25 20:05:55 UTC
Thanks for the bug report. I'm sorry we weren't able to get to this yet. There have been many fixes and improvements since this was reported, and this issue may have been fixed. I'm not able to reproduce it in today-s git-master.

Can you please re-test on your system with Plasma 6.4.1 or later / recent git-master and let us know if you can still reproduce the problem? If you can, please set this report back to REPORTED. Thanks!
Comment 2 Bug Janitor Service 2025-07-10 03:47:56 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2025-07-25 03:46:57 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.