https://bugs.kde.org/show_bug.cgi?id=506536
Bug ID: 506536
Summary: Screen locker is broken and unlocking is not possible
anymore
Classification: Plasma
Product: kwin
Version First unspecified
Reported In:
Platform: KDE Linux
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: generic-crash
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Please remove this comment after reading and before submitting - thanks!
***
SUMMARY
Tried to wake up system from sleep. Received the error message "Screen locker
is broken and unlocking is not possible anymore..."
See the attached photo of screen for the full error message.
STEPS TO REPRODUCE
1. Update system to latest via "dnf update"
2. Reboot system if reboot is required
3. Let system go to sleep or lock screen via CMD-L
4. See error message
OBSERVED RESULT
Receive the error message shown in the attached photo of the screen.
EXPECTED RESULT
Screen should unlock normally.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.4-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 32 GiB of RAM (27.1 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
ADDITIONAL INFORMATION
This bug appeared immediately after I did a system update via "sudo dnf update"
I've attached a list of the packages altered in the "dnf update" command.
I have also done a "dnf history undo <transaction id>" to undo the update.
This did not help. My system still cannot restore from screen lock.
In other words, my system is all "messed" up....
I wonder if someone 'tried' to fix the problem reported by me in bug #505288,
which was closed as a duplicate of bug #500339.
I marked the severity as "grave" but, honestly, I feel it's "critical." Not
testing software before putting it in the mainline "stable" release is a
critical affliction....
--
You are receiving this mail because:
You are watching all bug changes.
