Bug 468228

Summary:	Black screen after exiting screen lock on nvidia proprietary drivers
Product:	[Unmaintained] kscreenlocker	Reporter:	Victor Ryzhykh <victorr2007>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	nate
Priority:	NOR	Keywords:	regression
Version First Reported In:	5.27.4
Target Milestone:	---
Platform:	ROSA RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	log

Description Victor Ryzhykh 2023-04-07 04:59:56 UTC

1. It booted up and then went into standby mode.
2. Came out and got a black screen.


Operating System: ROSA Fresh Desktop 2021.1
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.5
Kernel Version: 6.1.22-generic-3rosa2021.1-x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz
Memory: 15.6 ГиБ of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B250M-D3H

Same problem. If the checkbox "After waking from sleep" is unchecked, then the download proceeds normally,
if the checkbox "After waking from sleep" is checked, then after entering the password, instead of opening the session, an empty black window appears.

The problem appeared after version 5.25.90. I collected updates from git for version 5.25.90 almost before the release.
Ten days before the release of 5.26.0, on package built from snapshots from git, or from sources taken from
https://origin.archive.neon.kde.org/unstable/pool/main/, there was no error.
The system started from standby on nvidia drivers without problems.
And after the release of 5.26.0, this problem appeared.
To check, I rearranged versions 5.25.90 and 5.26.0 several times.
On the first one there were no problems, on the second one appeared.

Comment 1 Victor Ryzhykh 2023-04-07 05:01:50 UTC

Created attachment 157915 [details]
log

Booted up and went into standby mode.
Came out and got a black screen.
Rebooted and ran command « journalctl -b -01 > log.txt».
Filtered the output since the transition to standby mode.
The text is long. I will attach the file, and below I will add the text in the browser.

Comment 2 Victor Ryzhykh 2023-04-07 05:04:32 UTC

(In reply to Victor Ryzhykh from comment #1)
> Created attachment 157915 [details]
> log
> 
I can't put such a long text in the browser. I get an error that there are too many lines.
So I attached the log file.

Comment 3 Victor Ryzhykh 2023-04-07 05:06:54 UTC

I have no problem without a screen lock. After turning on the lock, this problem appears.

Comment 4 Nate Graham 2023-04-10 17:19:16 UTC

> апр 06 19:31:05 aquarius plasmashell[2907]: The X11 connection broke (error 1). Did the X11 server die?

Something that the NVIDIA driver is doing is causing the X server to crash. This is definitely a bug in the NVIDIA driver itself as no KDE code is involved in intermediating the NVIDIA driver's connection with the X server. Please report this issue to the NVIDIA folks, either by sending an email to linux-bugs@nvidia.com or making a post at https://forums.developer.nvidia.com/c/gpu-graphics/linux. It would be helpful to the NVIDIA developers if you could run nvidia-bug-report.sh and attach the resulting file in your report. Thanks!

Comment 5 Victor Ryzhykh 2023-04-13 18:08:39 UTC

Thank you. Indeed, the problem was not in the plasma. The qt5-qtvirtualkeyboard package had a very old patch with no description. This patch is already three years old. I don't even remember why. I removed it from the package, and after rebuilding the qt5-qtvirtualkeyboard package, it became normal to exit the screen lock.