You are not logged in.
The problem is that when I try to log in via kdm screen gets black and I'm returned to kdm.
It's caused by ConsoleKit (anyway, why should I have to use HAL and ConsoleKit?!), because after rebuilding kdebase-workspace without consolekit it works agian. Anyway, should I add this as a bug report?
Xorg.0.log seems fine, but the end is little bit different than usually.
Normal Xorg.0.log:
(**) Keyboard0: CustomKeycodes disabled
(II) evaluating device (Mouse0)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) 3rd Button detected: disabling emulate3Button
Xorg.0.log after upgrade:
(**) Keyboard0: CustomKeycodes disabled
(II) evaluating device (Mouse0)
(II) evaluating device (Keyboard0)
(II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded
[config/dbus] couldn't register object path
(II) UnloadModule: "kbd"
(II) UnloadModule: "mouse"
daemon.log
Jan 7 10:05:19 red_dragon console-kit-daemon[2135]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:19 red_dragon console-kit-daemon[2206]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:21 red_dragon console-kit-daemon[2359]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:21 red_dragon console-kit-daemon[2424]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:21 red_dragon console-kit-daemon[2492]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:21 red_dragon console-kit-daemon[2557]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:21 red_dragon console-kit-daemon[2623]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:31 red_dragon kdm_greet[3350]: Cannot open default user face
Jan 7 10:05:36 red_dragon kdm: :0[3349]: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 0
Jan 7 10:05:36 red_dragon kdm: :0[3349]: Client start failed
Jan 7 10:05:36 red_dragon kdm: :0[3349]: Cannot close ConsoleKit session: Unable to close session: no session open
Jan 7 10:05:36 red_dragon console-kit-daemon[3365]: CRITICAL: cannot initialize libpolkit
Jan 7 10:05:39 red_dragon kdm_greet[3432]: Cannot open default user face
errors.log
Jan 7 10:05:31 red_dragon kdm_greet[3350]: Cannot open default user face
Jan 7 10:05:36 red_dragon kdm: :0[3349]: Cannot open ConsoleKit session: Unable to open session: Launch helper exited with unknown return code 0
Jan 7 10:05:36 red_dragon kdm: :0[3349]: Client start failed
Jan 7 10:05:36 red_dragon kdm: :0[3349]: Cannot close ConsoleKit session: Unable to close session: no session open
Jan 7 10:05:39 red_dragon kdm_greet[3432]: Cannot open default user face
ConsoleKit/history
1231319119.043 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
1231319119.497 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
1231319121.089 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
1231319121.108 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
1231319121.166 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
1231319121.190 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
1231319121.213 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
1231319136.715 type=SEAT_ADDED : seat-id='Seat1' seat-kind=0
Last edited by 6xx (2009-01-07 11:53:14)
Offline
Same thing here. But starting KDE from the console with startx is possible.
Offline
Same thing here. But starting KDE from the console with startx is possible.
Yeah, but it's uncomfortable and some members of my family don't know how to login and startx using console.
Offline
thats when my problems started after the last update of kdebase-workspace.
still haven't gotten it to work yet
Offline
Have you tried restarting the dbus service? Here kdm works ok.
In love I believe and in Linux I trust
Offline
Of course, several times.
Offline
I've seen that the new kde-workspace had a new kdmrc and I've merged the differences between my old kdmrc and kdmrc.pacnew. That's the only thing I think I've done after the upgrade. And when I first logged in I remember it threw me away and restarted KDM. But the second and subsequent logins were ok.
In love I believe and in Linux I trust
Offline
Hi, after research a bit what I have to do to get my kdm up and running I discover that, the only thing I have to do is execute console-kit somewhere, after that, kdm works perfect.
So maybe, (I have no idea, only maybe) the last update remove the auto execution of console-kit, or add that dependency.
Offline
As Jan de Groot (JGC) comments on http://bugs.archlinux.org/task/12702
the permissions and groups for /usr/lib/dbus-1.0/dbus-daemon-launch-helper should show up like this:
-rwsr-x--- 1 root dbus 46056 2008-11-28 20:35 /usr/lib/dbus-1.0/dbus-daemon-launch-helper
I changed mine and now kdm works fine:
# chown root:dbus /usr/lib/dbus-1.0/dbus-daemon-launch-helper
# chmod u+s /usr/lib/dbus-1.0/dbus-daemon-launch-helper
Offline
I've found out that the problem was in missing inotify support in my kernel. Now everything works fine.
Offline