Bug 822430
| Summary: | PK is stuck after installing a single update | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||
| Component: | PackageKit | Assignee: | Richard Hughes <hughsient> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | awilliam, hughsient, jens.hoelldampf, jonathan, rdieter, robatino, rvitale, satellitgo, smparrish, stefan.hoelldampf, tflink | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | RejectedBlocker, AcceptedNTH | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-01-23 09:48:15 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 752653 | ||||||
| Attachments: |
|
||||||
|
Description
Kamil Páral
2012-05-17 10:30:59 UTC
Created attachment 585162 [details]
gpk-update-viewer stuck
pkmon output is displayed in the terminal
Let's discuss whether this is a blocker. I have waited at least 10 minutes and the PK didn't get unstuck. Reboot seems truly necessary. Criterion: "The installed system must be able to download and install updates with yum and the default graphical package manager in all release-blocking desktops" https://fedoraproject.org/wiki/Fedora_17_Alpha_Release_Criteria Reproduced precisely as described. Note that when PK finishes installing the single update and refreshes to a blank grey update list, it still claims that one update is selected. When you quit and re-run, it's stuck as Kamil describes, it doesn't claim any updates are selected. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Discussed at the 2012-05-17 Fedora 17 final go/no-go meeting. This doesn't completely hit any of the Fedora 17 release criteria and has a simple workaround - install all of the updates. Thus it can be fixed by an update and does not need to block release. However, it does cause problems with certain update use cases and would be considered for freeze break. Separate patches and/or builds for the different PK issues are requested so that they can be evaluated individually. I have done a clean F17 RC1 installation. Then I have downgraded two packages (gedit and shotwell) by downloading older build from koji. Then I used gpk-update-viewer to update one of those packages. The the second one. Surprisingly, everything worked perfect. After that I followed the original reproducer (enable updates-testing and select one package) and it got stuck again. So this is not deterministic, it might depend on the current state of repositories and state of the update set. I wonder whether there is a use case we haven't considered when deciding blocker-ness. Maybe PK will get stuck even if we update all available packages, and then after a day or two another set of updates appears (some people don't reboot, just suspend, so it would be the same session). But this is hard to test - as I said, the issue is not deterministic. When I was testing the PackageKit builds for #794927, PackageKit stalled when I had all of the builds from updates-testing selected for updates. I started the updates, imported the needed keys and PK stalled about halfway through. We still don't know how often this is going to happen but with the new information, I'm moving this back to proposed. Discussed in the 2012-05-18 blocker bug review meeting. Rejected as a blocker for Fedora 17 final because while this could be a problem - there is only one reporter of a blocker-worthy issue and there is no debug information to work off of. Kamil, did you ever reproduce this again? Seems like we could close it out as CLOSED MAGICPIXIESINMYBOX.... I have tested it in F18 and it works well, let's just close. |