Description of problem: With recent kdm the autologin isn't possible on first start of kdm right after boot. If you switch to a tty and kill -9 kdm the autologin would succeed. Version-Release number of selected component (if applicable): kdm-4.3.85-1.fc13 How reproducible: ever Steps to Reproduce: 1. run a recent nightly build of the kde images. 2. boot 3. Actual results: no autologin Expected results: autologin
Just forgotten: There is no relevant output in kdm.log or /var/log/messages for this.
blocking kde-4.4 tracker (may move to F13Blocker-kde later, if this ends up being f13/rawhide specific).
Created attachment 379860 [details] /var/log/messages I've attached /var/log/messages. These lines appear when the user isn't logged in automatically: Dec 22 17:18:45 localhost kdm: :0[1533]: Cannot open ConsoleKit session: Unable to open session: Method "OpenSessionWithParameters" with signature "a(sv)" on interface "org.freedesktop.ConsoleKit.Manager" doesn't exist Dec 22 17:18:45 localhost kdm: :0[1533]: Client start failed Dec 22 17:18:45 localhost kdm: :0[1533]: Cannot close ConsoleKit session: Unable to close session: no session open After killing kdm there is no kdm related output (I've put a line as a marker in the attached messages).
OK, similar symptoms as bug #545639 (and dup'd bug #545267 ) then, ie, ConsoleKit failing on the first attempt. rpm -q ConsoleKit dbus hal please. given that we can double check whether this is addressed in rawhide yet.
ConsoleKit-0.4.1-3.fc13.i686 hal-0.5.14-1.fc13.i686 dbus-1.2.16-8.fc12.i686 Full package list: http://www.deadbabylon.de/fedora/livecd/packagelists/f13/long-F13-KDE-012-i686.txt
Re-assigning to ConsoleKit, seems the ck_connector_open_session_with_parameters call here is failing, dbus_error_init( &error ); ckStatus = ck_connector_open_session_with_parameters( ckConnector, &error, "unix-user", &p->pw_uid, "x11-display-device", &ckDevice, "x11-display", &td->name, "is-local", &isLocal, /* meaning not entirely clear per doc */ # ifdef XDMCP "remote-host-name", remoteHostName ? (const char **)&remoteHostName : &spaceStr, # endif (char *)0 );
Hi all... I have same problem, with the no-password option in Kdm. When I am on lo-gin screen, I press "Enter", I have a black screen and return on lo-gin screen. I re-press "Enter" and My session launch. With password option in Kdm, no problem. Trace in /var/log/message: Dec 23 17:44:39 localhost kdm: :0[1379]: Cannot open ConsoleKit session: Unable to open session: Method "OpenSessionWithParameters" with signature "a(sv)" on interface "org.freedesktop.ConsoleKit.Manager" doesn't exist Dec 23 17:44:39 localhost kdm: :0[1379]: Client start failed Dec 23 17:44:39 localhost kdm: :0[1379]: Cannot close ConsoleKit session: Unable to close session: no session open Dec 23 17:44:43 localhost acpid: client 1352[0:0] has disconnected Dec 23 17:44:43 localhost acpid: client connected from 1467[0:0]
Looks like the versions of libck-connector and ConsoleKit in Rawhide are not compatible with each other.
Ping? Are the versions of libck-connector and ConsoleKit in Rawhide not compatible with each other?
davidz thinks this is related to dbus activation (ala bug #545267), but I'd have assumed that should be fixed in rawhide already. If that's the expectation, then this bug serves to dispell that notion.
The strange things are: * F12 has the same version of ConsoleKit as F13, so is this also happening on F12? * libck-connector and the ConsoleKit daemon come from the same tarball, how can they get out of sync?
Hmmm, why does it say 'Method "OpenSessionWithParameters" with signature "a(sv)" on interface "org.freedesktop.ConsoleKit.Manager" doesn't exist'? That method is definitely there, maybe access is getting blocked by some security policy?
*** Bug 563603 has been marked as a duplicate of this bug. ***
There's a good chance this is the kdm equivalent of gdm bug #555593
*** Bug 560465 has been marked as a duplicate of this bug. ***
I can no longer reproduce "only 2nd login works" on F13. Maybe ConsoleKit-0.4.1-5.fc13.x86_64 fixed it?
I bet so. *** This bug has been marked as a duplicate of bug 555593 ***
I confirm comment 17 from Sven Lankes, I update to ConsoleKit-0.4.1-5.fc13.x86_64 and now that work fine...