https://bugs.kde.org/show_bug.cgi?id=466326
--- Comment #7 from Brian Tipton <brian.p.tip...@gmail.com> --- 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 Tipton from comment #6) > (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 "crash", I didn't realize it wasn't actually > crashing the kwin process. (In reply to Brian Tipton from comment #6) > (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 "crash", I didn't realize it wasn't actually > crashing the kwin process. What I see on my side during the "crash" is that the cursor doesn't have the ability to move, the keyboard doesn't do anything except sometimes lets me get to a TTY. And windows seems to be stuck at there last position. Most of the time it requires a reboot to get out of this state -- You are receiving this mail because: You are watching all bug changes.
