FS#17557 - hal-0.5.14-1, not start console-kit-daemon

Attached to Project: Arch Linux
Opened by ugaciaka (ugaciaka) - Sunday, 20 December 2009, 09:59 GMT
Last edited by Jan de Groot (JGC) - Sunday, 20 December 2009, 10:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
upgrade to hal-0.5.14-1. Hal not start console-kit-daemon.

Steps to reproduce:
Mount a pendrive:
Rejected send message, 1 matched rules; type="method_call", sender=":1.12" (uid=1000 pid=1195 comm="pcmanfm) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=557 comm="/usr/sbin/hald))
Directory doesn't exist!

my .xinitrc is
#!/bin/dash
exec ck-launch-session startxfce4

ck-launch-session want console-kit-daemon

see this topic http://bbs.archlinux.org/viewtopic.php?id=87123
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 20 December 2009, 10:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in consolekit 0.4.1-2. Launching consolekit through dbus activation no longer causes the first request to fail.
Comment by Jan de Groot (JGC) - Sunday, 20 December 2009, 10:31 GMT
I'm happy with this bug, as this bug finally shows the reason behind needing hal to get devicekit permissions working. I'll try to find out why dbus doesn't autostart consolekit when it's needed.