Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-17 Thread Bob Proulx
Sven Uhlig wrote: > Bob Proulx wrote: > > getent baldur.asgard > > That is why I used C's getnameinfo(). > > How should getent work? > > # getent baldur.asgard > Unknown database: baldur.asgard Sorry. That was a bad example on my part. The first parameter is the map name and the second is the

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-17 Thread Sven Uhlig
On 17.03.2013 03:12, Bob Proulx wrote: > Sven Uhlig wrote: >> Bob Proulx wrote: The problem is that "su" takes 25 seconds before it succeeds. >>> >>> That sounds like a DNS timeout. If you do a dns lookup of your >>> systems hostname does it respond? >> >> # nslookup baldur ** server c

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-17 Thread Sven Uhlig
On 17.03.2013 02:53, Clive Standbridge wrote: >> The reasons seems to be my setup of the system. >> Debian runs in a VirtualBox environment, headless and w/o X server. >> I use ssh to connect to the system. (putty) >> I use X forwarding to run X applications on the system. >> The variable $DISPLAY

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-16 Thread Clive Standbridge
> The reasons seems to be my setup of the system. > Debian runs in a VirtualBox environment, headless and w/o X server. > I use ssh to connect to the system. (putty) > I use X forwarding to run X applications on the system. > The variable $DISPLAY gets set to 10.0.2.2:0 after ssh auth. Sven, I'm

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-16 Thread Bob Proulx
Sven Uhlig wrote: > Bob Proulx wrote: > >> The problem is that "su" takes 25 seconds before it succeeds. > > > > That sounds like a DNS timeout. If you do a dns lookup of your > > systems hostname does it respond? > > # nslookup localhost > Name: localhost > Address: 127.0.0.1 > > # nslookup 1

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-16 Thread Sven Uhlig
On 16.03.2013 05:45, Bob Proulx wrote: >> The problem is that "su" takes 25 seconds before it succeeds. > > That sounds like a DNS timeout. If you do a dns lookup of your > systems hostname does it respond? # nslookup localhost Name: localhost Address: 127.0.0.1 # nslookup 127.0.0.1 1.0.0.127.

Re: "su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-15 Thread Bob Proulx
Sven Uhlig wrote: > this is my first message to this list. Welcome. > I noticed a little problem on my system after I installed the package > "virt-manager" and its dependencies on my system. One of the > dependencies is "dbus". Ugh. "dbus". I feel your pain. Too many applications have egregi

"su" - timeout for dbus/system_bus_socket if $DISPLAY set but unreachable

2013-03-15 Thread Sven Uhlig
Hello, this is my first message to this list. I noticed a little problem on my system after I installed the package "virt-manager" and its dependencies on my system. One of the dependencies is "dbus". The problem is that "su" takes 25 seconds before it succeeds. Using strace I think I identifie