Konsole crashes when closing a terminal

[Wesley Schwengle]

https://bugs.kde.org/show_bug.cgi?id=324501

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty

$ apt-cache policy konsole
konsole:
  Installed: 4:4.13.3-0ubuntu0.1
  Candidate: 4:4.13.3-0ubuntu0.1
  Version table:
     4:4.14.0-0ubuntu1 0
        100 http://archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
 *** 4:4.13.3-0ubuntu0.1 0
        500 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     4:4.13.0-0ubuntu1 0
        500 http://nl.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
     4:4.8.2-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

[Aleksi-uotila (aleksi-uotila)]

Application: konsole (2.10.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.4
Operating System: Linux 3.8.0-29-generic x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:

gave exit command on a tab and it crashed. I had other tabs open.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f52b94fa7c0 (LWP 2192))]

Thread 2 (Thread 0x7f52a32bd700 (LWP 2237)):
#0 0x00007f52b2eaa359 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007f52b2eaa5b9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f52b2e6a90b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f52b2e6b0fe in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f52b2e6b304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f52b79f4036 in QEventDispatcherGlib::processEvents (this=0x7f52940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6 0x00007f52b79c438f in QEventLoop::processEvents (this=this@entry=0x7f52a32bcd90, flags=...) at kernel/qeventloop.cpp:149
#7 0x00007f52b79c4618 in QEventLoop::exec (this=this@entry=0x7f52a32bcd90, flags=...) at kernel/qeventloop.cpp:204
#8 0x00007f52b78c6410 in QThread::exec (this=this@entry=0x19fd750) at thread/qthread.cpp:542
#9 0x00007f52b79a5edf in QInotifyFileSystemWatcherEngine::run (this=0x19fd750) at io/qfilesystemwatcher_inotify.cpp:256
#10 0x00007f52b78c8bec in QThreadPrivate::start (arg=0x19fd750) at thread/qthread_unix.cpp:338
#11 0x00007f52b3743f8e in start_thread (arg=0x7f52a32bd700) at pthread_create.c:311
#12 0x00007f52b8e2be1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f52b94fa7c0 (LWP 2192)):
[KCrash Handler]
#6 parent (this=0x1b1b440) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:273
#7 parentWidget (this=0x1b1b440) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:1033
#8 QWidget::window (this=this@entry=0x1b1b450) at kernel/qwidget.cpp:4350
#9 0x00007f52b6d714f4 in QApplicationPrivate::dispatchEnterLeave (enter=enter@entry=0x179f8f0, leave=0x1b1b450) at kernel/qapplication.cpp:2761
#10 0x00007f52b6d718e9 in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x179f8f0, event=event@entry=0x7fff89b88c50, alienWidget=alienWidget@entry=0x179f8f0, nativeWidget=nativeWidget@entry=0x1752600, buttonDown=buttonDown@entry=0x7f52b7849308 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3158
#11 0x00007f52b6de6ec4 in QETWidget::translateMouseEvent (this=this@entry=0x1752600, event=event@entry=0x7fff89b893d0) at kernel/qapplication_x11.cpp:4631
#12 0x00007f52b6de5ef1 in QApplication::x11ProcessEvent (this=0x7fff89b898f0, event=event@entry=0x7fff89b893d0) at kernel/qapplication_x11.cpp:3746
#13 0x00007f52b6e110b2 in x11EventSourceDispatch (s=0x163d270, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#14 0x00007f52b2e6af05 in g_main_context_di...

[Kde-m (kde-m)]

I can verify this bug in 4.13.3 (Ubuntu).