Bug 486279 - Crash after resume with a "in order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2)" message
Summary: Crash after resume with a "in order to unlock switch to a virtual terminal (e...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (show other bugs)
Version: 6.0.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-29 06:43 UTC by johann.jacobsohn
Modified: 2025-02-13 03:46 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description johann.jacobsohn 2024-04-29 06:43:25 UTC 
SUMMARY

Unlocking a 11gen Framework Laptop (integrated intel gpu) while connected to an external USB-C-Monitor regularly crashed kscreenlocker, showing the "in order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2)" message. This has happened during Plasma 5 and is still happening with Plasma 6.

STEPS TO REPRODUCE
1. Connect laptop to external display
2. Close laptop lid
3. Remove external display
4. Wake laptop

OBSERVED RESULT

kscreenlocker shows the above mentioned message

EXPECTED RESULT

Laptop should always be able to resume

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION

Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: Framework
Product Name: Laptop
System Version: AA
Comment 1 johann.jacobsohn 2024-04-29 06:50:33 UTC 
I am using "Standby, then hibernate" for sleep
Comment 2 bugs.kde.org 2024-06-24 21:32:53 UTC 
Looks like duplicate of https://bugs.kde.org/show_bug.cgi?id=485084; however I'm also seeing this on Fedora 40, KDE 6.1 and AMD
Comment 3 johann.jacobsohn 2024-06-26 12:28:42 UTC 
I switched to Hybrid sleep and the problem has decreased considerably, I only encounter this problem every few days now
Comment 4 TraceyC 2025-01-14 01:25:04 UTC 
Can anyone affected by this bug see if it's still happening on 6.2.5? If so, please set the status of this report to CONFIRMED. The fix should have been in 6.1.1. Thanks!
Comment 5 Bug Janitor Service 2025-01-29 03:47:08 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2025-02-13 03:46:42 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.