http://bugzilla.opensuse.org/show_bug.cgi?id=964812 Bug ID: 964812 Summary: Screen lock behavior appears random/disconnected from settings choice Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: HP OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team@suse.de Reporter: Pemberton.John.M@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Context: HP Pavilion Elite m9350f, AMD Phenom 64-bit quad core, 6 GB memory. Downloaded ISO via direct link, verified SHA256 sum, Burned DVD+R using K3B with *verify* option. No errors. After booting the DVD, choose update from DVD menu. Update seemingly proceeded without error. Problem Details: 1) AFAIK, in principle I have the screen lock disabled, but it still locks. That is, on the "System Settings - Screen Locker" panel, I have both "Start automatically after:" and "Require password after:", UNCHECKED. The "Apply" button was pressed, and just to try to be sure as possible that the change was implemented, the system was rebooted. So I'm expecting the screen locker should be disabled. 2) The screen locker's acceptance of the password seems to function randomly. That is, often it does not accept the password, but sometimes it DOES. Naturally when it FIRST didn't accept the password, I made a point of assuring that any modifier keys were off, and that I typed the password VERY slowly/carefully. I naturally also tested the keyboard to make sure that it was functioning correctly/reliably. I wouldn't even consider it an issue if I weren't very sure that the password had been typed correctly, SEVERAL times. I've also tried hitting ENTER after typing the password some times, but other times pressing with the mouse, the provided on screen button. As to whether or not the password is accepted, I was previously unaware of the kcheckpass chmod issue. Before entering this ticket, I searched for related tickets, but somehow didn't find them. Yet the automatic search triggered upon typing into the summary text input field, found the tickets. I have now done the chmod, so I'll have to see if it works more consistently. But unless there is a communication problem between the GUI environment and the command, I would expect it to work consistently, if it works at all. -- You are receiving this mail because: You are on the CC list for the bug.