Application: kmahjongg (0.9) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.92-31-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: I had played an intriguing game and saved it to my home drive. On pressing tne Save button on the file save dialog that dialog closed and the error report dialog started. -- Backtrace: Application: KMahjongg (kmahjongg), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7eff9fb79780 (LWP 4118))] Thread 2 (Thread 0x7eff83477700 (LWP 4121)): #0 0x00007eff9c01620d in poll () at /lib64/libc.so.6 #1 0x00007eff97542314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007eff9754242c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007eff9c9231ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007eff9c8d0bfb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007eff9c70bf5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007eff982f0295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x00007eff9c710a29 in () at /usr/lib64/libQt5Core.so.5 #8 0x00007eff97c76744 in start_thread () at /lib64/libpthread.so.0 #9 0x00007eff9c01eaad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7eff9fb79780 (LWP 4118)): [KCrash Handler] #6 0x0000000001d2fe10 in () #7 0x00007eff8a480bde in () at /usr/lib64/libKF5Notifications.so.5 #8 0x00007eff8a480c79 in () at /usr/lib64/libKF5Notifications.so.5 #9 0x00007eff9c8fb6c5 in QObjectPrivate::deleteChildren() () at /usr/lib64/libQt5Core.so.5 #10 0x00007eff9c904c7e in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5 #11 0x00007eff8a45f769 in () at /usr/lib64/libKF5Notifications.so.5 #12 0x00007eff9bf6c139 in __run_exit_handlers () at /lib64/libc.so.6 #13 0x00007eff9bf6c185 in () at /lib64/libc.so.6 #14 0x00007eff9bf556ec in __libc_start_main () at /lib64/libc.so.6 #15 0x00000000004142e9 in _start () Reported using DrKonqi
*** This bug has been marked as a duplicate of bug 380114 ***