Bug 352361 - Konsole crashed unexpectedly in background
Summary: Konsole crashed unexpectedly in background
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 15.08.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-09-06 19:41 UTC by Kévin Lesénéchal
Modified: 2017-02-18 23:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kévin Lesénéchal 2015-09-06 19:41:37 UTC
Application: konsole (15.08.0)

Qt Version: 5.5.0
Operating System: Linux 4.1.6-1-ARCH x86_64
Distribution: "Arch Linux"

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

Konsole crashed unexpectedly while running in the background. 2 tabs were open, one with GNU screen running, the other a SSH connection. No interactions were done causing the crashing, I was just watching the terminal.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1a67a42840 (LWP 1028))]

Thread 2 (Thread 0x7f1a501d4700 (LWP 1032)):
#0  0x00007f1a6745365b in __lll_lock_wait_private () from /usr/lib/libc.so.6
#1  0x00007f1a673d947a in malloc () from /usr/lib/libc.so.6
#2  0x00007f1a59486341 in ?? () from /usr/lib/libnvidia-tls.so.352.41
#3  0x00007f1a5ea1fdba in ?? () from /usr/lib/libxcb.so.1
#4  0x00007f1a5ea1dc61 in ?? () from /usr/lib/libxcb.so.1
#5  0x00007f1a5ea1f56f in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#6  0x00007f1a51f12ca9 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#7  0x00007f1a636f7a9e in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007f1a5e3f34a4 in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007f1a6744712d in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f1a67a42840 (LWP 1028)):
[KCrash Handler]
#5  0x00007f1a673915f8 in raise () from /usr/lib/libc.so.6
#6  0x00007f1a67392a7a in abort () from /usr/lib/libc.so.6
#7  0x00007f1a673d005a in __libc_message () from /usr/lib/libc.so.6
#8  0x00007f1a673d59a6 in malloc_printerr () from /usr/lib/libc.so.6
#9  0x00007f1a673d5c71 in malloc_consolidate () from /usr/lib/libc.so.6
#10 0x00007f1a673d6810 in _int_free () from /usr/lib/libc.so.6
#11 0x00007f1a51f17148 in QXcbConnection::processXcbEvents() () from /usr/lib/libQt5XcbQpa.so.5
#12 0x00007f1a63907eb1 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#13 0x00007f1a6461200c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#14 0x00007f1a646174e6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#15 0x00007f1a638d889b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#16 0x00007f1a638dac96 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#17 0x00007f1a6392ee33 in ?? () from /usr/lib/libQt5Core.so.5
#18 0x00007f1a5dcc09fd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x00007f1a5dcc0ce0 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0x00007f1a5dcc0d8c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0x00007f1a6392f23f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#22 0x00007f1a638d626a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#23 0x00007f1a638de20c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#24 0x00007f1a67725a46 in kdemain () from /usr/lib/libkdeinit5_konsole.so
#25 0x00007f1a6737e610 in __libc_start_main () from /usr/lib/libc.so.6
#26 0x0000000000400779 in _start ()

Possible duplicates by query: bug 352099, bug 351797, bug 351165, bug 351052, bug 350800.

Reported using DrKonqi
Comment 1 Kurt Hindenburg 2017-02-18 23:10:02 UTC
Thanks - there's not really enough info here - please update and let us know if you still have issues.