[ConsoleKit session] Failed to connect to socket (resolved)

Antione_7 · n00b Joined: 21 Jul 2011 Posts: 69 Location: México, D.F

Hi,

I just termated to install KDE, I reboot and I enter my login and password, but it appears an error message:

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.
_________________
Antoine,
Nationality: French

tetromino · Retired Dev Joined: 02 Dec 2003 Posts: 215

From the console, do
/etc/init.d/dbus restart

and see if there are any error messages. If dbus complains about missing machine-id and /etc/machine-id exists, you may need to
ln -sf /etc/machine-id /var/lib/dbus/machine-id

Antione_7 · n00b Joined: 21 Jul 2011 Posts: 69 Location: México, D.F

I did /etc/init.d/dbus restartand it's ok(not errors) but i rebot and entered my login and password, the problem is still here.

Thank you.
_________________
Antoine,
Nationality: French

tetromino · Retired Dev Joined: 02 Dec 2003 Posts: 215

If dbus works when started manually but doesn't start when you reboot, it probably means that you haven't added it to your default runlevel. Try the following:
rc-update add dbus default
rc-update add consolekit default

Antione_7 · n00b Joined: 21 Jul 2011 Posts: 69 Location: México, D.F

I did the both and it's ok thank you!!!
_________________
Antoine,
Nationality: French

cazort · Posted: Tue Aug 30, 2011 8:24 pm Post subject:

I just encountered this problem, and this "fix". Previous versions of KDE (i.e. <=4.4) did not seem to generate this error message. I just updated to 4.6.

Is this "feature creep" that is going to lead to bloat? I'd rather not use these daemons unless they're necessary.

Is there a way to disable this error message, or specify for KDE to not use these features?

I noticed that I was able to log in without consolekit running...it gave me an error message but everything seemed to work fine.
_________________
Alex Zorach | Teacology | RateTea | Why This Way