Bug 490532 - "Unlock failed" issue, and Sleep button not working
Summary: "Unlock failed" issue, and Sleep button not working
Status: RESOLVED NOT A BUG
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 6.1.3
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-20 01:07 UTC by qsabipb02
Modified: 2024-09-16 14:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description qsabipb02 2024-07-20 01:07:50 UTC
INFORMATION:
The screen locker shows the "Unlock failed" error message if I click on the Sleep or the Hibernate button, i.e., when I wasn't trying to unlock the screen, so the password field is clear. It does not happen when I click Switch User. Kscreenlocker is trying to unlock it without needing to.
Hibernate and Switch User work, but Sleep no longer does. I can still suspend to RAM from Plasma, from the Application Launcher for instance, or with systemctl suspend. When I click Sleep, it shows the usual, nonsensical "Unlock failed" message, interface components get greyed out, and then nothing happens. The system does not suspend. I inspected the journal, but found nothing of interest there, only a pam auth message saying that authentication failed (of course, since no password was supplied and I was just trying to suspend the PC).

EXPECTATIONS:
- No unlock attempt or fail message when I'm not trying to unlock the screen;
- Ability to suspend to RAM from the screen locker (very convenient, no need to switch user).

VERSIONS:
Linux: 6.9.10-zen1
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Comment 1 qsabipb02 2024-09-16 14:56:35 UTC
Greetings! I would like to inform that this was not a bug; it was simply a misconfiguration. When my system migrated to Plasma 6, the old configurations of the power management profile and of powerdevil remained in ~/.config. They were causing such problems. So I deleted their rc files and now suspending from the lock screen and auto-suspending after 10 minutes work again. I apologise for posting this erroneous bug report and for not having paid more attention and effort to the issue earlier. I would like to request the deletion of this report, if that be possible and necessary.