Bug 373823 - Konsole crashed after wakeup from suspend
Summary: Konsole crashed after wakeup from suspend
Status: RESOLVED DUPLICATE of bug 373865
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 16.08.2
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-12-18 13:59 UTC by Lubos Dolezel
Modified: 2016-12-20 18:03 UTC (History)
0 users

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 Lubos Dolezel 2016-12-18 13:59:36 UTC
Application: konsole (16.08.2)

Qt Version: 5.7.1
Frameworks Version: 5.27.0
Operating System: Linux 4.8.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

Woke up my laptop from suspend and saw Konsole crash for no obvious reason.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcbeca51940 (LWP 12473))]

Thread 3 (Thread 0x7fcbd30e8700 (LWP 12475)):
#0  0x00007fcbe3a8cf09 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fcbe3a8d91b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fcbe3a8db0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcbe91196fb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007fcbe90c307a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fcbe8ee50d3 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007fcbecb266d5 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fcbe8ee9d88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fcbe574c464 in start_thread (arg=0x7fcbd30e8700) at pthread_create.c:333
#9  0x00007fcbec5269df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fcbd90be700 (LWP 12474)):
#0  0x00007fcbec51d56d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fcbe5b71150 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fcbe5b72ee9 in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fcbdade3b69 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007fcbe8ee9d88 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fcbe574c464 in start_thread (arg=0x7fcbd90be700) at pthread_create.c:333
#6  0x00007fcbec5269df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7fcbeca51940 (LWP 12473)):
[KCrash Handler]
#6  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#7  0x00007fcbec47240a in __GI_abort () at abort.c:89
#8  0x00007fcbec4aebd0 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fcbec5a3c70 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#9  0x00007fcbec4b4fa6 in malloc_printerr (action=3, str=0x7fcbec5a3ce8 "double free or corruption (!prev)", ptr=<optimized out>, ar_ptr=<optimized out>) at malloc.c:5046
#10 0x00007fcbec4b579e in _int_free (av=0x7fcbec7d6b00 <main_arena>, p=0x55bd1c28a010, have_lock=0) at malloc.c:3902
#11 0x00007fcbdbce8771 in XIQueryDevice () from /lib/x86_64-linux-gnu/libXi.so.6
#12 0x00007fcbdae0e687 in QXcbConnection::touchDeviceForId(int) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#13 0x00007fcbdae0fe24 in QXcbConnection::xi2SetupDevices() () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#14 0x00007fcbdae1309c in QXcbConnection::xi2HandleHierachyEvent(void*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#15 0x00007fcbdae13173 in QXcbConnection::xi2HandleEvent(xcb_ge_event_t*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#16 0x00007fcbdade5aca in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#17 0x00007fcbdade6015 in QXcbConnection::processXcbEvents() () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#18 0x00007fcbe90f1b39 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007fcbe9c42b2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007fcbe9c4a2e1 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007fcbe90c5090 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fcbe90c781d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007fcbe91192d3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007fcbe3a8d7f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007fcbe3a8da60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007fcbe3a8db0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007fcbe91196df in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x00007fcbe90c307a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x00007fcbe90cb7ec in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x00007fcbec803cd8 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_konsole.so
#31 0x00007fcbec45e2b1 in __libc_start_main (main=0x55bd194eb780, argc=1, argv=0x7ffdcf3696e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdcf3696d8) at ../csu/libc-start.c:291
#32 0x000055bd194eb7ba in _start ()

Possible duplicates by query: bug 371957, bug 364287, bug 364188, bug 363636, bug 360774.

Reported using DrKonqi
Comment 1 Christoph Feck 2016-12-20 17:56:25 UTC
Did you remove/connect any input devices during the suspend?
Comment 2 Christoph Feck 2016-12-20 17:57:49 UTC

*** This bug has been marked as a duplicate of bug 373865 ***
Comment 3 Lubos Dolezel 2016-12-20 18:03:19 UTC
I don't remember, but I use a Bluetooth mouse so input device reconnects are very common.