Bug 337720 - Konsole crashes on exit command
Summary: Konsole crashes on exit command
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.13.2
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-23 08:56 UTC by Brandon Taylor
Modified: 2018-02-17 05:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Konsole backtrace from 7-23-2014 (3.45 KB, text/plain)
2014-07-23 08:56 UTC, Brandon Taylor
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brandon Taylor 2014-07-23 08:56:56 UTC
Created attachment 87896 [details]
Konsole backtrace from 7-23-2014

I had just finished using the Konsole app, and had typed in the "exit" command. Konsole closed as if nothing was wrong, but then the Crash Reporting Assistant appeared saying Konsole crashed.
Comment 1 Myriam Schweingruber 2014-12-15 11:36:34 UTC
Backtrace )please always paste those inline, else the database is not searchable):

Application: konsole (2.13.2)
KDE Platform Version: 4.13.2
Qt Version: 4.8.6
Operating System: Linux 3.15.4-031504-generic x86_64
Distribution: Ubuntu 14.04 LTS

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

I had just finished using the Konsole app, and had typed in the "exit" command. Konsole closed as if nothing was wrong, but then the Crash Reporting Assistant appeared saying Konsole crashed.

-- 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 0x7f69364e17c0 (LWP 20920))]

Thread 2 (Thread 0x7f6920136700 (LWP 20921)):
#0  0x00007f6935e13fbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f692f188fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f692f1890ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f69345227be in QEventDispatcherGlib::processEvents (this=0x7f69180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007f69344f40af in QEventLoop::processEvents (this=this@entry=0x7f6920135de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f69344f43a5 in QEventLoop::exec (this=this@entry=0x7f6920135de0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f69343f0c5f in QThread::exec (this=this@entry=0xf90620) at thread/qthread.cpp:537
#7  0x00007f69344d5823 in QInotifyFileSystemWatcherEngine::run (this=0xf90620) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007f69343f332f in QThreadPrivate::start (arg=0xf90620) at thread/qthread_unix.cpp:349
#9  0x00007f692fa6f182 in start_thread (arg=0x7f6920136700) at pthread_create.c:312
#10 0x00007f6935e2130d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f69364e17c0 (LWP 20920)):
[KCrash Handler]
#6  0x00007f6934373860 in QRegion::shared_empty () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
#7  0x00007f6933908090 in QApplication::x11ProcessEvent (this=0x7fffefcc8ba0, event=event@entry=0x7fffefcc86a0) at kernel/qapplication_x11.cpp:3529
#8  0x00007f6933930b02 in x11EventSourceDispatch (s=0xb69870, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#9  0x00007f692f188e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f692f189048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f692f1890ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f69345227be in QEventDispatcherGlib::processEvents (this=0xab3af0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#13 0x00007f6933930bb6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f69344f40af in QEventLoop::processEvents (this=this@entry=0x7fffefcc8a70, flags=...) at kernel/qeventloop.cpp:149
#15 0x00007f69344f43a5 in QEventLoop::exec (this=this@entry=0x7fffefcc8a70, flags=...) at kernel/qeventloop.cpp:204
#16 0x00007f69344f9b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#17 0x00007f693388d37c in QApplication::exec () at kernel/qapplication.cpp:3828
#18 0x00007f69361046f7 in kdemain (argc=1, argv=0x7fffefcc8ce8) at ../../src/main.cpp:86
#19 0x00007f6935d47ec5 in __libc_start_main (main=0x4006d0 <main(int, char**)>, argc=1, argv=0x7fffefcc8ce8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffefcc8cd8) at libc-start.c:287
#20 0x00000000004006fe in _start ()
Comment 2 Andrei 2015-05-22 01:01:15 UTC
This happens to me as well, every time I exit Konsole. It doesn't matter if I use the close button, the exit command or Ctrl-D.

Below is my info, although I'm unable get a better stack trace because I cannot find debug symbols for libqt5dbus5.

Konsole 15.04.0
KDE Frameworks Version 5.9.0
Qt Version 5.4.1
Operating System: Linux 3.19.0-16-generic x86_64 (Ubuntu 15.04)

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 0x7fcd6fec7800 (LWP 30404))]

Thread 2 (Thread 0x7fcd4ebab700 (LWP 30406)):
#0  0x00007fcd6f987743 in select () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fcd6c48a89f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007fcd6c2bab0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007fcd67e626aa in start_thread (arg=0x7fcd4ebab700) at pthread_create.c:333
#4  0x00007fcd6f990eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fcd6fec7800 (LWP 30404)):
[KCrash Handler]
#6  0x00007fcd6ff77313 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fcd6ff6c992 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8  0x00007fcd6ff6cc50 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007fcd6ff60df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007fcd6ff60ea9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x00007fcd6f8c3d32 in __run_exit_handlers (status=0, listp=0x7fcd6fc4e698 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#12 0x00007fcd6f8c3d85 in __GI_exit (status=<optimized out>) at exit.c:104
#13 0x00007fcd6f8aaa47 in __libc_start_main (main=0x400720 <main(int, char**)>, argc=1, argv=0x7ffff5206b58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff5206b48) at libc-start.c:323
#14 0x0000000000400759 in _start ()
Comment 3 Ahmad Samir 2018-02-17 05:46:37 UTC
Reopen if you can still reproduce the issue. (Note that libqt5dbus* is most likely part of the qtbase package, whatever it's called in Ubuntu, so if can still reproduce please install the necessary debug packages to get a full backtrace). Thanks.