Bug 309368

Summary: KRDC crash after network hiccup MainWindow::openFromRemoteDesktopsModel
Product: [Applications] krdc Reporter: Ralph deGennaro (SSCPS) <rdegennaro>
Component: generalAssignee: Urs Wolfer <uwolfer>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andrew.crouthamel, jim.odayinst, lameventanas
Priority: NOR    
Version First Reported In: 4.8.5   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Ralph deGennaro (SSCPS) 2012-11-01 13:35:50 UTC 
Application: krdc (4.8.5 (4.8.5))
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-32-generic x86_64
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
I left KRDC running over night with 2 rdp sessions (to Win2008R2) and 1 VNC session (Mac10.8).  The session tabs were still being shown, but I could not click anything inside any tab.  I closed them all, and started the sessions again.  Its not always the first session, but KRDC usually crashes within first 3 or so.  

Once I restart KRDC its fine until there is a network "hiccup".  Randomly there will be network issues where even pinging the server won't work.  The session usually freezes or nothing happens when clicking or typing in the tab.  Other sessions may stay working.  But as soon as I try to reconnect to one of the hung sessions, KRDC will crash.

-- Backtrace:
Application: KRDC (krdc), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f62014c5780 (LWP 10816))]

Thread 2 (Thread 0x7f61ebb29700 (LWP 10817)):
#0  begin (this=0x7f61e4002860) at ../../include/QtCore/../../src/corelib/tools/qlist.h:101
#1  constBegin (this=0x7f61e4002860) at ../../include/QtCore/../../src/corelib/tools/qlist.h:269
#2  QTimerInfoList::timerWait (this=0x7f61e4002860, tm=...) at kernel/qeventdispatcher_unix.cpp:455
#3  0x00007f61fe81f97c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f61ebb28c6c) at kernel/qeventdispatcher_glib.cpp:136
#4  0x00007f61fe81fa25 in timerSourcePrepare (source=<optimized out>, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#5  0x00007f61fac20846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f61fac20f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x00007f61fac21164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x00007f61fe820426 in QEventDispatcherGlib::processEvents (this=0x7f61e40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#9  0x00007f61fe7efc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#10 0x00007f61fe7efed7 in QEventLoop::exec (this=0x7f61ebb28dd0, flags=...) at kernel/qeventloop.cpp:204
#11 0x00007f61fe6eefa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#12 0x00007f61fe7cf9ff in QInotifyFileSystemWatcherEngine::run (this=0x2d4a120) at io/qfilesystemwatcher_inotify.cpp:248
#13 0x00007f61fe6f1fcb in QThreadPrivate::start (arg=0x2d4a120) at thread/qthread_unix.cpp:298
#14 0x00007f61fb0ede9a in start_thread (arg=0x7f61ebb29700) at pthread_create.c:308
#15 0x00007f61fe0aacbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#16 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f62014c5780 (LWP 10816)):
[KCrash Handler]
#6  ref (this=0x60) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:121
#7  QString (other=..., this=0x7fff0d1e5608) at ../../include/QtCore/../../src/corelib/tools/qstring.h:726
#8  QUrlPrivate::QUrlPrivate (this=0x7fff0d1e5600, copy=...) at io/qurl.cpp:3451
#9  0x00007f61fe7a8433 in QUrlPrivate::normalized (this=0x2e02488) at io/qurl.cpp:4054
#10 0x00007f61fe7a90b0 in QUrl::operator== (this=0x7fff0d1e5790, url=...) at io/qurl.cpp:6040
#11 0x0000000000427024 in MainWindow::openFromRemoteDesktopsModel (this=0x27939c0, index=...) at ../../krdc/mainwindow.cpp:388
#12 0x000000000042b4d6 in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=0x27939c0, _c=<optimized out>) at ./mainwindow.moc:142
#13 MainWindow::qt_static_metacall (_o=0x27939c0, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./mainwindow.moc:104
#14 0x00007f61fe805281 in QMetaObject::activate (sender=0x2b3bfb0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff0d1e5960) at kernel/qobject.cpp:3547
#15 0x00007f61ff710ad5 in QAbstractItemView::doubleClicked (this=<optimized out>, _t1=...) at .moc/release-shared/moc_qabstractitemview.cpp:355
#16 0x00007f61ff710c3e in QAbstractItemView::mouseDoubleClickEvent (this=0x2b3bfb0, event=0x7fff0d1e6640) at itemviews/qabstractitemview.cpp:1846
#17 0x00007f61ff23b15e in QWidget::event (this=0x2b3bfb0, event=0x7fff0d1e6640) at kernel/qwidget.cpp:8366
#18 0x00007f61ff5fb3b6 in QFrame::event (this=0x2b3bfb0, e=0x7fff0d1e6640) at widgets/qframe.cpp:557
#19 0x00007f61ff70f89b in QAbstractItemView::viewportEvent (this=0x2b3bfb0, event=0x7fff0d1e6640) at itemviews/qabstractitemview.cpp:1644
#20 0x00007f61fe7f1028 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x2b42330, event=0x7fff0d1e6640) at kernel/qcoreapplication.cpp:986
#21 0x00007f61ff1ea85f in notify_helper (e=0x7fff0d1e6640, receiver=0x2b42330, this=0x2601480) at kernel/qapplication.cpp:4555
#22 QApplicationPrivate::notify_helper (this=0x2601480, receiver=0x2b42330, e=0x7fff0d1e6640) at kernel/qapplication.cpp:4531
#23 0x00007f61ff1f00bf in QApplication::notify (this=<optimized out>, receiver=0x2b42330, e=0x7fff0d1e6640) at kernel/qapplication.cpp:4102
#24 0x00007f61fff243f6 in KApplication::notify (this=0x7fff0d1e7320, receiver=0x2b42330, event=0x7fff0d1e6640) at ../../kdeui/kernel/kapplication.cpp:311
#25 0x00007f61fe7f0e9c in QCoreApplication::notifyInternal (this=0x7fff0d1e7320, receiver=0x2b42330, event=0x7fff0d1e6640) at kernel/qcoreapplication.cpp:876
#26 0x00007f61ff1eb862 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#27 QApplicationPrivate::sendMouseEvent (receiver=0x2b42330, event=0x7fff0d1e6640, alienWidget=0x0, nativeWidget=0x2b42330, buttonDown=0x0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3170
#28 0x00007f61ff26abf5 in QETWidget::translateMouseEvent (this=0x2b42330, event=<optimized out>) at kernel/qapplication_x11.cpp:4617
#29 0x00007f61ff269bae in QApplication::x11ProcessEvent (this=0x7fff0d1e7320, event=0x7fff0d1e6f10) at kernel/qapplication_x11.cpp:3732
#30 0x00007f61ff2930d2 in x11EventSourceDispatch (s=0x25fc890, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#31 0x00007f61fac20d53 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f61fac210a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007f61fac21164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x00007f61fe8203bf in QEventDispatcherGlib::processEvents (this=0x25d9e00, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#35 0x00007f61ff292d5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0x00007f61fe7efc82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#37 0x00007f61fe7efed7 in QEventLoop::exec (this=0x7fff0d1e72b0, flags=...) at kernel/qeventloop.cpp:204
#38 0x00007f61fe7f4f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#39 0x0000000000415648 in main (argc=3, argv=0x7fff0d1e78e8) at ../../krdc/main.cpp:104

Reported using DrKonqi
Comment 1 Urs Wolfer 2012-11-03 13:04:47 UTC 
Do RDP and VNC sessions crash KRDC? Or only VNC?
Comment 2 Ralph deGennaro (SSCPS) 2012-11-03 19:38:55 UTC 
This has happened in the past before we even had the Mac server.  So definitely with RDP sessions.  But I can't say not with VNC.  I can say both RDP & VNC sessions freeze and don't respond.
Comment 3 Urs Wolfer 2013-08-22 05:47:21 UTC 
*** Bug 323877 has been marked as a duplicate of this bug. ***
Comment 4 alancio 2014-03-31 02:02:40 UTC 
This happens to me all the time.

I have 2 sessions:

1. RDP to a VM in local machine: reliable network connection
2. VNC to a remote machine via VNC: unreliable network connection

The second session has a network problem, causing KRDC to crash.
This leaves my first session with an orphan xfreerdp window.  I have to kill xfreerdp before starting KRDC again.

Very annoying.
Comment 5 Andrew Crouthamel 2018-10-31 03:59:41 UTC 
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!
Comment 6 alancio 2018-10-31 05:13:44 UTC 
Tomorrow will be the 6th year anniversary for this bug, and it went unanswered.

Normally people expect some kind of feedback for their bug reports, otherwise they don't bother anymore.

This is like sending a bug report for Windows 3.11 and getting feedback from Microsoft 6 years later, asking to check it again in Windows XP.
Comment 7 Andrew Crouthamel 2018-10-31 14:51:41 UTC 
(In reply to alancio from comment #6)
> Tomorrow will be the 6th year anniversary for this bug, and it went
> unanswered.
> 
> Normally people expect some kind of feedback for their bug reports,
> otherwise they don't bother anymore.
> 
> This is like sending a bug report for Windows 3.11 and getting feedback from
> Microsoft 6 years later, asking to check it again in Windows XP.

Bug triaging has very few volunteers. I'm trying to revisit a lot of the old bugs and see what is still relevant, to hopefully prevent that issue in the future.
Comment 8 Bug Janitor Service 2018-11-15 10:39:07 UTC 
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!
Comment 9 Bug Janitor Service 2018-11-30 03:51:54 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!