Summary: | [kdm + consolekit problem] auto logon does not work | ||
---|---|---|---|
Product: | [Unmaintained] kdm | Reporter: | felix <out.there> |
Component: | general | Assignee: | kdm bugs tracker <kdm-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | out.there, yuri |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
felix
2009-12-16 21:44:58 UTC
i deem it much more likely that the kde session just immediately creashes. check the timestamp of ~/.xsession-errors and have a look at daemon.log and kdm.log in /var/log. You might be right: daemon.log Dec 17 06:34:12 laptop kdm: :0[2058]: Cannot open ConsoleKit session: Unable to open session: Method "OpenSessionWithParameters" with signature "a(sv)" on interface "org.freedesktop.ConsoleKit.Manager" doesn't exist Dec 17 06:34:12 laptop kdm: :0[2058]: Client start failed Dec 17 06:34:12 laptop kdm: :0[2058]: Cannot close ConsoleKit session: Unable to close session: no session open IS this bug a duplicate of something else? blah, that's kdm's slightly broken consolekit integration. i'm aware of bugs in that area, but i don't remember whether they are filed on bugzilla. SVN commit 1093647 by ossi: make ConsoleKit failure non-fatal libck-connector sucks at error reporting, so we cannot tell whether no ck daemon is running (which would be kinda fine) or whether talking with it failed (which would be a bit worse). so choose the less disruptive whole-sale solution. BUG: 218983 M +9 -2 client.c WebSVN link: http://websvn.kde.org/?view=rev&revision=1093647 *** Bug 235605 has been marked as a duplicate of this bug. *** |