Version: (using KDE KDE 3.5.3) Installed from: SuSE RPMs Compiler: gcc 4.1.0 under SUSE 10.1 64-bit OS: Linux Krfb crashes after a short time after a connection is established from TightVNC from Windows 2000. Here's the backtrace: System configuration startup check disabled. Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47421826160704 (LWP 26878)] [New Thread 1098918208 (LWP 26881)] [New Thread 1090525504 (LWP 26880)] 0x00002b213f231202 in __select_nocancel () from /lib64/libc.so.6 #0 0x00002b213f231202 in __select_nocancel () from /lib64/libc.so.6 #1 0x00002b213eb7bf40 in XProcessInternalConnection () from /usr/X11R6/lib64/libX11.so.6 #2 0x00002b213eb7c2f9 in _XRead () from /usr/X11R6/lib64/libX11.so.6 #3 0x00002b213eb7ce21 in _XReply () from /usr/X11R6/lib64/libX11.so.6 #4 0x00002b213ea33ec2 in XShmGetImage () from /usr/X11R6/lib64/libXext.so.6 #5 0x0000000000411507 in XUpdateScanner::testScanline () #6 0x0000000000411bbd in XUpdateScanner::searchUpdates () #7 0x0000000000415ca7 in RFBController::idleSlot () #8 0x0000000000415e8a in RFBController::qt_invoke () #9 0x00002b213e433a8c in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #10 0x00002b213e4347a3 in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #11 0x00002b213e452e95 in QTimer::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #12 0x00002b213e3dca95 in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #13 0x00002b213e3dd6c7 in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x00002b213dc9cb08 in KApplication::notify () from /opt/kde3/lib64/libkdecore.so.4 #15 0x00002b213e3d3005 in QEventLoop::activateTimers () from /usr/lib/qt3/lib64/libqt-mt.so.3 #16 0x00002b213e3934ed in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #17 0x00002b213e3f17a1 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #18 0x00002b213e3f164a in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #19 0x000000000041949c in main ()
FYI: KRFB is currently unmaintained and therefore the future of the program is unclear.
It would be very helpful if you could provide a backtrace from a debug-enabled KDE 3.5.4 as well as the debug output from KRFB (usually found in ~/.xsession-errors)
Created attachment 17332 [details] xsession-errors file after Krfb crash This is the .xsession-errors file after Krfb crashed.
Hi! I experience the same bug when I access my OpenSuse 10.1 box running KDE 3.5.1 from either a Windows XP SP2 box running vncviewer 4.1 or Ubuntu 6.x box running xvncviewer. They both connect. The mouse does not respond. It then crashes. The trace is below. I also attached the .xsession-errors file. I don't know how to set up the the debug flag, which I presume is an option at compilation. Recompiling is not something I am comfortable to do with this system. GMercier gamercier@yahoo.com ---- trace ---- System configuration startup check disabled. (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231837520 (LWP 21140)] [New Thread -1260393568 (LWP 21143)] [New Thread -1252000864 (LWP 21142)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall () #0 0xffffe410 in __kernel_vsyscall () #1 0xb6ebc2db in __read_nocancel () from /lib/libpthread.so.0 #2 0xb6f1687e in _X11TransGetMyAddr () from /usr/X11R6/lib/libX11.so.6 #3 0xb6f1634f in _X11TransRead () from /usr/X11R6/lib/libX11.so.6 #4 0xb6efa339 in _XRead () from /usr/X11R6/lib/libX11.so.6 #5 0xb6efae94 in _XReply () from /usr/X11R6/lib/libX11.so.6 #6 0xb6ef0340 in XQueryPointer () from /usr/X11R6/lib/libX11.so.6 #7 0xb7186b2b in QCursor::pos () from /usr/lib/qt3/lib/libqt-mt.so.3 #8 0x0805a3b9 in ?? () #9 0xbfb52520 in ?? () #10 0x000002ab in ?? () #11 0x000001f6 in ?? () #12 0x082610b0 in ?? () #13 0x000003c0 in ?? () #14 0xb5608f38 in ?? () #15 0x000002ab in ?? () #16 0x000001f6 in ?? () #17 0x000002ab in ?? () #18 0x000001f6 in ?? () #19 0x08081d68 in typeinfo for QGList () #20 0xb7946901 in ?? () from /opt/kde3/lib/libkdecore.so.4 #21 0x00000000 in ?? ()
I can confirm this. A fresh install of kubuntu 6.06.1 (kde 3.5.2), and a tightvnc "vncviewer" app running on windows xp. When approximately 1/2 the screen is received, the connection drops and on the host the KDE Crash Handler appears.
*** This bug has been confirmed by popular vote. ***
Duplicates #124529
I am totally new to kubuntu and liunux in general but I am experiencing exactly the same problem....anybody knows how to fix it? if I use different VNC programs bot on the win2k and linux machine can I avoid the problem? Thanks Michele
Duplicate, as per comment #7 *** This bug has been marked as a duplicate of 124529 ***