| Summary: | Konsole crash when connecting bluetooth keyboard | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | Victor Mataré <vmatare+kdebug> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | vkrevs |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 15.08.0 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Victor Mataré
2015-12-14 09:58:05 UTC
Application: konsole (15.12.0) Qt Version: 5.5.1 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Had a konsole session with about a dozen tabs since yesterday. Today came into the office, ran a zypper dup command in one tab, attempted to switch to another tab, and konsole crashed. openSUSE 42.1 Leap with latest Plasma/Frameworks/Applications from OBS. $ rpm -qa | egrep "plasma|framework|konsole" | sort | grep -v debug frameworkintegration-plugin-5.18.0-88.1.x86_64 konsole-15.12.0-1.2.x86_64 konsole4-part-4.14.3-21.1.x86_64 konsole-part-15.12.0-1.2.x86_64 patterns-openSUSE-kde_plasma-20150918-12.1.x86_64 plasma5-addons-5.5.3-77.1.x86_64 plasma5-addons-kimpanel-5.5.3-77.1.x86_64 plasma5-addons-lang-5.5.3-77.1.noarch plasma5-desktop-5.5.3-133.4.x86_64 plasma5-desktop-branding-openSUSE-13.3-107.1.x86_64 plasma5-desktop-lang-5.5.3-133.4.noarch plasma5-pa-5.5.3-26.1.x86_64 plasma5-pa-lang-5.5.3-26.1.noarch plasma5-pk-updates-0.2-6.2.x86_64 plasma5-session-5.5.3-56.1.noarch plasma5-workspace-5.5.3-161.1.x86_64 plasma5-workspace-branding-openSUSE-13.3-107.1.x86_64 plasma5-workspace-lang-5.5.3-161.1.noarch plasma5-workspace-libs-5.5.3-161.1.x86_64 plasma5-workspace-wallpapers-5.5.2-51.1.noarch plasma-framework-5.18.0-95.1.x86_64 plasma-framework-components-5.18.0-95.1.x86_64 plasma-framework-lang-5.18.0-95.1.noarch plasma-framework-private-5.18.0-95.1.x86_64 plasma-nm5-5.5.3-91.4.x86_64 plasma-nm5-lang-5.5.3-91.4.noarch plasma-nm5-openconnect-5.5.3-91.4.x86_64 plasma-nm5-openvpn-5.5.3-91.4.x86_64 plasma-nm5-pptp-5.5.3-91.4.x86_64 plasma-nm5-vpnc-5.5.3-91.4.x86_64 python-kde4-plasma-4.14.3-2.11.x86_64 -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7724de2840 (LWP 20530))] Thread 2 (Thread 0x7f770dd26700 (LWP 20531)): #0 0x00007f772472b5cb in __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95 #1 0x00007f77246b7bca in _L_lock_10550 () at malloc.c:5203 #2 0x00007f77246b5705 in __GI___libc_malloc (bytes=140149212053536) at malloc.c:2886 #3 0x00007f7716e2a341 in () at /usr/lib64/tls/libnvidia-tls.so.352.63 #4 0x00007f771be8365d in _xcb_in_read (c=0x1970b60) at xcb_in.c:259 #5 0x00007f771be8365d in _xcb_in_read (c=c@entry=0x1970b60) at xcb_in.c:1012 #6 0x00007f771be81687 in _xcb_conn_wait (c=c@entry=0x1970b60, cond=cond@entry=0x1970ba0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:495 #7 0x00007f771be8300f in xcb_wait_for_event (c=0x1970b60) at xcb_in.c:693 #8 0x00007f77100833c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #9 0x00007f7720aeb32f in () at /usr/lib64/libQt5Core.so.5 #10 0x00007f771ba5e0a4 in start_thread (arg=0x7f770dd26700) at pthread_create.c:309 #11 0x00007f772471f04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f7724de2840 (LWP 20530)): [KCrash Handler] #6 0x00007f772466f187 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f7724670538 in __GI_abort () at abort.c:78 #8 0x00007f77246ac804 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f772479eb30 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x00007f77246b206e in malloc_printerr (action=3, str=0x7f772479acd5 "corrupted double-linked list", ptr=<optimized out>) at malloc.c:4993 #10 0x00007f77246b232c in malloc_consolidate (av=av@entry=0x7f7708000020) at malloc.c:4164 #11 0x00007f77246b2d31 in _int_free (av=0x7f7708000020, p=<optimized out>, have_lock=0) at malloc.c:4056 #12 0x00007f7710082e7a in QXcbConnection::processXcbEvents() () at /usr/lib64/libQt5XcbQpa.so.5 #13 0x00007f7720cf7ac6 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #14 0x00007f77219aae7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #15 0x00007f77219afcc8 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x00007f7720cc6e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #17 0x00007f7720cc9057 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #18 0x00007f7720d1e8f3 in () at /usr/lib64/libQt5Core.so.5 #19 0x00007f771b32ac84 in g_main_context_dispatch (context=0x7f7708001710) at gmain.c:3122 #20 0x00007f771b32ac84 in g_main_context_dispatch (context=context@entry=0x7f7708001710) at gmain.c:3737 #21 0x00007f771b32aed8 in g_main_context_iterate (context=context@entry=0x7f7708001710, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808 #22 0x00007f771b32af7c in g_main_context_iteration (context=0x7f7708001710, may_block=1) at gmain.c:3869 #23 0x00007f7720d1dd6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #24 0x00007f7720cc4d53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #25 0x00007f7720ccc8f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #26 0x00007f7724a09d51 in kdemain () at /usr/lib64/libkdeinit5_konsole.so #27 0x00007f772465bb05 in __libc_start_main (main=0x4007c0 <main>, argc=1, argv=0x7ffd68bfeba8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd68bfeb98) at libc-start.c:285 #28 0x00000000004007ee in _start () Reported using DrKonqi Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Haven't seen this in a long time, so |