Summary: | only one attemp to login by KDM | ||
---|---|---|---|
Product: | kdm | Reporter: | Sergei LITVINENKO <sergei.litvinenko> |
Component: | general | Assignee: | kdm bugs tracker <kdm-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | CC: | rdieter, sergei.litvinenko, sergio, zejdl |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
empty password - first time, no crash
empty password - second time, crash kdm with -debug 15, daemon.* |
Description
Sergei LITVINENKO
2010-06-05 11:36:43 UTC
I got same issue on F13 fully updated, curiosity if I fail more than one time , don't happen. This is not easy to debug , any help how I debug this is appreciated . the daemon.* syslog facility should give some clue. for improved debugging results, please restart kdm with -debug 15. some more details are in the kdm README. created abrt crash report - https://bugzilla.redhat.com/show_bug.cgi?id=605156 debug -15 doesn't work for me i said -debug 15, not debug -15 anyway, the original report contains no indication of using the fingerprint scanner plugin, so comment #3 is most likely unrelated. ok -15 was my typo in this comment, not in system (verified via ps ax) - kdm.log showed only X log, nothing more thanks for pointing to fingerprint PAM, after commenting it out, kdm works well (see my bugzilla report) too bad that you ignored about 80% of comment #2. but, oh, well, not my problem. I wonder if is not a intel-drv problem, which kill xserver ? Any non-intel here ? >> Any non-intel here ?
Yes,
The same on desktop with GF8800 GTX (proprietary driver).
Created attachment 48103 [details]
empty password - first time, no crash
Created attachment 48104 [details]
empty password - second time, crash
just for completeness' sake (-debug 15, daemon.*)
Created attachment 48655 [details] kdm with -debug 15, daemon.* wrong password - right password , crash kdm with -debug 15, daemon.* After this happen I could reproduce this behaviour , all the times , so you got 2 or 3 , crashes on attach. Also you have a completed backtrace on: https://bugzilla.redhat.com/show_bug.cgi?id=612176 (In reply to comment #12) this message: Jul 7 14:26:32 magix kdm[1747]: Cannot lock pid file /var/run/kdm/kdm.pid, another xdm is running (pid 1692) is just me trying start kdm from console, is not part of the bug. Looks like another pam-fprintd victim, and likely dup of bug #220404 If you're not using a fingerprint reader, see if yum remove fprintd-pam helps. And after: yum remove fprintd , My tests after this and couldn't reproduce the bug again, but just a few tests. looking at zejdl's log, it looks like PAM is crashing, so rex' suspicion might be correct. sergio's log is worthless; it doesn't contain any actual debugging information from kdm. i know that some distributions apply completely broken patches from suse, which also may explain the original submission, but i guess we'll never know, as the OP never posted a log. an actual bug in upstream kdm is somewhat unlikely, though. |