Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#6351 - hald and gpm troubles with dbus 1.0.2

Attached to Project: Arch Linux
Opened by Flavien Bridault (vlaaad) - Tuesday, 06 February 2007, 11:06 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 06 February 2007, 11:49 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Since I updated dbus to 1.0.2, various problems appear with gnome-power-manager. Actually this is because hald crashes on the first launch at boot. But even after relaunching it by hand, I am still unable to hibernate or suspend. However this still work with the hibernate command, but then gpm often crashes. I would bet that this affect all hal dependent applications like gnome or thunar volume-manager, etc...

Other people reported similar troubles on the forum :

Feel free to ask for more details.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 07 February 2007, 16:46 GMT
Reason for closing:  Fixed
Comment by Martin Schmidt (Blind) - Tuesday, 06 February 2007, 15:47 GMT
To add another related topic:

This bug is somewhat annoying...
Comment by Jan de Groot (JGC) - Tuesday, 06 February 2007, 23:45 GMT
hal has been patched to not call evil invalid dbus operations on things that don't exist. This should fix the issues with hal and programs using its libraries that crash.
Comment by mutlu inek (mutlu_inek) - Wednesday, 07 February 2007, 01:59 GMT
I have a partially corrupted /etc/udev/rules.d/udev.rules file since the recent updates. The patch does not correct this.

See this topic:
Comment by mutlu inek (mutlu_inek) - Wednesday, 07 February 2007, 02:49 GMT
Actually, my comment and my post seem to lead to a udev bug.

I opened a bug report: