Bug 155710 - hald is not running
Summary: hald is not running
Alias: None
Product: Fedora
Classification: Fedora
Component: hal   
(Show other bugs)
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Zeuthen
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-22 14:14 UTC by David Balažic
Modified: 2013-03-06 03:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-03 20:51:13 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 David Balažic 2005-04-22 14:14:04 UTC
Description of problem:
I have a FC4test2 default install.

I logged in as plain user (to GNOME), selected menu : Desktop / Preferences /
Removable Drives and Media

I get an error dialog :
Volume management not supported

The "hald" service is required but not currently running. Enable the service and
rerun this applet, or contact your system administrator.

# ps -ef |grep hal
root      3264     1  0 19:31 ?        00:00:00 hald-addon-acpi
root      3273     1  0 19:31 ?        00:00:00 hald-addon-storage
root      3282     1  0 19:31 ?        00:00:00 hald-addon-storage
root      3286     1  0 19:31 ?        00:00:00 hald-addon-storage
root      3290     1  0 19:31 ?        00:00:00 hald-addon-storage
root      4067  3980  0 19:50 pts/3    00:00:00 grep hal

# service haldaemon status
hald is stopped

I have udev-057-1, the rest standard FC4t2, as on the official DVD.

Version-Release number of selected component (if applicable):

How reproducible:
After a reboot, the problem did not reappear (hald was running correctly). Did
not try more than once.

Comment 1 David Zeuthen 2005-05-03 20:51:13 UTC
Well, if you can't reproduce this or otherwise provide more useful about what is
wrong, there is no way I can fix this. To submit good bug reports please see


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