[Pkg-utopia-maintainers] Bug#444668: Bug#444668: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

[Andrey Golovin]

У сб, 2007-11-17 у 13:27 +0100, Sjoerd Simons пише:
> On Mon, Oct 01, 2007 at 12:02:49AM +0200, Michael Biebl wrote:
> > Andrey Golovin schrieb:
> > > ?? ????, 2007-09-30 ?? 14:09 +0200, Michael Biebl ????????:
> > >> Andrey Golovin schrieb:
> > >>> Package: dbus
> > >>> Version: 1.1.1-3
> > >>> Severity: normal
> > > 
> > >> Please check, if you have the file /var/run/dbus/system_bus_socket. Post
> > >> the output of
> > >>
> > >> ls -la /var/run/dbus/
> > >>
> > >> Cheers,
> > >> Michael
> > > $ ls -la /var/run/dbus/
> > > total 1
> > > drwxr-xr-x  2 messagebus messagebus  48 2007-09-30 22:34 .
> > > drwxr-xr-x 18 root       root       520 2007-09-30 22:34 ..
> > > andy at andygol:~$ 
> > 
> > There is clearly something wrong with your running dbus daemon.
> > 
> > Please restart dbus (/etc/init.d/dbus restart) and check /var/run/dbus
> > again.
> > 
> > You should have have a system_dbus_socket and pid file there.
> 
> The only things i can think of is that either the disk was full when dbus was
> started (thust causing it to be unable to create the necessary files..) or that
> /var/run was read-only. In the first case a more gracefull error would probably
> be nice, in the second case it's a user error.
> 
> But we definately need more info about this one indeed (especially if it keeps
> happening or if it was a onetime thing)
> 
>   Sjoerd
I have enough disk space when dbus is started
$ df -a /dev/sdb1
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sdb1             17068464   6732696  10335768  40% /

Here is right for /var/run/dbus dir

$ ls -la /var/run/dbus/
total 1
drwxr-xr-x  2 messagebus messagebus  48 2007-11-27 21:36 .
drwxr-xr-x 19 root       root       552 2007-11-27 21:36 ..

User 'root' is a member of 'messagebus' group.
what right need for /var/run/dbus/?

This problem keep happening regular at last times.
Upgrading dbus up to version 1.1.2-1 don't resolve this problem.