Bug 483312 - Crash UI after screen goes black
Summary: Crash UI after screen goes black
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-03-12 04:59 UTC by Ali
Modified: 2024-04-12 03:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ali 2024-03-12 04:59:13 UTC
SUMMARY
***
Inside x11, when one of the 2 monitors is turned off or the screen is locked and the screen turns black, after turning on one of the monitors, it turns off and blinks, and after a few seconds, the entire user interface crashes.
How can I collect and send logs?
I have this problem only in x11, and it was in version 5 as well.
***


STEPS TO REPRODUCE
1. Physically turning off one of the 2 monitors
2. Turn on that monitor
3. Both or one of 2 monitor start blinking and
4. UI and shell crash

STEPS TO REPRODUCE
1. Lock the screen
2. After few second screens goes black
3. After move mouse to turn on and unlock UI and shell crash

SOFTWARE/OS VERSIONS
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-25-generic (64-bit)
Graphics Platform: X11
Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics
Graphics Processor: AMD Radeon Graphics
Comment 1 Nicolas Fella 2024-03-12 18:40:25 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 2 Ali 2024-03-13 08:06:57 UTC
(In reply to Nicolas Fella from comment #1)
> 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!

It doesn't exactly crash.
The screen flashes and then goes completely black, and only the mouse cursor remains, and I have to reboot.
I typed this command and it had this output. How do I get the log exactly?

$ coredumpctl --reverse
TIME                           PID  UID  GID SIG     COREFILE     EXE                                                     SIZE
Wed 2024-03-13 11:31:31 +0330 1847    0    0 SIGSEGV inaccessible /snap/cups/1024/sbin/cups-proxyd                         n/a
Wed 2024-03-13 11:29:06 +0330 1840    0    0 SIGSEGV inaccessible /snap/cups/1024/sbin/cups-proxyd                         n/a
Wed 2024-03-13 11:21:45 +0330 7921 1000 1000 SIGABRT present      /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil  967.9K
Wed 2024-03-13 11:21:44 +0330 7766 1000 1000 SIGABRT present      /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil  967.1K
Wed 2024-03-13 11:21:44 +0330 7639 1000 1000 SIGABRT present      /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil  968.7K
Wed 2024-03-13 11:21:43 +0330 7504 1000 1000 SIGABRT present      /usr/bin/plasmashell                                 1016.0K
Wed 2024-03-13 11:21:43 +0330 7506 1000 1000 SIGABRT present      /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil  967.0K
Wed 2024-03-13 11:21:43 +0330 7439 1000 1000 SIGABRT present      /usr/bin/plasmashell                                 1016.4K
Wed 2024-03-13 11:21:43 +0330 7443 1000 1000 SIGABRT present      /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil  967.2K
Wed 2024-03-13 11:21:08 +0330 1843    0    0 SIGSEGV inaccessible /snap/cups/1024/sbin/cups-proxyd                         n/a
Comment 3 Bug Janitor Service 2024-03-28 03:46:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2024-04-12 03:48:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!