Summary: | System crash when connecting monitors via a USB hub | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Miguel Guthridge <hdsq> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | nate |
Priority: | NOR | ||
Version: | 5.24.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Miguel Guthridge
2022-05-22 05:44:40 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Can you please attach one? Thanks! (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > Can you please attach one? Thanks! Sadly I can't figure out how to get a backtrace on my system since I don't get the error pop-up when the crash happens. It simply takes me straight back to the login screen. I did notices that it displays some error messages on the screen right before showing the login screen though, so I've uploaded a quick video of that. The error messages should be readable. https://youtu.be/8ZNDS-n4Aug If there is any info on how I can access the backtraces? Since all my running apps get killed, I imagine that GDB would be taken down with it, so the advice in the linked article desn't really help. You may be able to retrieve a backtrace using `coredumpctl`. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl This strikes me as likely to ultimately be caused by an issue in the graphics drivers or the kernel, though. (In reply to Nate Graham from comment #3) > You may be able to retrieve a backtrace using `coredumpctl`. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > > This strikes me as likely to ultimately be caused by an issue in the > graphics drivers or the kernel, though. It looks like basically everything crashed over the course of 3 seconds or so, due to a combination of SIGABRT and SIGSEGV errors. The first program to crash is Xorg, then 5 instances of drkonqi, a bunch of other random apps, and then near the end kwin_x11. All of them have an accessible corefile except for Xorg (which is marked as inaccessible). Should I try installing a few more debug symbols to try to get more info on Xorg in particular, since it appears to be the first program to crash (although if it's a kernel issue, I'm not sure if it would appear in this list?). Yes please. If Xorg itself is crashing though, it's very likely an Xorg issue or a kernel issue, not a KDE issue. 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! |