Version: (using KDE 4.3.0) Installed from: RedHat RPMs I have A KDE at work that I connect remotely from home using in VNC. Sometime my work computer crashes and gives me THE APPLICATION DESKTOP SHARING (krfb) crashed and caused the signal 11 (SIGSEGV) (no debugging symbols found) Using host libthread_db library "/lib/tls/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) (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 -1208113472 (LWP 4986)] [New Thread -1239422032 (LWP 4989)] [New Thread -1228932176 (LWP 4988)] (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) 0x005bb7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #0 0x005bb7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2 #1 0x00694411 in ___newselect_nocancel () from /lib/tls/libc.so.6 #2 0x007600c2 in _XEnq () from /usr/X11R6/lib/libX11.so.6 #3 0x0076049e in _XRead () from /usr/X11R6/lib/libX11.so.6 #4 0x007615fb in _XReply () from /usr/X11R6/lib/libX11.so.6 #5 0x00823bf1 in XShmGetImage () from /usr/X11R6/lib/libXext.so.6 #6 0x080586a6 in QMemArray<char>::detach () #7 0x0805894c in QMemArray<char>::detach () #8 0x080563f0 in ?? () #9 0x09983d28 in ?? () #10 0xbff61500 in ?? () #11 0x00000184 in ?? () #12 0x099864a8 in ?? () #13 0x00000484 in ?? () #14 0x7f43d0e8 in ?? () #15 0x006356f0 in _int_free () from /lib/tls/libc.so.6 #16 0x08056567 in ?? () #17 0xbff61d40 in ?? () #18 0x006f0d30 in __libc_ptyname1 () from /lib/tls/libc.so.6 #19 0x0987a830 in ?? () #20 0x06f44f90 in ?? () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #21 0x09982788 in ?? () #22 0xbff615f0 in ?? () #23 0xbff615a8 in ?? () #24 0x06b11450 in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #25 0x06b11450 in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #26 0x06b11b2a in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #27 0x06e4429d in QTimer::timeout () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #28 0x06b3115c in QTimer::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #29 0x06ab28f9 in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #30 0x06ab2a8a in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #31 0x001b93f8 in KApplication::notify () from /usr/lib/libkdecore.so.4 #32 0x06aa6c6e in QEventLoop::activateTimers () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #33 0x06a62c2e in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #34 0x06ac7f25 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #35 0x06ac7e7e in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #36 0x06ab1afb in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #37 0x0805942b in QMemArray<char>::detach () #38 0x005e8e23 in __libc_start_main () from /lib/tls/libc.so.6 #39 0x080534f1 in ?? ()
Seems like the application crashing is from KDE3. (but you mentioned to be using KDE4.3) If you can reproduce the crash at will(or if you experience this regularly), may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks
The bug report here doesn't contain enough information to really do anything with. Please can you follow Dario's suggestion in Comment #1 and provide us with a new backtrace (which will hopefully have enough information to find the crash).
No response for over a month. Please reopen this report if you can provide information as requested in Comment #2. Thanks.