Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 177932 - gnome-power-manager doesn't survive haldaemon restarting
Summary: gnome-power-manager doesn't survive haldaemon restarting
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
Blocks: FC5Target
TreeView+ depends on / blocked
Reported: 2006-01-16 16:17 UTC by Jonathan Blandford
Modified: 2013-04-02 04:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-13 23:36:34 UTC

Attachments (Terms of Use)

Description Jonathan Blandford 2006-01-16 16:17:56 UTC

Comment 1 Richard Hughes 2006-01-16 16:38:58 UTC
Any ideas on how this can be done? Should g-p-m just wait around until hal is
started again, or is this a race? Or for a fixed timeout (say 5 seconds) --
ideas please.

Thanks, Richard.

Comment 2 Jonathan Blandford 2006-01-16 16:56:13 UTC
NetworkManager seems to survive haldaemon dying; might make sense to take a look
at that code to see what it is doing.

Comment 4 Richard Hughes 2006-01-16 22:35:35 UTC
Thanks for the link, I'll see what I can do. This sortof depends on, but I'll fix it in the currect
structure asap.

Comment 5 Leslie Satenstein 2006-01-27 03:50:01 UTC
HalDaemon does not start after patch received for it (Test 2 vanilla version
worked OK)

As result, GNOME POWER MANAGER does not work. (CORE5 TEST2)

Comment 6 Leslie Satenstein 2006-01-27 03:53:19 UTC
Hal Daemon appeared to work on my system with initial release of Core5 Test2.
Then a patch arrived, and as a result of applying patch, HalDaemon fails to start.

When it fails to start, GNOME POWER MANAGER (for UPS monitoring) fails to start
as well.

Comment 7 Christopher Aillon 2006-02-01 18:41:52 UTC
Just curious what the status here is Richard.

Comment 8 Leslie Satenstein 2006-02-01 18:59:47 UTC
Since I am not a linux internals man, I can only report what I see. My IT skills
are in other areas.

Is there a link between the HAL daemon and GNOME POWER MANAGER, or am I
detecting coincidences?


Comment 9 Richard Hughes 2006-02-01 23:54:42 UTC
I'm working on this at the moment, but it required refactoring other parts of
the code.

And Leslie, checkout


Comment 10 Richard Hughes 2006-02-13 23:36:34 UTC
Now fixed in CVS.

2006-02-13 Richard Hughes <>
 * src/gpm-hal-monitor.c (gpm_hash_new_devices_cache,
gpm_hash_free_devices_cache): Add these so we can simplify our memory
management. We need to be more careful that what we were, as hal could be
restarted many times and we could loose lots of memory.
 (hal_monitor_stop): Inline into _finalize, as not called elsewhere.
 * src/gpm-hal.c (gpm_hal_enable_power_save): valgrind (quite rightly) warns of
use before set. Just initialise ret to zero.
 * src/gpm-power.c (battery_device_cache_entry_free) remove, as broken.
 (gpm_hash_new_kind_cache, gpm_hash_free_kind_cache, gpm_hash_new_device_cache,
gpm_hash_free_device_cache): Add these so we can simplify our memory management,
and not forget to free.
 (gpm_power_init): Listen for the hal-disconnected signal so we can clear the
caches, else the devices think they are initialised.
 Fixes bug #327234.

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