When I boot my system since recent updates to 12.2 GM I
get several errors messages.
First message on boot:
Code
Failed to connect to the D-Bus daemon: Failed to connect
to socket /var/run/dbus/system_bus_socket: No such file
or directory
/Code
I also see a simular message when I do the following
command from the command line as su -:
Code
/usr/bin/ck-list-sessions
Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or
directory
/Code
A search of my system fails to find the /var/run/dbus/system_bus_socket
anywhere. I do find /Run in root but no dbus. A search for dbus finds
references in:
Code
But no reference to the socket. I assume this is some recent change. It
was working on RC2 and earlier than last Friday in GM. A search of
Bugzilla did not turn this failure but the were several that maybe
related.
Here are some of the errors I see in system log:
Code
09/12/12 05:34:46 PM linux-9wvj kernel 47.422890] NVRM:
corruption and stability problems, and is not supported.
09/12/12 05:34:47 PM linux-9wvj acpid 1 client rule loaded
09/12/12 05:34:57 PM linux-9wvj kdm :0[3957]: Cannot open
ConsoleKit session: Unable to open session: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
09/12/12 05:35:01 PM linux-9wvj kdm :0[3957]:
pam_systemd(xdm:session): Failed to connect to system bus: Failed to
connect to socket /var/run/dbus/system_bus_socket: No such file or
directory
09/12/12 05:35:03 PM linux-9wvj checkproc checkproc: can
not get session id for process 4621!
09/12/12 05:35:08 PM linux-9wvj pulseaudio[4136]
[pulseaudio] core-util.c: Failed to connect to system bus: Failed to
connect to socket /var/run/dbus/system_bus_socket: No such file or
directory
09/12/12 05:35:09 PM pulseaudio[4136] last message
repeated 10 times
09/12/12 05:35:09 PM linux-9wvj pulseaudio[4136] [alsa-
sink] core-util.c: Failed to connect to system bus: Failed to connect to
socket /var/run/dbus/system_bus_socket: No such file or directory
09/12/12 05:35:09 PM pulseaudio[4136] last message
repeated 4 times
09/12/12 05:35:09 PM linux-9wvj pulseaudio[4136]
[pulseaudio] bluetooth-util.c: Failed to get D-Bus connection: Failed to
connect to socket /var/run/dbus/system_bus_socket: No such file or
directory
09/12/12 05:35:09 PM linux-9wvj pulseaudio[4136]
[pulseaudio] module.c: Failed to load module “module-bluetooth-discover”
(argument: “”): initialization failed.
09/12/12 05:35:09 PM linux-9wvj pulseaudio[4136]
[pulseaudio] main.c: Module load failed.
09/12/12 05:35:09 PM linux-9wvj pulseaudio[4136]
[pulseaudio] main.c: Failed to initialize daemon.
09/12/12 05:35:09 PM linux-9wvj pulseaudio[4131]
[pulseaudio] main.c: Daemon startup failed.
09/12/12 05:35:10 PM linux-9wvj kernel 70.669769] fuse init
(API version 7.18)
\Code
It appears of errors I see later in boot could be related to this.
Any Idea what to look at next? I will report bug tomorrow.
Hi upscope. I assume your configured repos are all in order. Not sure what might have failed with your upgrade to GM, but may be worth trying ‘zypper dup’ perhaps?
Another workaround, (assuming it is systemd that is not starting the required console-kit-daemon.service or similar), might be to try reverting to sysvinit
>
> Hi upscope. I assume your configured repos are all in order. Not sure
> what might have failed with your upgrade to GM, but may be worth
> trying ‘zypper dup’ perhaps?
>
> Another workaround, (assuming it is systemd that is not starting the
> required console-kit-daemon.service or similar), might be to try
> reverting to sysvinit
>
> ‘openSUSE:Managing Systemd - openSUSE’
> (http://en.opensuse.org/openSUSE:Managing_Systemd)
>
> Does that make a difference to getting a working desktop?
>
>
Thanks, I’ll try that later today, I forgot about tat. The Gm had been
running fine since it came out, untill I did some updates this last
Sunday and Monday. Noticed Tuesday.
i was wondering if it could have been caused by the pulse audio stuff
since Akonadi had a problem that I solved. Also Power Management reports
an error. on Start of KDE.
>
> Hi upscope. I assume your configured repos are all in order. Not sure
> what might have failed with your upgrade to GM, but may be worth
> trying ‘zypper dup’ perhaps?
Tried, no help
>
> Another workaround, (assuming it is systemd that is not starting the
> required console-kit-daemon.service or similar), might be to try
> reverting to sysvinit
system said consolekit is running. Tried stopping and starting, no help.
Rebooted using sysvinit. Still had problem.
>
> ‘openSUSE:Managing Systemd - openSUSE’
> (http://en.opensuse.org/openSUSE:Managing_Systemd)
>
> Does that make a difference to getting a working desktop?
>
>
After much playing I decided to install KDE 4.8.5 on my openSUSE
12.1.and rebooted. I got the same errors fron Consolekit as described in
original post on 12.2 GM. Then updated to 9.1 on 12.1, no help still
what I thought were consolekit caused errors:
MyComputer did not display any disk drives or cdroms.
K3B could not find an optical drive.
Dolphin did not display any disks or cdroms.
Have been others also.
YaST–> Hardware info showed all the disk drives and cdrom. Also YaST
Partitioner also showed all the drives.
I then dropped 12.1 back to 4.8.4 Release “2”. All problems went away
after reboot. No more consolekit error or power management error on
reboot. Above problems all fixed also.
Tried same on 12.2 (used oss repo) to 4.8.4 Release “2”
No more problems.
I will search bugzilla for problems but I’m not sure if it is a bad
consolekit (I did not reinstall it) or something in KDE.
Thanks for your help. Any Idea how to isolate what in KDE could cause
this?
