On Mon, Jun 05, 2006 at 11:49:45PM +0200, Tim Dijkstra (tdykstra) wrote:
> Package: dbus
> Version: 0.61-5
> Severity: important
>
>
> For a certain class of users on my systems apps that need dbus to start
> fail to do so. The symptom is as follows:
>
> [EMAIL PROTECTED]:~$ hal-device
> error: dbus_bus_get: org.freedesktop.DBus.Error.NoReply: No reply within
> specified time
>
> The user test only lives on a LDAP server, it has no /etc/passwd entries. If
> I add an entry there all is well. So this sounds like a timeout issue, but if
> I read the source correctly (which could very well not be the case;)
> dbus_bus_get in the end calls _dbus_pending_call_new with a timeout value -1
> which means 25 seconds. And the hal-device commands only takes a short while
> to complete, certainly not 25s.
I'm running various machines with ldap users and i never had any such problems
there. So it's not inherent to dbus with ldap.
Does the following also cause a timeout?:
$ dbus-send --print-reply --system --type=method_call
--dest=org.freedesktop.DBus.Peer / org.freedesktop.DBus.Peer.Ping
If so could you attach a strace of that command ?
Sjoerd
--
The biggest difference between time and space is that you can't reuse time.
-- Merrick Furst
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
