Summary: | Konsole process doesn't terminate when window is closed by the close button in the Titlebar. | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | lnxusr |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | rdieter |
Priority: | NOR | ||
Version: | 15.08.0 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
lnxusr
2015-11-22 22:51:14 UTC
Sorry, I forgot to mention that the bash process associated with the Konsole does terminate properly. It's only the Konsole process that remains running. I just had Konsole crash on me when I typed 'exit' to quit. The process is still listed however it's not using any CPU and is listed as stopped. This is the first time this has happened closing it in this fashion. Here's the info from the crash handler: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x00007fdb5ebb2267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x00007fdb5ebb3eca in __GI_abort () at abort.c:89 #8 0x00007fdb5ebf5c53 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fdb5ed0e1a8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x00007fdb5ebfdc69 in malloc_printerr (ptr=<optimized out>, str=0x7fdb5ed0e2b8 "double free or corruption (out)", action=1) at malloc.c:4965 #10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3834 #11 0x00007fdb5ec0189c in __GI___libc_free (mem=<optimized out>) at malloc.c:2950 #12 0x00007fdb5b894b9c in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x00007fdb5b894be9 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007fdb5b869807 in QCoreApplication::removePostedEvents(QObject*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007fdb5b896e92 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x00007fdb5b896fb9 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007fdb5b89f668 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007fdb4beb7229 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #19 0x00007fdb4bebaa4e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #20 0x00007fdb4bebab49 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #21 0x00007fdb5bb8013e in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x00007fdb5c12fc49 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x00007fdb5b89f668 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00007fdb5c1319ab in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x00007fdb5ef68be5 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so #26 0x00007fdb5eb9da40 in __libc_start_main (main=0x400730 <main>, argc=1, argv=0x7ffdff7431f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdff7431e8) at libc-start.c:289 #27 0x0000000000400769 in _start () Closing out the crash handler also killed the process. I suppose this is an expected feature not a problem. Are you using nvidia driver? If so, then it's likely a dup of bug #343803 *** This bug has been marked as a duplicate of bug 343803 *** |