Bug 363720 - Konsole crash when closing
Summary: Konsole crash when closing
Status: RESOLVED DUPLICATE of bug 346826
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 16.04.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-05-30 21:18 UTC by Marek Śledziona
Modified: 2016-08-13 18:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Śledziona 2016-05-30 21:18:33 UTC
Application: konsole (16.04.1)

Qt Version: 5.6.0
Frameworks Version: 5.22.0
Operating System: Linux 4.1.21-14-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
Did a distribution upgrade using 'zypper dup'. Updates were properly installed and then I closed the Konsole window. That caused Konsole to crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa745901840 (LWP 5600))]

Thread 3 (Thread 0x7fa731e51700 (LWP 5601)):
#0  0x00007fa745230bbd in poll () at /lib64/libc.so.6
#1  0x00007fa73be35e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fa73be35f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fa74181b3fb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007fa7417c904b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007fa7416055da in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007fa73f9e1095 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x00007fa74160a079 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007fa73c5690a4 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fa745238fed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fa72ab18700 (LWP 5602)):
#0  0x00007fa74524556b in __lll_lock_wait_private () at /lib64/libc.so.6
#1  0x00007fa7451d1c81 in _L_lock_11968 () at /lib64/libc.so.6
#2  0x00007fa7451cfff1 in calloc () at /lib64/libc.so.6
#3  0x00007fa73792221e in  () at /usr/lib64/tls/libnvidia-tls.so.361.42
#4  0x00007fa73c568e62 in __nptl_deallocate_tsd () at /lib64/libpthread.so.0
#5  0x00007fa73c5690b7 in start_thread () at /lib64/libpthread.so.0
#6  0x00007fa745238fed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fa745901840 (LWP 5600)):
[KCrash Handler]
#6  0x00007fa7451cc185 in malloc_consolidate () at /lib64/libc.so.6
#7  0x00007fa7451ccc91 in _int_free () at /lib64/libc.so.6
#8  0x00007fa7311cc940 in  () at /usr/lib64/libQt5XcbQpa.so.5
#9  0x00007fa73119b8f1 in QXcbConnection::~QXcbConnection() () at /usr/lib64/libQt5XcbQpa.so.5
#10 0x00007fa73119c099 in QXcbConnection::~QXcbConnection() () at /usr/lib64/libQt5XcbQpa.so.5
#11 0x00007fa7311a2cbe in QXcbIntegration::~QXcbIntegration() () at /usr/lib64/libQt5XcbQpa.so.5
#12 0x00007fa7311a2da9 in QXcbIntegration::~QXcbIntegration() () at /usr/lib64/libQt5XcbQpa.so.5
#13 0x00007fa741d180e4 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () at /usr/lib64/libQt5Gui.so.5
#14 0x00007fa7424cba89 in QApplicationPrivate::~QApplicationPrivate() () at /usr/lib64/libQt5Widgets.so.5
#15 0x00007fa7417fd0b6 in QObject::~QObject() () at /usr/lib64/libQt5Core.so.5
#16 0x00007fa7417ccaae in QCoreApplication::~QCoreApplication() () at /usr/lib64/libQt5Core.so.5
#17 0x00007fa741d17f3f in QGuiApplication::~QGuiApplication() () at /usr/lib64/libQt5Gui.so.5
#18 0x00007fa7424cd4ba in QApplication::~QApplication() () at /usr/lib64/libQt5Widgets.so.5
#19 0x00007fa745524e93 in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#20 0x00007fa745175b05 in __libc_start_main () at /lib64/libc.so.6
#21 0x000000000040078e in _start ()

Reported using DrKonqi
Comment 1 Martin Sandsmark 2016-08-13 18:03:29 UTC

*** This bug has been marked as a duplicate of bug 346826 ***