Bug 453255 - Set "needs attention" state and/or raise window when showing the "confirm update?" sheet or else users can miss it
Summary: Set "needs attention" state and/or raise window when showing the "confirm upd...
Status: CONFIRMED
Alias: None
Product: Discover
Classification: Applications
Component: Updates (other bugs)
Version First Reported In: 5.24.4
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2022-05-01 08:21 UTC by Paolo Zamponi
Modified: 2025-09-23 18:41 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Paolo Zamponi 2022-05-01 08:21:30 UTC 
SUMMARY
It seems there is no way to know when an update operation is been waiting for an user action.

STEPS TO REPRODUCE
1. Perform an update with Discover and then iconify it in the taskbar. 

OBSERVED RESULT
The update process is always been waiting for a confirm, but nothing warned you.

EXPECTED RESULT
I should be warned if the process is been waiting for something, or if something goes wrong (e.g. the icon in the taskbar should flash, or by a notification).

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220427
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Notification are on in System settings.
This occurs also if something goes wrong, e.g. dependency problem.
Comment 1 Nate Graham 2022-05-03 15:23:50 UTC 
That's quite fair.
Comment 2 Paolo Zamponi 2022-05-04 05:53:13 UTC 
Do you think it makes sense to add a "Don't ask me again" checkbox too in the sheet?
Comment 3 Nate Graham 2022-05-04 17:41:52 UTC 
I don't think so. Ideally you would actually read the contents to see if there's anything dangerous in there; that's why we added it. We might as well just delete it instead of adding an "always proceed" option.