Mailinglist Archive: opensuse-bugs (6633 mails)

< Previous Next >
[Bug 533189] New: fingerprint reader messes up login and kills possibility of unlocking locked session
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 21 Aug 2009 02:54:51 -0600
  • Message-id: <bug-533189-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=533189

User onelife.onemission@xxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=533189#c1

Summary: fingerprint reader messes up login and kills
possibility of unlocking locked session
Classification: openSUSE
Product: openSUSE 11.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.1
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Security
AssignedTo: security-team@xxxxxxx
ReportedBy: onelife.onemission@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---


User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; de;
rv:1.9.0.10) Gecko/2009042315 Firefox/3.0.10

Good morning folks.
Topic of the day: Solving a mysterious bug. Several people have been asking how
to fix the issue and it certainly is annoying.

Bug: When enabling „Use Fingerprint Reader“ in OpenSuse as login method, a
popup warns with the message: `This Design cannot be used with Authentication
method "Generic".´ Afterwards the login screen gets totaly misplaced. The User
has to provide his name manually. When wanting to UNLOCK a locked screen, a
warning pops up with `SESSION LOCKED - UNLOCKING SESSION FAILED.´ while buttons
of the popup are disabled.

DELETING THE .kde and/or .kde4 folder DOES NOT (!) WORK.

Note that several threads exist regarding this matter:

- http://forums.opensuse.org/applications/408887-cant-stop-screen-locking.html?
-
http://forums.opensuse.org/applications/408788-session-keeps-locking-screen-brightness.html?
- http://forums.opensuse.org/applications/418608-unlock-session.html?
- http://forums.opensuse.org/hardware/420208-issues-fingerprint-reader.html
-
http://forums.opensuse.org/applications/408588-unlocking-screen-unlocking-failed-3.html
- ... (I´ve seen more, but won´t state all links here)

And hey, if the fingerprint reader cannot be used as login method...why does it
even exist? ;)
Conclusion: Important matter to be solved.

Reproducible: Always

Steps to Reproduce:
1. Open YaST and enable "use fingerprint reader" in the hardware tab
2. Configure login method fingerprint in the security settings
3. Reboot. You will notice the warning popup, the cracked login screen and and
if you´ve once locked a session (either manually or via screensaver) you will
not be able to unlock it the normal way
Actual Results:
* Warning popup before login screen: `This Design cannot be used with
Authentication method "Generic".´
* Scrambled login screen with having to provide user name manually
* Unlocking the screen after manual or automated lock is not possible. Warning
message pops up: `SESSION LOCKED - UNLOCKING SESSION FAILED.´
* Side issue #1: Changing login themes via session management is not possible
* Side issue #2: Login after suspending session FAILS from time to time.

Expected Results:




There exist two uncool solutions:

Choice 1: Disable the fingerprint reader to be used as login method in YaST.
Choice 2: Press ALT+CTRL+F1 to arrive at bash. Provide superuser credentials
and kill kdesktoplock; get back to your session via ALT+CTRL+F7.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >