Help in debugging a crashing hald on startup
Andy Jones
andy at hasbox.com
Sat Oct 6 12:42:35 PDT 2007
Hi Dan,
No the prolem wasn't dbus that was not running (if it wasn't you'd get a
socket error much earlier on).
The problem is in SVN but it seem the developers are not interested in
bug reports.
I reverted to non-svn (i.e. 0.5.9.1) hal and it work fine again.
Thanks for taking the time to reply anyhow.
rgds
Andy
-------- Original Message --------
Subject: Re: Help in debugging a crashing hald on startup
Date: Mon, 1 Oct 2007 08:02:56 -0700
From: Dan Nicholson <dbn.lists at gmail.com>
To: Andy Jones <andy at hasbox.com>
References: <47001E20.8060604 at hasbox.com>
On 9/30/07, Andy Jones <andy at hasbox.com> wrote:
> 02:03:18.156 [I] hald_runner.c:301: Runner has pid 8503
> 02:03:18.157 [W] ci-tracker.c:299: Could not get uid for connection:
> org.freedesktop.DBus.Error.NameHasNoOwner Could not get UID of name
> 'org.freedesktop.DBus': no such name
> 02:03:18.157 [E] hald_dbus.c:4944: Cannot get caller info for
> org.freedesktop.DBus
Is dbus running? It seems that dbus_bus_get_unix_user is failing. I
don't know if this is the root of your problems, but it seems like HAL
won't operate correctly without this.
--
Dan
More information about the hal
mailing list