Bug 483371 - X11 [AMD]: After locking, the screen goes black
Summary: X11 [AMD]: After locking, the screen goes black
Status: RESOLVED DUPLICATE of bug 483163
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 6.0.2
Platform: Manjaro Linux
: NOR grave
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-12 20:14 UTC by kde
Modified: 2024-03-21 16:47 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Part of the journal (journalctl -m) when locking the screen (867 bytes, text/plain)
2024-03-12 20:14 UTC, kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2024-03-12 20:14:59 UTC
Created attachment 167058 [details]
Part of the journal (journalctl -m) when locking the screen

SUMMARY
When I lock my system, the screen goes black until I blindly type the password, or unlock it via loginctl.

STEPS TO REPRODUCE
1. Lock the system (Meta + L)
2. Observe
3. Press any button
4. Observe

OBSERVED RESULT
After locking, the screen goes black. After pressing any button, the cursor appears.
I can exit this black screen by either:
1) blindly typing the password and hitting enter, or
2) unlock the session using loginctl

See this video for a demonstration (I cannot upload it here, as it's too large):  https://www.youtube.com/watch?v=_lVF2S9akZw

EXPECTED RESULT
The lock screen is shown

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.7.9-zen1-1-zen (64-bit)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
I believe this is not a duplicate of https://bugs.kde.org/show_bug.cgi?id=481308 as the black screen only appears after locking and does not disappear after some time.

Nothing relevant appears in the journal when I lock the screen, but I attached the part anyway
Comment 1 kde 2024-03-13 15:15:04 UTC
I did not find a way to edit my last comment, so I just want to add that I can also reproduce this on Plasma 6.0.2
Comment 2 Philip Müller 2024-03-19 02:14:30 UTC
I can confirm the issue as I see it on the OrangePi Neo I'm developing on. As soon as we put the device to sleep and wait a little, most of the time we see a black screen with mouse cursor. On a gaming handheld there are no buttons to interact with the lockscreen. When I attach a keyboard to the device and press Enter it shows the plasma desktop. If the user has a password, that needs to be entered first. How can we help to debug, as this is a blocker issue for our product.
Comment 3 Philip Müller 2024-03-19 02:24:00 UTC
Hmm, after changing to our own theme breath that is didn't happen. Might be related to https://bugs.kde.org/show_bug.cgi?id=483163
Comment 4 kde 2024-03-20 08:19:34 UTC
(In reply to Philip Müller from comment #3)
> Hmm, after changing to our own theme breath that is didn't happen. Might be
> related to https://bugs.kde.org/show_bug.cgi?id=483163

I can also confirm that changing to the Oxygen theme (from Breeze) solves the issue. Unfortunately it isn't really a solution.
Perhaps it is related to Breeze then?
Comment 5 duha.bugs 2024-03-21 16:44:07 UTC
> I can also confirm that changing to the Oxygen theme (from Breeze) solves the issue. Unfortunately it isn't really a solution.
Perhaps it is related to Breeze then?

This is probably: https://bugs.kde.org/show_bug.cgi?id=483163

Change your Plasma Style (not global theme) to either Breeze Dark or Breeze Light. That should fix the issue.
Comment 6 kde 2024-03-21 16:47:10 UTC
(In reply to duha.bugs from comment #5)
> > I can also confirm that changing to the Oxygen theme (from Breeze) solves the issue. Unfortunately it isn't really a solution.
> Perhaps it is related to Breeze then?
> 
> This is probably: https://bugs.kde.org/show_bug.cgi?id=483163
> 
> Change your Plasma Style (not global theme) to either Breeze Dark or Breeze
> Light. That should fix the issue.

Thanks for the suggestion! I can confirm that this indeed did solve my issue.
I wish you a nice rest of the day.

*** This bug has been marked as a duplicate of bug 483163 ***