Bug 506536 - Screen locker is broken and unlocking is not possible anymore
Summary: Screen locker is broken and unlocking is not possible anymore
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: unspecified
Platform: KDE Linux Linux
: NOR grave
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-03 15:25 UTC by Vartan
Modified: 2025-07-03 15:28 UTC (History)
1 user (show)

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


Attachments
dnf update transaction information (41.89 KB, text/plain)
2025-07-03 15:27 UTC, Vartan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vartan 2025-07-03 15:25:59 UTC
***
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....
Comment 1 Vartan 2025-07-03 15:27:28 UTC
Created attachment 182900 [details]
dnf update transaction information
Comment 2 Zamundaaa 2025-07-03 15:28:57 UTC
This is a Fedora issue, see https://pagure.io/fedora-kde/SIG/issue/639