[avahi] client-browse-services.c fails: "Unexpected DBUS error occured"

[Lennart Poettering]

On Fri, 09.06.06 10:49, Nicholas Andrews (tar.bz2 at gmail.com) wrote:

> 
> Trent,
> 
> The --system dbus is indeed running. Looking at proc/<pid>/fd, I see 0
> through 12 files (named 0->12) but a "ls -l" shows that they either
> point to /dev/null or to a socket:[XXXX]. How should I fix this?

I don't know any way to map the kernel socket inode back to the path
it was created with.

However, you can use "strace -e connect" to track down which UNIX
socket it is avahi wants to connect to.

Lennart

-- 
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lennart/