https://bugs.kde.org/show_bug.cgi?id=437783
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Status|REPORTED |NEEDSINFO
Resolution|--- |BACKTRACE
--- Comment #13 from Nate Graham <n...@kde.org> ---
Crashing thread:
Thread 1 (LWP 1671 "kwin_wayland"):
#0 0x00007efeda7b432e in __ppoll (fds=fds@entry=0x55eefae90c98,
nfds=nfds@entry=9, timeout=<optimised out>, timeout@entry=0x7ffccec62bb0,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:48
#1 0x00007efedaf9e3e0 in ppoll (__ss=<optimised out>, __timeout=<optimised
out>, __nfds=<optimised out>, __fds=<optimised out>) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:79
#2 qt_ppoll (timeout_ts=0x7ffccec62bb0, nfds=9, fds=0x55eefae90c98) at
kernel/qcore_unix.cpp:132
#3 qt_ppoll (timeout_ts=0x7ffccec62bb0, nfds=9, fds=0x55eefae90c98) at
kernel/qcore_unix.cpp:129
#4 qt_safe_poll (fds=0x55eefae90c98, nfds=9,
timeout_ts=timeout_ts@entry=0x7ffccec62c20) at kernel/qcore_unix.cpp:164
#5 0x00007efedaf9fbd3 in QEventDispatcherUNIX::processEvents (this=<optimised
out>, flags=...) at kernel/qeventdispatcher_unix.cpp:502
#6 0x000055eef9795681 in ?? ()
#7 0x00007efedaf47b8b in QEventLoop::exec (this=this@entry=0x7ffccec62d50,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#8 0x00007efedaf50024 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#9 0x000055eef9741235 in ?? ()
#10 0x00007efeda6d0565 in __libc_start_main (main=0x55eef973f1a0, argc=5,
argv=0x7ffccec63268, init=<optimised out>, fini=<optimised out>,
rtld_fini=<optimised out>, stack_end=0x7ffccec63258) at ../csu/libc-start.c:332
#11 0x000055eef9741afe in ?? ()
Unfortunately the backtrace is incomplete. :( It needs more debug symbols! See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_.28Ubuntu.2C_Kubuntu.2C_KDE_Neon.2C_Linux_Mint.29
--
You are receiving this mail because:
You are watching all bug changes.
