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
Sorry for replying in the older thread but this error caught me last night as well after cleaning some of the packages on my system
. 3.5 GB of space from packages that I never used but installed just in case... Cleaning them out saved me from moving to bigger HDD
...
I got an error just like YouCanToo about the non-existing file and the file existed just like in YouCanToo's case BUT... During boot time under Plymouth I have noticed a info about loop being detected between couple of services (avahi-daemon, and mandi for example) and a messagebus. After browsing logs I have confirmed the fact it was messagebus aka dbus related. I reinstalled dbus packages (never removed any of them - just wanted to make sure that they were installed properly and that the files were not damaged) and I still had that error. Then after a while I understood what the error at boot time meant... Messagebus was starting to late and all the services that were needing it to start properly were failing - this was the reason for my error message.
You can see boot messages in /var/log/boot.log as root.
I went to the /etc/rc5.d/ and listed it's content and sure enough messagebus was starting later then the packages that needed it. SO I renamed it with the mv command and I made sure that the number after S was smaller then on the packages that were complaining about the lack of messagebus.
Rebooted.
No more errors.
Errors in my case were caused by the order in which the services were starting. Why did the error occured in the first place? I probably had it all properly installed but since I removed services like apache and proftpd - order got messed up
. So yeah - me messing with the system was the main cause... ID Ten T error between the keyboard and the chair
... I am glad I have fixed it and since this thread existed I can add my solution to it.
Later I got rid of the loop between haldaemon and dm and all is peachy. System lost plenty of weight and I am not suffering from any annoyances!
PCLinuxOS - You rock
.
Andy
