SUMMARY Camera Indicator Widget leaves pop-up if the pop-up is open when the widget is removed. The pop-up then cannot be closed without either restoring the widget and closing the pop-up via the widget or restarting Plasma. STEPS TO REPRODUCE 1. Add Camera Indicator Widget to desktop via Edit Mode. 2. Click Camera Indicator Widget, bringing up the pop-up. 3. Right-click and remove Camera Indicator Widget. OBSERVED RESULT Camera Indicator Widget pop-up remains after the widget has been removed, and cannot be interacted with. EXPECTED RESULT Camera Indicator Widget pop-up removed if the widget is removed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.11.0-26-generic #26~24.04.1-Ubuntu KDE Plasma Version: plasma-desktop-4:6.3.5-0zneon+24.04+noble+release+build29.amd64 KDE Frameworks Version: plasma-framework-6.3.5-0zneon+24.04+noble+release+build19.all Qt Version: qt6-base-6.9.0-0zneon+24.04+noble+release+build112.amd64
This is a general issue with all widgets whose popups were open at the moment they were deleted. The popup will close automatically when you dismiss the undo notification — at which point the widget *actually* gets removed.
(In reply to Nate Graham from comment #1) > This is a general issue with all widgets whose popups were open at the > moment they were deleted. The popup will close automatically when you > dismiss the undo notification — at which point the widget *actually* gets > removed. If this is expected behavior, should this be marked as RESOLVED? This is the first bug I've reported manually, so I'm not very familiar with the reporting process and I'm not certain what responsibilities I have.
It's "expected" in that we know it happens and it's doing what the code says it should. From that perspective it's not really a bug in the technical sense of the word. However it results in an awkward UX, so it's a bug in the UX sense of the word, in that it's an unexpected and weird behavior from a user's point of view. You don't have any responsibilities at this point. Since the ticket is in CONFIRMED status, that means it's now up to developers to resolve the issues once any of them have time to do so.
*** This bug has been marked as a duplicate of bug 470812 ***