After upgrading kde from 3.5x to 4.1 on my debian testing box, kdm refused to work. That is, I could log in,but all that happened was that the screen went blank for a moment, then I was back at the login prompt. After quite some googleing, I found the culprit to be the console-kit-daemon. After manually starting that, kdm worked fine again. gdm, on the other side had worked fine all the time. Then the next problem was to have console-kit-daemon to start automatically at boot time, to avoid having to force the rest of the family to start it manually if the box should be booted while I was not present. Oh and btw, kdm worked just fine with a box that was installed initially with the same versions of kde.<\/p>\n
console-kit-daemon is to be started from dbus, not a usual \/etc\/init.d script. everything seems to be fine with the dbus install, but I have both \/etc\/init.d\/dbus and \/etc\/init.d\/dbus-1, but in \/etc\/rc2.d\/ dbus is called first. Seems like that may be the problem. So far I have move \/etc\/rc2.d\/S12dbus to \/etc\/rc2.d\/not_S12dbus, but that didn’t seem to work. Back soon with some updates.<\/p>\n
A bit more updates: dbus-1 is an old package that has been uninstalled, but it seems like some cruft has been left over since that. But so far I have given in and made a startup script for console-kit-deamon:<\/p>\n
PATH=\/bin:\/usr\/bin:\/sbin:\/usr\/sbin test -x $DAEMON || exit 0<\/p>\n . \/lib\/lsb\/init-functions<\/p>\n case \"$1\" in exit 0 This script is saved as \/etc\/init.d\/console-kit. After upgrading kde from 3.5x to 4.1 on my debian testing box, kdm refused to work. That is, I could log in,but all that happened was that the screen went blank for a moment, then I was back at the … Continue reading
\n#! \/bin\/sh
\n### BEGIN INIT INFO
\n# Provides: console-kit-daemon
\n# Required-Start: $syslog $time $remote_fs
\n# Required-Stop: $syslog $time $remote_fs
\n# Default-Start: 2 3 4 5
\n# Default-Stop: 0 1 6
\n# Short-Description:
\n# Description: Debian init script for console-kit-daemon
\n#
\n### END INIT INFO
\n#
\n# Author: morten sickel, rewritten after Ryan Murray
\n#<\/p>\n
\nDAEMON=\/usr\/sbin\/console-kit-daemon<\/p>\n
\n start)
\n log_daemon_msg \"Starting console-kit-daemon\" \"ckd\"
\n start_daemon $DAEMON
\n log_end_msg $?
\n ;;
\n stop)
\n log_daemon_msg \"Stopping console-kit-daemon\" \"ckd\"
\n killproc $DAEMON
\nlog_end_msg $?
\n ;;
\n stop)
\n log_daemon_msg \"Stopping console-kit-daemon\" \"ckd\"
\n killproc $DAEMON
\n log_end_msg $?
\n ;;
\n force-reload|restart)
\n $0 stop
\n $0 start
\n ;;
\n *)
\n echo \"Usage: \/etc\/init.d\/console-kit {start|stop|restart|force-reload}\"
\n exit 1
\n ;;
\nesac<\/p>\n
\n<\/rmurray><\/code><\/p>\n
\nthen run
\n
\nchmod +x \/etc\/init.d\/console-kit
\nln -s \/etc\/inid.d\/console-kit \/etc\/rc2.d\/S98console-kit
\n<\/code>
\nThen it is started automatically in runlevel 2 which is debians default runlevel. I tried to call console-kit-daemon in the dbus startup script, but that did for some reason not work.<\/p>\n","protected":false},"excerpt":{"rendered":"