Bug 124441 - Excessive number of clicks required when updating system
Summary: Excessive number of clicks required when updating system
Status: CLOSED DUPLICATE of bug 120336
Alias: None
Product: Fedora
Classification: Fedora
Component: up2date   
(Show other bugs)
Version: 2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Adrian Likins
QA Contact:
Keywords: FutureFeature
Depends On:
Blocks: 120092
TreeView+ depends on / blocked
Reported: 2004-05-26 16:29 UTC by Ricky Ng-Adam
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 19:03:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ricky Ng-Adam 2004-05-26 16:29:25 UTC
When the Red Hat Alert Notification Tool in the icon tray goes to a
red exclamation point, I have to:

Click on tray icon
List of updates available
Click on "Launch up2date..."
Enter password
Click on OK
Package and channels shown
Click on Forward
Check "Select all packages"
Click on Forward
Retrieving packages and when completed...
Click on Forward
Installing packages
Click on Forward
All finished
Click on Finish

That is 8 clicks / different steps to get to the updated system. Many
of those steps are purely informational or for confirmation only.  All
I want is to update everything automatically. Only have it popup an
extra dialog if a problem occurs. No more then 4 clicks and the root
password input should be necessary and at best it would be to have an
option to silently update the system.

Also, I noticed that the icon in the tray does not turn to a blue
checkmark immediately after update.

Comment 1 Miloslav Trmac 2004-05-28 09:03:36 UTC
This seems to be a duplicate of bug 120336.

Comment 2 Ricky Ng-Adam 2004-05-28 14:58:15 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:03:49 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.