https://bugzilla.novell.com/show_bug.cgi?id=331002#c16
Martin Wilck changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martin.wilck@fujitsu-siemens.com
--- Comment #16 from Martin Wilck 2007-10-24 05:14:15 MST ---
I had the same problem. Making matters worse, both haldaemon and consolekit
were not running (rchaldaemon status -> "unused").
Apparently this is due to dbus being started asynchronously by
/etc/init.d/dbus, so that the rc script may finish before is dbus actually
available, causing subsequent dependent services to fail (fail SILENTLY though,
there were no error messages from the rc scripts).
I put a "sleep 2" statement in /etc/init.d/haldaemon, and it helped. The hint
in bug 333735, comment #12 should also cause dbus invocation to be serialized
if I understand it correctly, but the reporter there said it didn't help.
In my case, the delays in dbus startup were apparently caused by a problem in
the ConsoleKit package. /etc/dbus-1/system.d/ConsoleKit.conf refers to a user
gdm who didn't exist on my system (KDE installaiton, no gdm package installed).
This caused an error message "" to be displayed by dbus, and may have caused a
delay of some sort, too. Here is a boot.msg excerpt:
Starting D-Bus daemondone
<notice>startproc: execve (/usr/sbin/console-kit-daemon) [
/usr/sbin/console-kit-daemon ], [ CON
SOLE=/dev/console ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0
LC_ALL=POSIX INIT_VE
RSION=sysvinit-2.86 REDIRECT=/dev/tty1 COLUMNS=124
PATH=/bin:/sbin:/usr/bin:/usr/sbin vga=0x317
RUNLEVEL=2 PWD=/
SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1024x768.cfg PREVLEVEL=
N LINES=44 HOME=/ SHLVL=2 splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/dm-0
_=/sbin/startproc DAE
MON=/usr/sbin/console-kit-daemon ]
Starting ConsoleKitdone
acpid: 2 rules loaded
Starting HAL daemonChecking/updating CPU microcode done
<notice>startproc: execve (/usr/sbin/hald) [ /usr/sbin/hald --daemon=yes ], [
CONSOLE=/dev/conso
le ROOTFS_FSTYPE=ext3 SHELL=/bin/sh TERM=linux ROOTFS_FSCK=0 LC_ALL=POSIX
INIT_VERSION=sysvinit-
2.86 REDIRECT=/dev/tty1 COLUMNS=124 PATH=/bin:/sbin:/usr/bin:/usr/sbin
vga=0x317 RUNLEVEL=2 PWD=
/ SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1024x768.cfg
PREVLEVEL=N LINES=44 HOME
=/ SHLVL=2 splash=silent SPLASH=yes ROOTFS_BLKDEV=/dev/dm-0 _=/sbin/startproc
DAEMON=/usr/sbin/h
ald ]
done
Loading CPUFreq modulesUnknown username "gdm" in message bus configuration file
done
It can be seen that the dbus rc script exits, and much later (after the hal
daemon was started), the dbus error msg about the "gdm" user is diplayed.
At least, since I installed gdm, the error has disappeared for me. Nevertheless
I reckon that it could still unless the dbus startup script is fixed. It needs
to wait until dbus is fully initialized before it exits. The "fix" to install
gdm (or just create a "gdm" user) isn't solid.
So, 2 problems here:
1 dbus rc script must not exit before dbus is really up
2 ConsoleKit shouldn't refer to the "gdm" user (or depend on the gdm package,
which would be annoying for KDE users)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.