[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#809081: marked as done (konsole: Crash on mouse movement)

Your message dated Tue, 27 Dec 2016 17:30:45 +0100
with message-id <3733086.faIhzG7mUH@bagend>
and subject line Re: Bug#809081: konsole: Crash on mouse movement
has caused the Debian Bug report #809081,
regarding konsole: Crash on mouse movement
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
809081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809081
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: konsole
Version: 4:15.08.3-1
Severity: normal

I was using my mouse in vim in a Konsole window and it suddenly crashed.
As it wasn't on 'exit' this time, I'm filing a separate bug for it.
This is just the first time I experienced it and there's a reasonable
chance that I can't reproduce it. If it turns out I can, I'll report
back.

Stacktrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd672208940 (LWP 4256))]

Thread 2 (Thread 0x7fd65c21b700 (LWP 4257)):
#0  0x00007fd66a19e57c in __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x00007fd66a198895 in __GI___pthread_mutex_lock (mutex=0x968aa8) at ../nptl/pthread_mutex_lock.c:80
#2  0x00007fd66a7c258c in _xcb_conn_wait (c=c@entry=0x968a90, cond=cond@entry=0x968ad0, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:476
#3  0x00007fd66a7c3ff7 in xcb_wait_for_event (c=0x968a90) at ../../src/xcb_in.c:693
#4  0x00007fd65e1654f9 in QXcbEventReader::run() (this=0x976900) at qxcbconnection.cpp:1229
#5  0x00007fd66e68f87e in QThreadPrivate::start(void*) (arg=0x976900) at thread/qthread_unix.cpp:331
#6  0x00007fd66a196284 in start_thread (arg=0x7fd65c21b700) at pthread_create.c:333
#7  0x00007fd671cf974d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fd672208940 (LWP 4256)):
[KCrash Handler]
#6  0x00007fd66a7c3488 in poll_for_reply (c=c@entry=0x968a90, request=request@entry=47830, reply=reply@entry=0x7ffc928eef78, error=error@entry=0x7ffc928ef070) at ../../src/xcb_in.c:428
#7  0x00007fd66a7c3d4c in wait_for_reply (c=c@entry=0x968a90, request=47830, e=e@entry=0x7ffc928ef070) at ../../src/xcb_in.c:515
#8  0x00007fd66a7c3e41 in xcb_wait_for_reply (c=0x968a90, request=47830, e=0x7ffc928ef070) at ../../src/xcb_in.c:546
#9  0x00007fd66bd2f317 in _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
#10 0x00007fd65f35841f in XIQueryDevice () at /usr/lib/x86_64-linux-gnu/libXi.so.6
#11 0x00007fd65e18c9ee in QXcbConnection::handleEnterEvent(xcb_enter_notify_event_t const*) (this=0x93bcb0) at qxcbconnection_xi2.cpp:830
#12 0x00007fd65e17d34f in QXcbWindow::handleEnterNotifyEvent(xcb_enter_notify_event_t const*) (this=0xa98be0, event=0x7fd6540035f0) at qxcbwindow.cpp:2318
#13 0x00007fd65e16951d in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x93bcb0, event=event@entry=0x7fd6540035f0) at qxcbconnection.cpp:1069
#14 0x00007fd65e169d13 in QXcbConnection::processXcbEvents() (this=0x93bcb0) at qxcbconnection.cpp:1502
#15 0x00007fd66e8a0591 in QObject::event(QEvent*) (this=0x93bcb0, e=<optimized out>) at kernel/qobject.cpp:1239
#16 0x00007fd66f163ffc in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x956b80, receiver=receiver@entry=0x93bcb0, e=e@entry=0x7fd654003640) at kernel/qapplication.cpp:3716
#17 0x00007fd66f1694c6 in QApplication::notify(QObject*, QEvent*) (this=0x7ffc928ef9e0, receiver=0x93bcb0, e=0x7fd654003640) at kernel/qapplication.cpp:3499
#18 0x00007fd66e870b6b in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffc928ef9e0, receiver=0x93bcb0, event=event@entry=0x7fd654003640) at kernel/qcoreapplication.cpp:965
#19 0x00007fd66e872f66 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x7fd654003640, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#20 0x00007fd66e872f66 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x8fb490) at kernel/qcoreapplication.cpp:1593
#21 0x00007fd66e873448 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451
#22 0x00007fd66e8c6ed3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x99ec30) at kernel/qeventdispatcher_glib.cpp:271
#23 0x00007fd669a60fd7 in g_main_context_dispatch (context=0x7fd654001710) at /build/glib2.0-2.46.2/./glib/gmain.c:3154
#24 0x00007fd669a60fd7 in g_main_context_dispatch (context=context@entry=0x7fd654001710) at /build/glib2.0-2.46.2/./glib/gmain.c:3769
#25 0x00007fd669a61230 in g_main_context_iterate (context=context@entry=0x7fd654001710, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/glib2.0-2.46.2/./glib/gmain.c:3840
#26 0x00007fd669a612dc in g_main_context_iteration (context=0x7fd654001710, may_block=may_block@entry=1) at /build/glib2.0-2.46.2/./glib/gmain.c:3901
#27 0x00007fd66e8c72df in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x99ec10, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#28 0x00007fd66e86e2fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffc928ef8a0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#29 0x00007fd66e8763dc in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229
#30 0x00007fd66ebaa8bc in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1527
#31 0x00007fd66f160435 in QApplication::exec() () at kernel/qapplication.cpp:2976
#32 0x00007fd671fd636b in kdemain(int, char**) (argc=1, argv=0x7ffc928efb28) at ../../src/main.cpp:113
#33 0x00007fd671c31870 in __libc_start_main (main=0x400710 <main(int, char**)>, argc=1, argv=0x7ffc928efb28, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc928efb18) at libc-start.c:291
#34 0x0000000000400749 in _start () at ../sysdeps/x86_64/start.S:118


This looks a lot like https://bugs.kde.org/show_bug.cgi?id=353911 as it
also involves a mouse action and the stack traces look very similar.
Unfortunately it doesn't contain much info besides the stack trace.

If you want more information, just ask.

Diederik

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages konsole depends on:
ii  konsole-kpart           4:15.08.3-1
ii  libc6                   2.21-6
ii  libkf5completion5       5.16.0-1
ii  libkf5configcore5       5.16.0-1
ii  libkf5configgui5        5.16.0-1
ii  libkf5configwidgets5    5.16.0-1
ii  libkf5coreaddons5       5.16.0-1
ii  libkf5i18n5             5.16.0-1
ii  libkf5iconthemes5       5.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiowidgets5       5.16.0-1
ii  libkf5notifyconfig5     5.16.0-1
ii  libkf5widgetsaddons5    5.16.0-1
ii  libkf5windowsystem5     5.16.0-1
ii  libkf5xmlgui5           5.16.0-1
ii  libqt5core5a            5.5.1+dfsg-10
ii  libqt5gui5              5.5.1+dfsg-10
ii  libqt5widgets5          5.5.1+dfsg-10
ii  libstdc++6              5.3.1-4

konsole recommends no packages.

konsole suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
notfound 809081 konsole/4:15.08.3-1
thanks

On vrijdag 23 december 2016 17:05:38 CET Maximiliano Curia wrote:
> Upstream closed the issue as yet another qt issue regarding qscreen and xcb 
> (https://bugreports.qt.io/browse/QTBUG-42985), which should have been fixed
> in qt 5.5. Are you still being able to reproduce the issue? 

At some point the issue went away, while I don't think it was a konsole 
update, so likely (indeed) a qt update.
In various stack traces I've seen from my system, xcb is the one part which 
kept popping up, so the explanation looks plausible.

> If not, it would be better to close the issue.

Thanks for the reminder, should be done with this mail.

Cheers,
  Diederik

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: