| Summary: | Crash UI after screen goes black | ||
|---|---|---|---|
| Product: | [I don't know] kde | Reporter: | Ali <fakhamati> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nicolas.fella |
| Priority: | NOR | Keywords: | qt6 |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Ali
2024-03-12 04:59:13 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! (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 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! 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! |