Bug 438486

Summary: Software Updates notifications stay on the screen.
Product: [Plasma] plasma-pk-updates Reporter: jerrys <j>
Component: generalAssignee: Jan Grulich <jgrulich>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aleixpol, jackhill3103, nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Software Update Notifications

Description jerrys 2021-06-12 02:03:55 UTC
SUMMARY
Software Updates notifications stay on the screen and they can grow to larger number.
These notifications (which stay on the screen) are the most annoying feature in Linux desktop today. I am constantly forced to get rid of these notifications several times a day.
Please get rid of it. Use standard notification which disappear after some time. 

Regarding the error on the screenshot, I allowed the unverified signature in zypper, but packagekit cannot handle it. Zypper is not giving me any errors, packagekit does. It is wrong that the system uses two different platforms for updates and they are not aware of each other. This results into bad user experience!

STEPS TO REPRODUCE
1. Just use updates. Everytime update is available these notification will pop up and are glued to the screen.


OBSERVED RESULT
Notifications are glued to the screen. They don't disappear unless manually removed.


EXPECTED RESULT
Use normal notifications which disappear after few seconds.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSuse Tumbleweed / Plasma 5.21.5
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Comment 1 jerrys 2021-06-12 02:04:27 UTC
Created attachment 139242 [details]
Software Update Notifications
Comment 2 Nate Graham 2021-06-15 22:43:42 UTC
These come from openSUSE's plasma-pk-updates widget, not from Discover.
Comment 3 Jack Hill 2022-09-07 10:26:37 UTC

*** This bug has been marked as a duplicate of bug 413041 ***
Comment 4 Jack Hill 2022-09-07 10:39:41 UTC
Sorry for the spam, I set this as a duplicate to the wrong bug

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