[kde] [Bug 381878] New: Konsole crashes after exiting from the shell
Cezar Tigaret
bugzilla_noreply at kde.org
Sat Jul 1 20:37:55 BST 2017
https://bugs.kde.org/show_bug.cgi?id=381878
Bug ID: 381878
Summary: Konsole crashes after exiting from the shell
Product: kde
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: cezar.tigaret at gmail.com
Target Milestone: ---
Application: kdeinit5 (16.08.2)
Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.73-18.17-default x86_64
Distribution: "openSUSE Leap 42.2"
-- Information about the crash:
- What I was doing when the application crashed:
Just exited a bash sell session by calling "exit" at the command prompt. Had
successfully ran a python session from within the bash.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Konsole (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f135461b780 (LWP 10560))]
Thread 2 (Thread 0x7f1337752700 (LWP 10562)):
#0 0x00007f135279720d in poll () at /lib64/libc.so.6
#1 0x00007f134f209314 in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007f134f20942c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3 0x00007f1352d1b33b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQt5Core.so.5
#4 0x00007f1352cc8feb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQt5Core.so.5
#5 0x00007f1352b03f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x00007f1349549295 in () at /usr/lib64/libQt5DBus.so.5
#7 0x00007f1352b089e9 in () at /usr/lib64/libQt5Core.so.5
#8 0x00007f134fece744 in start_thread () at /lib64/libpthread.so.0
#9 0x00007f135279faad in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7f135461b780 (LWP 10560)):
[KCrash Handler]
#6 0x00007f13526ea8d7 in raise () at /lib64/libc.so.6
#7 0x00007f13526ebcaa in abort () at /lib64/libc.so.6
#8 0x00007f13527281b4 in () at /lib64/libc.so.6
#9 0x00007f135272d706 in malloc_printerr () at /lib64/libc.so.6
#10 0x00007f135272e453 in _int_free () at /lib64/libc.so.6
#11 0x00007f1352cf2f6b in QMetaCallEvent::~QMetaCallEvent() () at
/usr/lib64/libQt5Core.so.5
#12 0x00007f1352cf2fc9 in QMetaCallEvent::~QMetaCallEvent() () at
/usr/lib64/libQt5Core.so.5
#13 0x00007f1352ccdb0f in QCoreApplication::removePostedEvents(QObject*, int)
() at /usr/lib64/libQt5Core.so.5
#14 0x00007f1352cf5a97 in QObjectPrivate::~QObjectPrivate() () at
/usr/lib64/libQt5Core.so.5
#15 0x00007f1352cf5c49 in QObjectPrivate::~QObjectPrivate() () at
/usr/lib64/libQt5Core.so.5
#16 0x00007f1352cfd016 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#17 0x00007f1340ad0b69 in QXcbConnection::~QXcbConnection() () at
/usr/lib64/libQt5XcbQpa.so.5
#18 0x00007f1340ad778e in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#19 0x00007f1340ad7879 in QXcbIntegration::~QXcbIntegration() () at
/usr/lib64/libQt5XcbQpa.so.5
#20 0x00007f1353217f54 in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
at /usr/lib64/libQt5Gui.so.5
#21 0x00007f135137c159 in QApplicationPrivate::~QApplicationPrivate() () at
/usr/lib64/libQt5Widgets.so.5
#22 0x00007f1352cfd016 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#23 0x00007f1352ccca7e in QCoreApplication::~QCoreApplication() () at
/usr/lib64/libQt5Core.so.5
#24 0x00007f1353217daf in QGuiApplication::~QGuiApplication() () at
/usr/lib64/libQt5Gui.so.5
#25 0x00007f135137dcca in QApplication::~QApplication() () at
/usr/lib64/libQt5Widgets.so.5
#26 0x00007f135137de29 in QApplication::~QApplication() () at
/usr/lib64/libQt5Widgets.so.5
#27 0x00007f1341d4cc99 in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#28 0x0000000000408720 in ()
#29 0x0000000000409a1e in ()
#30 0x000000000040a101 in ()
#31 0x00000000004051bc in ()
#32 0x00007f13526d66e5 in __libc_start_main () at /lib64/libc.so.6
#33 0x0000000000405f79 in _start ()
Reported using DrKonqi
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list