Bug 486970

Summary:	Screen blanked, kwin crashed
Product:	[Plasma] kwin	Reporter:	d7ghrrkcz
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kde
Priority:	NOR
Version First Reported In:	5.27.5
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	gdb backtrace gdb backtrace gdb backtrace dmesg

Description d7ghrrkcz 2024-05-13 15:49:35 UTC

Today, I left the computer unattended, screens went to sleep. When I came back, both screens were lit up but with black screen only, and mouse cursor was able to move around interacting with objects. But I could not see anything else.  I had to kill X session and log in again. This has repeated later again, so I restarted by computer. It had never happened before.

sudo coredumpctl list --no-pager
Mon 2024-05-13 16:06:44 BST 3171626 1000 1000 SIGABRT present  /usr/lib/x86_64-linux-gnu/libexec/drkonqi                                                     611.8K
Mon 2024-05-13 16:06:44 BST 3171622 1000 1000 SIGABRT present  /usr/bin/kwin_x11                                                                             961.8K
Mon 2024-05-13 16:06:47 BST    6314 1000 1000 SIGSEGV present  /usr/bin/kwin_x11                                                                              13.9M

Three entries here, all will be attached in next message.

ADDITIONAL INFORMATION
Operating System: Debian GNU/Linux 12 (clean and updated stable, with no weird packages or settings)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.0-21-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6800 XT
Product Name: X570 Steel Legend

Comment 1 d7ghrrkcz 2024-05-13 15:50:01 UTC

Created attachment 169442 [details]
gdb backtrace

Comment 2 d7ghrrkcz 2024-05-13 15:50:11 UTC

Created attachment 169443 [details]
gdb backtrace

Comment 3 d7ghrrkcz 2024-05-13 15:50:20 UTC

Created attachment 169444 [details]
gdb backtrace

Comment 4 d7ghrrkcz 2024-05-13 15:53:52 UTC

Created attachment 169446 [details]
dmesg

Comment 5 d7ghrrkcz 2024-05-13 16:00:20 UTC

Furthermore, drkonqi has failed to submit this report. I filled information in, clicked submit in the end, it was consuming one CPU core at 100% for several minutes, and did not send the report. I killed it and filled this report here manually.
If you want me to fill a bug against drkonqi, I will be happy to, please let me know. gbd backtrace reports from drkonqi attached.

Comment 6 David Edmundson 2024-05-14 21:00:13 UTC

>                #3  0x00007f1bbb290c79 qt_message_fatal (libQt5Core.so.5 + 0x90c79)

This means we can't connect to the X server. That's an issue below KDE

Comment 7 d7ghrrkcz 2024-05-14 22:01:56 UTC

(In reply to David Edmundson from comment #6)
> >                #3  0x00007f1bbb290c79 qt_message_fatal (libQt5Core.so.5 + 0x90c79)
> 
> This means we can't connect to the X server. That's an issue below KDE

Thanks. Where should I report it? Against Xorg? Linux kernel?
Why kwin crashed?
What about drkonqi crashes?

Appreciate your assistance.