Bug 131388
Summary: | updating hal system locks up | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Joseph Harnish <jharnish> |
Component: | hal | Assignee: | David Zeuthen <davidz> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | mclasen, nobody+pnasrat |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-12 16:45:37 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
Joseph Harnish
2004-08-31 20:43:34 UTC
Try downloading and installing the hal package with -Uvv. I suspect that you will find that the hang is occuring when the haldaemon process is restarted during package install. If so, that is a hal, not rpm/yum, problem. Is your machine hanging when haldaemon is restarted? I will try this. It may take a little bit after the last update. But from what I saw with YUM it died when it was running the post script. Once my system is back online I will test this. The daemon restart is what is done in %post. Reassigning to hal ... Did you have hal-0.2.97.cvs20040819 installed before the upgrade? If yes, you need to manually kill the haldaemon before upgrading. 'pkill hald' as root will achieve this. For more information see http://www.redhat.com/archives/fedora-test-list/2004-August/msg00785.html as this is a known issue with that version. Btw, one way to resolve this may be to kill the hal daemon, erase all duplicates of the hal package (so you only have one left) and manually upgrade to the latest version of hal which 0.2.97.cvs20040901-1. Since we haven't heard anything back for more than a week and I'm sure that the issues were caused by the bug mentioned that is already fixed I'm closing this bug. |