Bug 287840 - KRDC crash with no obvious reason.
Summary: KRDC crash with no obvious reason.
Status: RESOLVED DUPLICATE of bug 261571
Alias: None
Product: krdc
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-29 14:35 UTC by underline
Modified: 2011-12-03 09:33 UTC (History)
3 users (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 underline 2011-11-29 14:35:22 UTC
Application: krdc (4.7.2 (4.7.2))
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
KRDC crashed when I performed operations on the remote machines very quickly, like scrolling then clicking etc.

-- Backtrace:
Application: KRDC (krdc), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fd19df43780 (LWP 6162))]

Thread 3 (Thread 0x7fd18931d700 (LWP 6165)):
#0  0x00007fd19ab67773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fd1977d7f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fd1977d8429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fd19b2cff3e in QEventDispatcherGlib::processEvents (this=0x1024040, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fd19b2a3cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fd19b2a3ef7 in QEventLoop::exec (this=0x7fd18931cdd0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fd19b1bb27f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007fd19b286cbf in QInotifyFileSystemWatcherEngine::run (this=0x10230d0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fd19b1bdd05 in QThreadPrivate::start (arg=0x10230d0) at thread/qthread_unix.cpp:331
#9  0x00007fd197ca9efc in start_thread (arg=0x7fd18931d700) at pthread_create.c:304
#10 0x00007fd19ab7389d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fd188a6b700 (LWP 6166)):
[KCrash Handler]
#6  0x00007fd18bbf96a5 in VncClientThread::run (this=0x11d8540) at ../../../krdc/vnc/vncclientthread.cpp:397
#7  0x00007fd19b1bdd05 in QThreadPrivate::start (arg=0x11d8540) at thread/qthread_unix.cpp:331
#8  0x00007fd197ca9efc in start_thread (arg=0x7fd188a6b700) at pthread_create.c:304
#9  0x00007fd19ab7389d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fd19df43780 (LWP 6162)):
#0  0x00007fd19ab67773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fd1956a94f2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fd1956a9a3f in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fd1956a9ac4 in xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x00007fd199f36597 in _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5  0x00007fd199f36acb in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6  0x00007fd199f33bed in XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7  0x00007fd19bd3a899 in QWidgetPrivate::mapFromGlobal (this=0x11d0570, pos=<optimized out>) at kernel/qwidget_x11.cpp:1337
#8  0x00007fd19bd3a93d in QWidget::mapFromGlobal (this=<optimized out>, pos=<optimized out>) at kernel/qwidget_x11.cpp:1350
#9  0x00007fd19bcaacee in QApplication::notify (this=<optimized out>, receiver=0x11d84e0, e=0x7fff24e81650) at kernel/qapplication.cpp:4067
#10 0x00007fd19c9b9126 in KApplication::notify (this=0x7fff24e822b0, receiver=0x11d84e0, event=0x7fff24e81650) at ../../kdeui/kernel/kapplication.cpp:311
#11 0x00007fd19b2a4afc in QCoreApplication::notifyInternal (this=0x7fff24e822b0, receiver=0x11d84e0, event=0x7fff24e81650) at kernel/qcoreapplication.cpp:787
#12 0x00007fd19bca63f2 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#13 QApplicationPrivate::sendMouseEvent (receiver=0x11d84e0, event=0x7fff24e81650, alienWidget=0x0, nativeWidget=0x11d84e0, buttonDown=0x0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3146
#14 0x00007fd19bd25945 in QETWidget::translateMouseEvent (this=0x11d84e0, event=<optimized out>) at kernel/qapplication_x11.cpp:4568
#15 0x00007fd19bd248be in QApplication::x11ProcessEvent (this=0x7fff24e822b0, event=0x7fff24e81e70) at kernel/qapplication_x11.cpp:3690
#16 0x00007fd19bd4d412 in x11EventSourceDispatch (s=0x91ee20, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#17 0x00007fd1977d7a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fd1977d8258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fd1977d8429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fd19b2cfed6 in QEventDispatcherGlib::processEvents (this=0x9003b0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#21 0x00007fd19bd4d07e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fd19b2a3cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#23 0x00007fd19b2a3ef7 in QEventLoop::exec (this=0x7fff24e82240, flags=...) at kernel/qeventloop.cpp:201
#24 0x00007fd19b2a8789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#25 0x0000000000415558 in main (argc=3, argv=0x7fff24e82878) at ../../krdc/main.cpp:104

This bug may be a duplicate of or related to bug 261571.

Possible duplicates by query: bug 286077, bug 285020, bug 282310, bug 280595, bug 278880.

Reported using DrKonqi
Comment 1 Blagovest Zlatev 2011-11-29 15:15:45 UTC
I weren't able to reproduce the bug and I didn't find any duplicates.
Comment 2 underline 2011-11-29 15:26:44 UTC
This bug appears not very often. Only dring some time working intensively with remote machines.
Comment 3 Christoph Feck 2011-11-29 22:18:24 UTC
> I didn't find any duplicates.

Blagovest, the report even mentions the possible duplicates. By comparing the backtraces of the crashing thread, you will see that the duplicates mentioned are correct.
Comment 4 Myriam Schweingruber 2011-12-03 09:33:55 UTC

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