Does the issue reproduce when when not using screen locking? I.e. when you go to System Settings > Workspace Behavior > Screen Locking and uncheck "After waking from sleep"?

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.

(In reply to Nate Graham from comment #1)
> Does the issue reproduce when when not using screen locking? I.e. when you
> go to System Settings > Workspace Behavior > Screen Locking and uncheck
> "After waking from sleep"?
Yes, the issue reproduce without Screen Locking. 
On resume I see only black screen. 
journalctl -b -1 ended:
апр 05 15:16:00 keleg-nvidia systemd[1]: grub-common.service: Deactivated successfully.
апр 05 15:16:00 keleg-nvidia systemd[1]: Finished Record successful boot for GRUB.
апр 05 15:16:00 keleg-nvidia systemd[1]: Starting GRUB failed boot detection...
апр 05 15:16:00 keleg-nvidia systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
апр 05 15:16:00 keleg-nvidia systemd[1]: Finished GRUB failed boot detection.
апр 05 15:16:01 keleg-nvidia systemd[1]: nvidia-suspend.service: Deactivated successfully.
апр 05 15:16:01 keleg-nvidia systemd[1]: Finished NVIDIA system suspend actions.
апр 05 15:16:01 keleg-nvidia systemd[1]: Starting System Suspend...
апр 05 15:16:01 keleg-nvidia systemd-sleep[1604]: Entering sleep state 'suspend'...
апр 05 15:16:01 keleg-nvidia kernel: PM: suspend entry (deep)

Sorry, I'm a bit confused. You said:

> If the checkbox "After waking from sleep" is unchecked, then the download proceeds normally,

and also

> Yes, the issue reproduce without Screen Locking. 
> On resume I see only black screen. 

Can you confirm whether the issue happens after resuming from suspend without screen locking?

(In reply to Nate Graham from comment #4)
> Sorry, I'm a bit confused. You said:
> 
> > If the checkbox "After waking from sleep" is unchecked, then the download proceeds normally,
> 

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

(In reply to Nate Graham from comment #4)
> and also
> 
> > Yes, the issue reproduce without Screen Locking. 
> > On resume I see only black screen. 
This was written by another user.

Oh my mistake, sorry.

Vladimir, your issue is caused by an NVIDIA driver issue or regression. 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!

---

Viktor, your issue is different if it goes away when you disable the lock screen. Can you submit a new bug report for it? Thanks

(In reply to Nate Graham from comment #7)
> Viktor, your issue is different if it goes away when you disable the lock
> screen. Can you submit a new bug report for it? Thanks
I will try.
Until I figure out how to do it right.

Created attachment 157904 [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.

(In reply to Victor Ryzhykh from comment #9)
> Created attachment 157904 [details]
> The text is long. I will attach the file, and below I will add the text in
> the browser.

I can't put such a long text in the browser. I get an error that there are too many lines.

In another bug report please, Victor.

(In reply to Nate Graham from comment #11)
> In another bug report please, Victor.

Ok.
https://bugs.kde.org/show_bug.cgi?id=468228