Bug 500523
| Summary: | PackageKit update applet insist that there are update when they have been installed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hubert Figuiere <hub+rhbz> |
| Component: | PackageKit | Assignee: | Richard Hughes <richard> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | dcantrell, jhaar, lmacken, mclasen, richard, smparrish |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-16 00:01:08 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Hubert Figuiere
2009-05-13 04:35:00 UTC
The version I have installed: PackageKit-yum-0.4.6-8.fc11.i586 PackageKit-glib-0.4.6-8.fc11.i586 PackageKit-yum-plugin-0.4.6-8.fc11.i586 PackageKit-0.4.6-8.fc11.i586 PackageKit-gtk-module-0.4.6-8.fc11.i586 Me too I'm an old-time "yum update" user, so I often install from command line. The PackageKit Update applet doesn't seem to notice and will then tell me I have outstanding updates. When I click on "Show Updates" it has a think about it and then tells me there are zero updates - but doesn't change its own status. This has happened since the beginning of my FC11 experience - starting 3-4 weeks ago when I installed FC11-preview. Currently PackageKit-yum-0.4.6-8.fc11.i586 Just to be clear: it happen even when using PackageKit to perform the update. Worse: if the update installed need reboot, and after I have dismissed the icon, when I do "Show Updates", the icon asking me to reboot appear again. *** This bug has been marked as a duplicate of bug 492005 *** |