Re: dbus issue

[lina <lina.lastname@gmail.com>]

On Fri, Dec 2, 2011 at 2:33 AM, Michael Biebl <biebl@debian.org> wrote:
> First of all, it is helpful to know if you are running (an up-to-date)
> squeeze, wheezy or sid system.
>
> On 01.12.2011 15:49, lina wrote:
>> (it's related to former thread, but also different)
>>
>> Here the problem,
>>
>> gdm3 restart
>>
>> showed me Could not connect to system bus: failed to connect to socket
>> /var/run/dbus/system_bus_socket: no such file or directory
>>
>> actually there is no /dbus directory under /var/run
>>
>> I checked the dbus and related libs seems installed, or might still
>> lack someone,
>
> On wheezy and sid /run is a volatile tmpfs nowadays, and /var/run and
> /var/lock are symlinks pointing to /run resp. /run/lock.
>
> What is the output of ls -l /var/run and ls -l /var/lock ?
lrwxrwxrwx 1 root root 4 Jul 25 17:34 /var/run -> /run

ls -l /var/lock
lrwxrwxrwx 1 root root 9 Jul 25 17:34 /var/lock -? /run/lock

> The /var/run/dbus directory is created by the dbus init script. Do you
> start dbus in /etc/rc?.d/?

> ls -ls /etc/rcS.d and /etc/rc?.d  and the output of service dbus status
> will be helpful, too.

I removed the gnome and the gdm3 yesterday.

later realized it might something still back to fglrx-driver.

without gnome and gdm3, the above output will still have some meanings?

btw
# /etc/rc?/d? start
bash: /etc/rc?.d/?: No such file or directory.
# /etc/rc?.d/dbus start
bash: /etc/rc?.d/dbus: No such file or directory



>
>
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>