https://bugs.kde.org/show_bug.cgi?id=490970
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|wayland-generic |tabbox
CC| |n...@kde.org
Status|REPORTED |NEEDSINFO
Resolution|--- |BACKTRACE
--- Comment #4 from Nate Graham <n...@kde.org> ---
Hmm, the backtrace doesn't make much sense. It's saying that this is the
crashing thread:
Stack trace of thread 90033:
#0 0x00007cbeb231abb0 ppoll (libc.so.6 + 0x10bbb0)
#1 0x00007cbeb2ab93ab
_Z12qt_safe_pollP6pollfdm14QDeadlineTimer (libQt6Core.so.6 + 0x2b93ab)
#2 0x00007cbeb2ac60f3
_ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt6Core.so.6 + 0x2c60f3)
#3 0x00007cbeb33f9693
_ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt6Gui.so.6 + 0x5f9693)
#4 0x00007cbeb294f01e
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 +
0x14f01e)
#5 0x00007cbeb294934d _ZN16QCoreApplication4execEv
(libQt6Core.so.6 + 0x14934d)
#6 0x00005856153e2015 n/a (kwin_wayland + 0x3d015)
#7 0x00007cbeb2234e08 n/a (libc.so.6 + 0x25e08)
#8 0x00007cbeb2234ecc __libc_start_main (libc.so.6 + 0x25ecc)
#9 0x00005856153e7fb5 n/a (kwin_wayland + 0x42fb5)
But it doesn't look like a crashing thread to me.
Can you following the instructions in
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
to get a new backtrace that shows only the crashing thread? Maybe it will be
different this time and show something more actionable.
--
You are receiving this mail because:
You are watching all bug changes.
