Bug 744661

Summary: Confirmation of notifier "Password will expire in XX days" only possible with mouse
Product: [openSUSE] openSUSE 12.1 Reporter: Olaf Knobloch <o.knobloch>
Component: KDE4 WorkspaceAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P5 - None CC: o.knobloch, robby.engelmann, suse-beta, wbauer
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 12.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Olaf Knobloch 2012-02-01 21:37:26 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.77 Safari/535.7

Hi All !

This is just a small issue. In case passwords are limited with yast2 to a certain time, lets say a month, a notifier appears when trying to log in, saying that a new password needs to be set in XX days (starting from 7 to 0). This notifier cannot be closed with the Return key, you need to take the mouse to confirm. This is a bit bad, when no mouse device is given.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.


Expected Results:  
Mouse and keyboard (Return key) should be usable to confirm the notifier.
Comment 1 Christian Boltz 2012-02-07 23:09:36 UTC 
Where does this notifier appear? In the login manager? Which one - KDM, GDM, ...?
Comment 2 Olaf Knobloch 2012-03-08 08:56:12 UTC 
Hi, 

sorry for the late reply.

It appears on the first login page provided by Opensuse. I then login to KDE. So I guess it is the KDM.


regards
Comment 3 Robby Engelmann 2015-11-06 06:56:22 UTC 
hmm, kdm is not actively developed anymore. I guess I can close this bug
Comment 4 Wolfgang Bauer 2015-11-06 18:30:31 UTC 
ACtually this sounds to me like a duplicate of Bug#772344.
It was a general input focus problem in kdm, and should be fixed since nearly a year (in 12.3 and up).

I just tried it here in 13.2, and pressing the Return key to dismiss the warning *did* work.

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