[SOLVED] Error after latest system update

[YouCanToo]

After updating my system this afternoon, I started getting the following error after booting and before getting to the desktop.

Warning
Cannot open Consolekit Session: Unable to open session: failed to connect to socket /var/run/dbus system_bus_socket: No such file or directory

This is what I show for that path

[dwmoar@workbox ~]$ cd /var/run/dbus
[dwmoar@workbox dbus]$ ls -la
total 8
drwxr-xr-x  2 root root 4096 Mar  6 18:51 ./
drwxr-xr-x 25 root root 4096 Mar  6 18:51 ../
srwxrwxrwx  1 root root    0 Mar  6 18:51 system_bus_socket=
[dwmoar@workbox dbus]$

If I press the "OK" button when this error appears I can get to my desktop just fine.

Anyone have any ideas what might be going wrong here?

I am running KDE 4.6.1

[Viking]

I have the same problem. It shows me this error. 

When will the new distribution with KDE 4.6.1 iso?

[YouCanToo]

This issue has only happened to one of my machines. I have updated 8 out of the nine. (that last one is a hold out of KDE3.5)

[Texstar]

please rpm -qa |grep dbus in a terminals and let's see what you got installed?

[AS]

Warning
Cannot open Consolekit Session: Unable to open session: failed to connect to socket /var/run/dbus system_bus_socket: No such file or directory

Hi,
may be totally unrelated but I have seen a very similar error in another thread, the short story is that a KDE user end up with messed services names in /etc/rc5.d:

http://www.pclinuxos.com/forum/index.php/topic,88136.msg735855.html#msg735855

AS

[Texstar]

Warning
Cannot open Consolekit Session: Unable to open session: failed to connect to socket /var/run/dbus system_bus_socket: No such file or directory

Hi,
may be totally unrelated but I have seen a very similar error in another thread, the short story is that a KDE user end up with messed services names in /etc/rc5.d:

http://www.pclinuxos.com/forum/index.php/topic,88136.msg735855.html#msg735855

AS

KDE does not touch your startup services.

[AS]

KDE does not touch your startup services.

that's sure! but zhangyou say to have touched nothing to mess up his service names ... the error however is quite similar:
no file system_bus_socket but later when you check for existence of file it's there, that means messagebus is not started when error related to sys_bus_socket is shown.

AS

[YouCanToo]

please rpm -qa |grep dbus in a terminals and let's see what you got installed?

Here it is

[dwmoar@workbox ~]$ rpm -qa |grep dbus
libdbusmenu-qt2-0.6.4-1pclos2010
qt4-qtdbus-4.7.1-2pclos2010
libdbus-1_3-1.4.1-1pclos2010
python-dbus-0.83.2-1pclos2010
libdbus-glib-1_2-0.88-1pclos2010
dbus-1.4.1-1pclos2010
dbus-x11-1.4.1-1pclos2010
libeggdbus1_0-0.6-1pclos2010
libqtdbus4-4.7.1-2pclos2010
[dwmoar@workbox ~]$

[Old-Polack]

KDE does not touch your startup services.

that's sure! but zhangyou say to have touched nothing to mess up his service names ... the error however is quite similar:
no file system_bus_socket but later when you check for existence of file it's there, that means messagebus is not started when error related to sys_bus_socket is shown.

AS

People always say, "I didn't do anything," after they screw something up. It doesn't make it so, and it doesn't even mean they are aware of what they did. The end results says they did, whether they knew it or not.

[AS]

Hi All,

I read again the whole thread, and may be my posts sound a bit polemical, but i did not mean to be polemical. My apologies if it looked that way.

I just wanted to point out that what was described by YouCanToo is a starting point to search for the problem:

failed to connect to socket /var/run/dbus system_bus_socket: No such file or directory

srwxrwxrwx  1 root root    0 Mar  6 18:51 system_bus_socket=

to me, the above means that at time of ls -l messagebus service is already started, while look like not started at the time YouCanToo see the error. That's all.

@Old-Polack

People always say, "I didn't do anything," after they screw something up.

Of course, I know it very well, but I have learned to believe what they say, until there is proof it's not true.
May be I'm wrong, but I have seen several times to happen completely unexpected things as consequence of some bug.

AS

[Texstar]

please rpm -qa |grep dbus in a terminals and let's see what you got installed?

Here it is

[dwmoar@workbox ~]$ rpm -qa |grep dbus
libdbusmenu-qt2-0.6.4-1pclos2010
qt4-qtdbus-4.7.1-2pclos2010
libdbus-1_3-1.4.1-1pclos2010
python-dbus-0.83.2-1pclos2010
libdbus-glib-1_2-0.88-1pclos2010
dbus-1.4.1-1pclos2010
dbus-x11-1.4.1-1pclos2010
libeggdbus1_0-0.6-1pclos2010
libqtdbus4-4.7.1-2pclos2010
[dwmoar@workbox ~]$

libdbus-glib-1_2-0.88-1pclos2010
libdbus-1_3-1.4.1-1pclos2010
libqtdbus4-4.7.1-2pclos2010
dbus-1.4.1-1pclos2010
python-dbus-0.83.2-1pclos2010
qt4-qtdbus-4.7.1-2pclos2010
libeggdbus1_0-0.6-1pclos2010
libdbusmenu-qt2-0.6.4-1pclos2010
dbus-x11-1.4.1-1pclos2010

This is what is installed on my system.

Please check to make sure dbus is running in PCC. You can also delete the .dbus folder in your /home and reboot in case the permissions got messed up somewhere.

Another post on the forum said to uncheck the box to run /tmp in memory (ie clean tmp at each boot) fixed his issue.

I'll send up an udpated dbus package to the repos today just to see if it helps your situation.

One last thing. Is this a fairly recent system or something that is dated like P II or P III system.

[YouCanToo]

please rpm -qa |grep dbus in a terminals and let's see what you got installed?

Here it is

[dwmoar@workbox ~]$ rpm -qa |grep dbus
libdbusmenu-qt2-0.6.4-1pclos2010
qt4-qtdbus-4.7.1-2pclos2010
libdbus-1_3-1.4.1-1pclos2010
python-dbus-0.83.2-1pclos2010
libdbus-glib-1_2-0.88-1pclos2010
dbus-1.4.1-1pclos2010
dbus-x11-1.4.1-1pclos2010
libeggdbus1_0-0.6-1pclos2010
libqtdbus4-4.7.1-2pclos2010
[dwmoar@workbox ~]$

libdbus-glib-1_2-0.88-1pclos2010
libdbus-1_3-1.4.1-1pclos2010
libqtdbus4-4.7.1-2pclos2010
dbus-1.4.1-1pclos2010
python-dbus-0.83.2-1pclos2010
qt4-qtdbus-4.7.1-2pclos2010
libeggdbus1_0-0.6-1pclos2010
libdbusmenu-qt2-0.6.4-1pclos2010
dbus-x11-1.4.1-1pclos2010

This is what is installed on my system.

Please check to make sure dbus is running in PCC. You can also delete the .dbus folder in your /home and reboot in case the permissions got messed up somewhere.

Seems that the dbus is missing.  What do I need to do to make sure it is running?

Another post on the forum said to uncheck the box to run /tmp in memory (ie clean tmp at each boot) fixed his issue.

The clean tmp is unchecked.

I'll send up an udpated dbus package to the repos today just to see if it helps your situation.

One last thing. Is this a fairly recent system or something that is dated like P II or P III system.

The machine is just a little over a year old. It is a 2.6 Ghz AMD AM2+ with 2 gigs memory.

[YouCanToo]

UPDATE:

   Just updated my systems a few moments ago. I rebooted and the error that I was getting no longer appears. I still do not see dbus in pcc, like in the snapshot in the other post. Is this something that I really should worry about?

[Texstar]

UPDATE:

   Just updated my systems a few moments ago. I rebooted and the error that I was getting no longer appears. I still do not see dbus in pcc, like in the snapshot in the other post. Is this something that I really should worry about?

I'm sorry. dbus is called messagebus in the PCLinuxOS Control Center.

* Texstar riding the shortbus to the forum daily.

[YouCanToo]

Oh that would explain why I did not find it there  Anyway I will mark this solved, since the last update took care of this issue. Thanks for all the help.