| Summary: | Lock screen sometimes does not respond to Unlock button | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreensaver | Reporter: | Michał Zając <michal.zajac+kde.org> |
| Component: | locker-qml | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | kde, mauromol, mgraesslin, oliver.henshaw |
| Priority: | NOR | ||
| Version: | 4.10.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
My .xsession-errors file
New xsession-errors |
||
|
Description
Michał Zając
2013-03-25 22:47:57 UTC
Created attachment 78389 [details]
My .xsession-errors file
I have enabled everything from kdebugdialog before creating this file.
(In reply to comment #1) > Created attachment 78389 [details] > My .xsession-errors file > > I have enabled everything from kdebugdialog before creating this file. Can you make sure "ksmserver" and "kscreenlocker_greet" are enabled in kdebugdialog, and login again? It's a strange quirk that sometimes you have to try twice to enable some debug areas. Then "tail -f ~/.xsession-errors" just before you lock should be enough. You're using the simple locker, correct? Or are you using the screensaver type? Does it still happen if you use the desktop widgets locker? Created attachment 78400 [details]
New xsession-errors
Removed the file itself so there is nothing old laying around. Logged in, locked screen, the bug did not trigger.
I think I also see this. Entering the password and pressing enter doesn't unlock, but if I click with the mouse on "unlock" it works fine. The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more. I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component. I understand you don't want to work on this, but... can anybody help to fix or workaround this? I'm affected by this problem (in the unlock screen, I can type my password, but ENTER does nothing, neither does clicking on the OK button with the mouse). I think this has started to happen after the latest X update on my Linux Mint 17.3 (based on Ubuntu 14.04). Previously it was working just fine. By "OK button" I meant the "Unlock button" indeed. I can't even switch user. Also, if I replace mdm with kdm, it seems like I can't even login into KDE, ENTER does nothing there, too... I don't even see any button to click (instead of pressing ENTER)... @Mauro: this is not a support forum. If you need user support please ask at your distribution support forums or at forum.kde.org. Hi Martin, I know, thanks, I dared to write anyway because my problem seems like to be exactly this and in comment #3 Michał seems to suggest he fixed/worked around this problem, but I didn't understand how it did. Also, I'm quite sceptical I will get proper feedback on the forums. Anyway, I won't spam any more here. Thank you. Just in case someone gets here, in my case the problem was caused by a recent update of fingerprint-gui (or of some other package that broke it). See http://askubuntu.com/questions/795890/kubuntu-14-04-kde-login-impossible-after-update/796146 oh my, that sounds horrible :-( Thanks for the update on what was the problem. Changing the solution to DOWNSTREAM to indicate that it was a "distro problem". |