https://bugs.kde.org/show_bug.cgi?id=483008
--- Comment #8 from agap...@hotmail.com <agap...@hotmail.com> --- (In reply to Méven Car from comment #7) > (In reply to agap...@hotmail.com from comment #6) > > Created attachment 166956 [details] > > gdb.txt with backtrace > > > > I have managed to get a backtrace to show up in the .txt. Let me know if > > anyhting else is needed. > > This is nice and even more detailed that what I would expect normally ;) > > But I am not sure what this trace is for. If you use gdb, it should mention > a segfault or a crash somewhere but this does not seem to be the case. > > With gdb, you need to launch or attach to kwin process, and get it to crash, > then we will have a useful trace in gdb output. > > Or with coredumpctl after kwin has quit after a crash, you can run > `coredumpctl info -1 kwin_wayland` to get essentially the same thing. I can't consistently reproduce the crash so I can't use gdb. It finally crashed again so using the coredump command I have attached the output -- You are receiving this mail because: You are watching all bug changes.
