| Summary: | Packagekit sometimes doesn't recognize new updates | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Rolle <rolle.hoffmann> |
| Component: | PackageKit | Assignee: | Richard Hughes <richard> |
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | adel.gadllah, djuran, jonathan, pankaj86, paradoxe, rhughes, richard, smparrish |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-10 17:09:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Rolle
2011-05-22 21:02:17 UTC
We only do the notification of normal updates (e.g. not security updates) once a week, no matter the checking frequency the user specified. Has it been more than one week since you were notified? I don't wait until a notification appears automatically. In the last 2 weeks I opened PackageKit manually (Software-Updates) to see if new updates are available and wondered that in such a heat-phase before a new distribution-release is scheduled, more days along no updates available. But with "yum update" I can see it. So with your explanation it could be the reason for that behaviour. Is this behaviour in past releases (Fedora 14) the same? Because when I remember back, this is not the case? Maybe I changed the settings in Fedora 14 for a long time to notify me once per day? And now I didn't change this setting on the new Fedora 15 Beta installation? I couldn't remember what I did (or not did) for a long time :-( If this is the case, then this is not a bug. And I understand this behaviour. Thank you Same here, in most of time Package-kit will not show any updates. I'm also having same problems. The issue here is that packagekit goes not show updates (not talking about the notification) even when i select the update application from the menu. Running 'yum update' does show and install updates. I feel at least the application should really show updates when i manually open it. (I've set update check period to hourly if thats relevant) Here's a thing which i feel is bug * open update from the menu, it shows no updates * do yum update on a terminal. 54 packages are updated If it can happen due to some setting/config changes then it'd be good to know what it is *** Bug 716596 has been marked as a duplicate of this bug. *** Thanks for the hint on the issue. Does that mean setting the gsettings value using dconf for the root user will be honoured by packagekit (In reply to comment #1) > We only do the notification of normal updates (e.g. not security updates) once > a week, no matter the checking frequency the user specified. Has it been more > than one week since you were notified? Ah that makes sense and it seems to work fine now (i.e just got a notification). What we should do though (re #716596) is to stop shipping an outdated man page (minor issue though). Sorry for the noise. Workaround: Install yum-updatesd. If nothing else, the gpk-prefs should be updated to reflect this behaviour. At least for me it's not obvious that "check for updates daily" really means that it will be checked once a week... (In reply to comment #6) > Please read > http://lists.fedoraproject.org/pipermail/test/2011-May/100468.html I don't know if you speak about the behaviour of update notifications or about the behaviour of gpk-update-viewer. In se second case, you mean gpk-update-viewer only show packages to update once a week except if we have security update? Can you clarify This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 |