Bug 510545

Summary: Don't allow duplicate notifications, re-use the existing notifications instead.
Product: [Plasma] plasmashell Reporter: Fernando M. Muniz <fernandommuniz>
Component: NotificationsAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: akselmo, kde
Priority: NOR Keywords: usability
Version First Reported In: 6.4.5   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Issue on Plasma 6.4.5

Description Fernando M. Muniz 2025-10-12 23:20:29 UTC
Created attachment 185724 [details]
Issue on Plasma 6.4.5

STEPS TO REPRODUCE
1. Have a damaged/cheap usb cable.
2. Use it to connect your phone to your PC.

OBSERVED RESULT
Multiple duplicate notifications appear, needlessly wasting screen space.

EXPECTED RESULT
There should only be one notification with the exact same text, in this case 1 "Detected" and 1 "Removed" notification, and each time the device changes state; the older notification should change places with newer one and reset its fade out timer.
And if there is only one notification; just reset the fade out timer.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz
Memory: 9 GB of RAM (8.1 GB usable)
Graphics Processor 1: Intel® Iris® Xe Graphics
Graphics Processor 2: NVIDIA GeForce GTX 1650
Manufacturer: LENOVO
Product Name: 82MG
System Version: IdeaPad Gaming 3 15IHU6

ADDITIONAL INFORMATION
That should solve a bunch of needless notification clutter.
Comment 1 Fernando M. Muniz 2025-10-12 23:53:31 UTC
I guess the non-artsy-fartsy way to implement this is to simply delete older duplicate notifications.

But I prefer my original suggestion because it would allow fancy switcheroo effect between notifications.
Comment 2 Akseli Lahtinen 2025-10-13 09:30:59 UTC

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