Bug 585799 - kdm back screen into text mode if password fail (graphics login is locked)
kdm back screen into text mode if password fail (graphics login is locked)
Status: CLOSED DUPLICATE of bug 605156
Product: Fedora
Classification: Fedora
Component: kdebase-workspace (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-26 01:18 EDT by Sergei LITVINENKO
Modified: 2010-11-03 11:22 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-03 11:22:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sergei LITVINENKO 2010-04-26 01:18:37 EDT
Description of problem:
if password wrong, kdm close graphics window and show text screen.

Version-Release number of selected component (if applicable):
[sergeil@eee901 ~]$ rpm -qf `which kdm`

How reproducible:

Steps to Reproduce:
1.login with wrong password
Actual results:
kdm close graphics screen and show text console

Expected results:
kdm restart and propose to try again

Additional info:
`killall kdm` solve problem
kdm in f12 is affected too.
Comment 1 Steven M. Parrish 2010-06-04 21:11:41 EDT
This is a issue which needs to be reported upstream.  Please file a report at

Please add upstream report info to this report.  We will monitor the upstream
report for a resolution.

Thanks for the report

Fedora Bugzappers volunteer triage team
Comment 2 Sergei LITVINENKO 2010-06-05 05:38:56 EDT
>> This is a issue which needs to be reported upstream. 

Comment 3 John Griffiths 2010-11-03 11:14:24 EDT
The upstream https://bugs.kde.org/show_bug.cgi?id=240796 is reporting:

Status:  	RESOLVED
Resolution: 	DOWNSTREAM

Pointing to fprintd-pam as the culprit.

I did a yum remove fprintd which also removed fprintd-pam and gdm-plugin-fingerprint since I do not use a fingerprint reader.

This solved the problem.

Now whether this is a problem in fprintd-pam or the othe fprintd related packages or kdm not playing well with those packages is an issue to be determined and solved by the respective developers.

As a user I appreciate the effort by all the developers, but I think that I can reflect the sentiments of most of the users in saying I don't care about finger pointing, just solutions.
Comment 4 Kevin Kofler 2010-11-03 11:22:55 EDT

*** This bug has been marked as a duplicate of bug 605156 ***

Note You need to log in before you can comment on or make changes to this bug.