Application: konversation (1.7.4) Qt Version: 5.10.1 Frameworks Version: 5.44.0 Operating System: Linux 4.15.14-1-zen x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I was exiting Konversation after leaving it running for a few hours. It crashed upon closing. The crash can be reproduced sometimes. -- Backtrace: Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7ffa2edecd80 (LWP 1329))] Thread 2 (Thread 0x7ffa194d1700 (LWP 1330)): #0 0x00007ffa279bf97b in poll () at /usr/lib/libc.so.6 #1 0x00007ffa21c4a613 in () at /usr/lib/libglib-2.0.so.0 #2 0x00007ffa21c4a72e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x00007ffa28657264 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #4 0x00007ffa285f932b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #5 0x00007ffa2840872e in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x00007ffa28a7a416 in () at /usr/lib/libQt5DBus.so.5 #7 0x00007ffa2840dacd in () at /usr/lib/libQt5Core.so.5 #8 0x00007ffa25aeb08c in start_thread () at /usr/lib/libpthread.so.0 #9 0x00007ffa279c9e7f in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7ffa2edecd80 (LWP 1329)): [KCrash Handler] #6 0x00007ffa1c7057f9 in () at /usr/lib/libwayland-client.so.0 #7 0x00007ffa1c7017e7 in wl_proxy_destroy () at /usr/lib/libwayland-client.so.0 #8 0x00007ffa1b00e7c9 in KWayland::Client::Shadow::release() () at /usr/lib/libKF5WaylandClient.so.5 #9 0x00007ffa1b00e7eb in KWayland::Client::Shadow::~Shadow() () at /usr/lib/libKF5WaylandClient.so.5 #10 0x00007ffa1b00e85a in KWayland::Client::Shadow::~Shadow() () at /usr/lib/libKF5WaylandClient.so.5 #11 0x00007ffa2862915d in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #12 0x00007ffa2963e8d5 in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #13 0x00007ffa2978a05a in QMenu::~QMenu() () at /usr/lib/libQt5Widgets.so.5 #14 0x0000564fab6a41ff in () #15 0x0000564fab6a4349 in () #16 0x00007ffa2790b448 in __run_exit_handlers () at /usr/lib/libc.so.6 #17 0x00007ffa2790b49a in () at /usr/lib/libc.so.6 #18 0x00007ffa278f4f51 in __libc_start_main () at /usr/lib/libc.so.6 #19 0x0000564fab57ba9a in _start () Reported using DrKonqi
I also had this once but not sure how to reproduce it.
Slightly better backtrace: Application: Konversation (konversation), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff753d73880 (LWP 4104))] Thread 2 (Thread 0x7ff733e61700 (LWP 4105)): #0 0x00007ff743bae400 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x00007ff743b67c28 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #2 0x00007ff74cc0454b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #3 0x00007ff74cbafd2a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #4 0x00007ff74ca009ba in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #5 0x00007ff74d01b641 in ?? () from /usr/lib64/libQt5DBus.so.5 #6 0x00007ff74ca05097 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x00007ff749941877 in start_thread () from /lib64/libpthread.so.0 #8 0x00007ff74bd8048f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff753d73880 (LWP 4104)): [KCrash Handler] #6 0x00007ff7367e7c0c in wl_map_insert_at () from /usr/lib64/libwayland-client.so.0 #7 0x00007ff7367e3cfe in wl_proxy_destroy () from /usr/lib64/libwayland-client.so.0 #8 0x00007ff73550453b in org_kde_kwin_shadow_destroy (org_kde_kwin_shadow=0x561f1812fd90) at /var/tmp/portage/kde-frameworks/kwayland-5.44.0/work/kwayland-5.44.0_build/src/client/wayland-shadow-client-protocol.h:375 #9 0x00007ff7355054ec in KWayland::Client::WaylandPointer<org_kde_kwin_shadow, org_kde_kwin_shadow_destroy>::release (this=0x561f18133b80) at /var/tmp/portage/kde-frameworks/kwayland-5.44.0/work/kwayland-5.44.0/src/client/wayland_pointer_p.h:53 #10 0x00007ff7355049d4 in KWayland::Client::Shadow::release (this=0x561f18108ed0) at /var/tmp/portage/kde-frameworks/kwayland-5.44.0/work/kwayland-5.44.0/src/client/shadow.cpp:134 #11 0x00007ff73550496a in KWayland::Client::Shadow::~Shadow (this=0x561f18108ed0, __in_chrg=<optimized out>) at /var/tmp/portage/kde-frameworks/kwayland-5.44.0/work/kwayland-5.44.0/src/client/shadow.cpp:129 #12 0x00007ff7355049a2 in KWayland::Client::Shadow::~Shadow (this=0x561f18108ed0, __in_chrg=<optimized out>) at /var/tmp/portage/kde-frameworks/kwayland-5.44.0/work/kwayland-5.44.0/src/client/shadow.cpp:130 #13 0x00007ff74cbe16de in QObjectPrivate::deleteChildren() () from /usr/lib64/libQt5Core.so.5 #14 0x00007ff74db1cadd in QWidget::~QWidget (this=0x561f17943360, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1700 #15 0x00007ff74dceec4b in QMenu::~QMenu (this=0x561f17943360, __in_chrg=<optimized out>) at widgets/qmenu.cpp:1675 #16 0x00007ff74dceec84 in QMenu::~QMenu (this=0x561f17943360, __in_chrg=<optimized out>) at widgets/qmenu.cpp:1692 #17 0x0000561f15b3df8c in ?? () #18 0x0000561f15b3e059 in ?? () #19 0x00007ff74bcbe238 in ?? () from /lib64/libc.so.6 #20 0x00007ff74bcbe29a in exit () from /lib64/libc.so.6 #21 0x00007ff74bca6511 in __libc_start_main () from /lib64/libc.so.6 #22 0x0000561f15a31faa in _start ()
I doubt this is a KWayland problem. It looks to me like incorrect cleanup by either konversation or breeze widget style. But from the backtrace it looks like a dangling menu to me.
*** Bug 403654 has been marked as a duplicate of this bug. ***
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status when you reply to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!