What I was doing when the application crashed: I had KRDC connected to remote pc, and then I minimized it, while I was working on something else. There was no warning, and no custom settings, I restarted twice and it crashed as soon as I reconnected to remote pc. Reproducible: Sometimes Steps to Reproduce: 1.Open KRDC 2. connect to remote machine 3. Minimize program Actual Results: It takes spells, it will crash every time, you leave it alone for an hour or so and then it will work for a short period of time, then it will crash, and will crash as soon as you connect and minimize, then you wait a while and it will work again. Expected Results: Don't expect it to crash
Created attachment 90596 [details] KDE crash report assistant report For some reason I couldn't get the crash report assistant to file the report, so I'm doing it manually
Application: krdc (4.14.1) KDE Platform Version: 4.14.1 Qt Version: 4.8.6 Operating System: Linux 3.16.0-28-generic x86_64 Distribution: Ubuntu 14.10 -- Information about the crash: - What I was doing when the application crashed: I had KRDC connected to remote pc, and then I minimized it, while I was working on something else. There was no warning, and no custom settings, I restarted twice and it crashed as soon as I reconnected to remote pc. - Unusual behavior I noticed: None - Custom settings of the application: None The crash does not seem to be reproducible. -- Backtrace: Application: KRDC (krdc), signal: Floating point exception Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7c268a78c0 (LWP 2933))] Thread 3 (Thread 0x7f7c0f8ef700 (LWP 2945)): #0 0x00007f7c227a03dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f7c204b9ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f7c204b9ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f7c249c904e in QEventDispatcherGlib::processEvents (this=0x7f7c000030a0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x00007f7c2499a4f1 in QEventLoop::processEvents (this=this@entry=0x7f7c0f8eece0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f7c2499a805 in QEventLoop::exec (this=this@entry=0x7f7c0f8eece0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f7c24898c39 in QThread::exec (this=this@entry=0x26e6c90) at thread/qthread.cpp:538 #7 0x00007f7c2497c033 in QInotifyFileSystemWatcherEngine::run (this=0x26e6c90) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x00007f7c2489b39f in QThreadPrivate::start (arg=0x26e6c90) at thread/qthread_unix.cpp:349 #9 0x00007f7c20bb00a5 in start_thread (arg=0x7f7c0f8ef700) at pthread_create.c:309 #10 0x00007f7c227aa88d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f7c10557700 (LWP 2947)): [KCrash Handler] #5 HandleRFBServerMessage (client=0x1) at rfbproto.c:1907 #6 0x00007f7c129fe3d4 in VncClientThread::run (this=0x278a400) at ../../vnc/vncclientthread.cpp:490 #7 0x00007f7c2489b39f in QThreadPrivate::start (arg=0x278a400) at thread/qthread_unix.cpp:349 #8 0x00007f7c20bb00a5 in start_thread (arg=0x7f7c10557700) at pthread_create.c:309 #9 0x00007f7c227aa88d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f7c268a78c0 (LWP 2933)): #0 0x00007f7c2279c0ed in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f7c204fced0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f7c204b996c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f7c204b9e83 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f7c204b9ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f7c249c904e in QEventDispatcherGlib::processEvents (this=0x2091c90, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x00007f7c234d34e6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #7 0x00007f7c2499a4f1 in QEventLoop::processEvents (this=this@entry=0x7fff0bf4e340, flags=...) at kernel/qeventloop.cpp:149 #8 0x00007f7c2499a805 in QEventLoop::exec (this=this@entry=0x7fff0bf4e340, flags=...) at kernel/qeventloop.cpp:204 #9 0x00007f7c2499ff67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #10 0x00007f7c2342e4dc in QApplication::exec () at kernel/qapplication.cpp:3828 #11 0x00000000004156f0 in main (argc=<optimized out>, argv=<optimized out>) at ../main.cpp:104 The reporter indicates this bug may be a duplicate of or related to bug 211515. Possible duplicates by query: bug 334283. Report to https://bugs.kde.org/
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!
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!