Bug 240796 - only one attemp to login by KDM
Summary: only one attemp to login by KDM
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-05 11:36 UTC by Sergei LITVINENKO
Modified: 2010-10-24 18:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
empty password - first time, no crash (5.38 KB, text/plain)
2010-06-18 09:17 UTC, zejdl
Details
empty password - second time, crash (4.28 KB, text/plain)
2010-06-18 09:19 UTC, zejdl
Details
kdm with -debug 15, daemon.* (6.01 KB, text/plain)
2010-07-07 15:55 UTC, Sérgio Basto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sergei LITVINENKO 2010-06-05 11:36:43 UTC
Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

if password is wrong, kdm propose to login again. But after it right password is typed, kdm close graphics window and show text screen. So, in general, we have only one attempt to login by KDM.




Reproducible: Always

Steps to Reproduce:
Choice runlevel '5' and KDM as manager, reboot.
Put right login and right password - OK. Exit KDE and login again.

Username field is OK - do not touch it, put worng password and press enter. Receice message about password wrong and new prompt to login. 

Put right password and press enter.


Actual Results:  
KDM hide graphics screen and show text console... No way to continue...

Expected Results:  
KDM accept password and run GUI.

For newbie only one way - reboot system.
For advanced user it is necessary to switch to different console, login as root and kill kdm process or `killall kdm`. It cause KDM restarting.

This bug is affected to kdm in fedora-12 too.
Comment 1 Sérgio Basto 2010-06-05 13:40:31 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 .
Comment 2 Oswald Buddenhagen 2010-06-05 15:26:37 UTC
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.
Comment 3 zejdl 2010-06-17 12:56:09 UTC
created abrt crash report - https://bugzilla.redhat.com/show_bug.cgi?id=605156

debug -15 doesn't work for me
Comment 4 Oswald Buddenhagen 2010-06-17 13:37:23 UTC
i said -debug 15, not debug -15
Comment 5 Oswald Buddenhagen 2010-06-17 13:39:36 UTC
anyway, the original report contains no indication of using the fingerprint scanner plugin, so comment #3 is most likely unrelated.
Comment 6 zejdl 2010-06-17 14:28:30 UTC
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)
Comment 7 Oswald Buddenhagen 2010-06-17 15:06:16 UTC
too bad that you ignored about 80% of comment #2. but, oh, well, not my problem.
Comment 8 Sérgio Basto 2010-06-17 19:15:59 UTC
I wonder if is not a intel-drv problem, which kill xserver ? 
Any non-intel here ?
Comment 9 Sergei LITVINENKO 2010-06-17 19:44:40 UTC
>> Any non-intel here ?

Yes,
The same on desktop with GF8800 GTX (proprietary driver).
Comment 10 zejdl 2010-06-18 09:17:43 UTC
Created attachment 48103 [details]
empty password - first time, no crash
Comment 11 zejdl 2010-06-18 09:19:15 UTC
Created attachment 48104 [details]
empty password - second time, crash

just for completeness' sake (-debug 15, daemon.*)
Comment 12 Sérgio Basto 2010-07-07 15:55:47 UTC
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
Comment 13 Sérgio Basto 2010-07-07 15:59:44 UTC
(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.
Comment 14 Rex Dieter 2010-07-07 16:41:19 UTC
Looks like another pam-fprintd victim, and likely dup of bug #220404
Comment 15 Sérgio Basto 2010-07-07 17:07:09 UTC
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.
Comment 16 Oswald Buddenhagen 2010-10-24 18:35:26 UTC
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.