Bug 2224365 - Thinkpad T495: kscreenlock stays black after a while, needs force shutdown
Summary: Thinkpad T495: kscreenlock stays black after a while, needs force shutdown
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kscreenlocker
Version: 38
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL: https://bugs.kde.org/show_bug.cgi?id=...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-20 14:39 UTC by Henning
Modified: 2024-05-28 13:33 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:33:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Henning 2023-07-20 14:39:59 UTC 
The screen stays black and doesnt react to inputs

Reproducible: Sometimes

Steps to Reproduce:
1.lock screen
2. wait 30min or so
3. try to input password when its black
Actual Results:  
no input works. This seems to be a core architecture problem, maybe AMD


--- Software ---
OS: Fedora Linux 38.20230718.0 (Kinoite)
KDE Plasma: 5.27.6
KDE Frameworks: 5.107.0
Qt: 5.15.10
Kernel: 6.3.12-200.fc38.x86_64
Compositor: wayland

--- Hardware ---
Thinkpad T495

CPU: AMD Ryzen 5 PRO 3500U w/ Radeon Vega Mobile Gfx
RAM: 13.5 GB
GPU: AMD Radeon Vega 8 Graphics
Video memory: 2048MB
Comment 1 Aoife Moloney 2024-05-28 13:33:38 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.