Bug 500810 - get randomly black screen
Summary: get randomly black screen
Status: NEEDSINFO WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: Containment (show other bugs)
Version: 6.3.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-27 12:31 UTC by Cherkah
Modified: 2025-03-15 03:47 UTC (History)
3 users (show)

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


Attachments
plasmashell-log (12.05 KB, text/plain)
2025-02-27 12:31 UTC, Cherkah
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cherkah 2025-02-27 12:31:01 UTC
Created attachment 178941 [details]
plasmashell-log

***

SUMMARY
I consider this problem as a plasmashell crash even if I do not have a Core_dump captured by systemd/kcrash.

on my setup composed of 1 laptop + 2 screens (the laptop one + external) I have been experiencing random desktop graphical shutdowns for 1 week (5 in total).
my two screens suddenly become black with no mouse cursor. applications can only be launched via the terminal (yakuake/konsole).

I recover desktop graphical usage via the cmd:
`` systemctl restart --user plasma-plasmashell.service &``

when a program crashes, drkonqi launches automatically with generation of core.plasmashell.XX.XX.XXX.zst . but here this is not the case.

I provided a systemctl log file that will probably help characterize this problem.
some logs before the incident and after

STEPS TO REPRODUCE
1. dont know. This can happen with 1 or more applications open.


OBSERVED RESULT
black screen

EXPECTED RESULT
  

SOFTWARE/OS VERSIONS
 Operating System: EndeavourOS 
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Comment 1 Cherkah 2025-02-27 13:27:37 UTC
now i've updated my system from KDE Plasma Version: 6.3.1 to -> 6.3.2, I remain on the lookout for possible feedback.
expecting it went away with this new update..
regards
Comment 2 Cherkah 2025-02-27 14:08:23 UTC
the problem just happened again with logs:
```
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: No QSGTexture provided from updateSampledImage(). This is wrong.
fév 27 14:59:33 Mercury kwin_wayland[2713]: kwin_scene_opengl: Could not delete texture because no context is current
```
still no crash_log to provide and still same command line to find the desktop. even after updating plasma to 6.3.2
Comment 3 TraceyC 2025-02-28 21:41:22 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!
Comment 4 Nate Graham 2025-02-28 22:15:21 UTC
It sounds like this isn't actually a crash, but rather a case where plasmashell either exited, or kept running but misplaced the containments (hence them turning black).

Does it ever happen when you only have the laptop, with no external screen connected?
Comment 5 Cherkah 2025-02-28 22:25:29 UTC
@TraceyC as i said there is no backtrace about this bug that why i've provided the logs..

@ Nate Graham the crash is not a systematical one (it can be for any reasons). sinc my last post i got. 
Since my last post I haven't had one yet, external screen connected or not
Comment 6 Bug Janitor Service 2025-03-15 03:47:34 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!