https://bugs.kde.org/show_bug.cgi?id=466326
--- Comment #7 from Brian Tipton ---
It (In reply to Nate Graham from comment #5)
> The gdb backtrace doesn't show that kwin_wayland crashed but rather than it
> was interrupted.
>
> Can you get a backtrace of the crash itself?
(In reply to Brian Tipt
https://bugs.kde.org/show_bug.cgi?id=466326
--- Comment #6 from Brian Tipton ---
(In reply to Nate Graham from comment #5)
> The gdb backtrace doesn't show that kwin_wayland crashed but rather than it
> was interrupted.
>
> Can you get a backtrace of the crash itself?
This gdb was during the "c
https://bugs.kde.org/show_bug.cgi?id=466326
--- Comment #5 from Nate Graham ---
The gdb backtrace doesn't show that kwin_wayland crashed but rather than it was
interrupted.
Can you get a backtrace of the crash itself?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466326
--- Comment #4 from Brian Tipton ---
Created attachment 156744
--> https://bugs.kde.org/attachment.cgi?id=156744&action=edit
Diagnosis Info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466326
--- Comment #3 from Brian Tipton ---
Created attachment 156743
--> https://bugs.kde.org/attachment.cgi?id=156743&action=edit
GDB
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466326
--- Comment #2 from Brian Tipton ---
(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_use
https://bugs.kde.org/show_bug.cgi?id=466326
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC|