Bug 167816

Summary: KRDC crashed when remote connection is closed.
Product: [Applications] krdc Reporter: Mehul Rajput <mehulrajput>
Component: generalAssignee: Urs Wolfer <uwolfer>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mehul Rajput 2008-07-31 07:46:23 UTC
Version:           4.1 (using KDE 4.1.0)
Installed from:    Ubuntu Packages
OS:                Linux

Application: KRDC (krdc), signal SIGSEGV
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb613b720 (LWP 13212)]
[New Thread 0xb4739b90 (LWP 13232)]
[KCrash handler]
#6  0xb6f08f4c in QFont::~QFont () from /usr/lib/libQtGui.so.4
#7  0xb6e46ee5 in ?? () from /usr/lib/libQtGui.so.4
#8  0xb6e4701c in QPainter::restore () from /usr/lib/libQtGui.so.4
#9  0xb6e4aaaa in ?? () from /usr/lib/libQtGui.so.4
#10 0xb6e4ac26 in QPainter::end () from /usr/lib/libQtGui.so.4
#11 0xb6e4b51b in QPainter::~QPainter () from /usr/lib/libQtGui.so.4
#12 0xb70f5a65 in QMainWindow::event () from /usr/lib/libQtGui.so.4
#13 0xb7c16d73 in KMainWindow::event (this=0x812bf38, ev=0xbff855c4)
    at /build/buildd/kde4libs-4.1.0/kdeui/widgets/kmainwindow.cpp:1013
#14 0xb7c525bc in KXmlGuiWindow::event (this=0x812bf38, ev=0xbff855c4)
    at /build/buildd/kde4libs-4.1.0/kdeui/xmlgui/kxmlguiwindow.cpp:122
#15 0xb6d4bc0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#16 0xb6d50898 in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb7b5eef3 in KApplication::notify (this=0xbff86018, receiver=0x812bf38, 
    event=0xbff855c4)
    at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311
#18 0xb76e26a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#19 0xb6da722e in ?? () from /usr/lib/libQtGui.so.4
#20 0xb6d9d84f in QWidgetPrivate::drawWidget () from /usr/lib/libQtGui.so.4
#21 0xb6efee9d in ?? () from /usr/lib/libQtGui.so.4
#22 0xb6eff627 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb6da318f in QWidget::event () from /usr/lib/libQtGui.so.4
#24 0xb70f57e5 in QMainWindow::event () from /usr/lib/libQtGui.so.4
#25 0xb7c16d73 in KMainWindow::event (this=0x812bf38, ev=0x83cf7b0)
    at /build/buildd/kde4libs-4.1.0/kdeui/widgets/kmainwindow.cpp:1013
#26 0xb7c525bc in KXmlGuiWindow::event (this=0x812bf38, ev=0x83cf7b0)
    at /build/buildd/kde4libs-4.1.0/kdeui/xmlgui/kxmlguiwindow.cpp:122
#27 0xb6d4bc0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#28 0xb6d50898 in QApplication::notify () from /usr/lib/libQtGui.so.4
#29 0xb7b5eef3 in KApplication::notify (this=0xbff86018, receiver=0x812bf38, 
    event=0x83cf7b0)
    at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311
#30 0xb76e26a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#31 0xb76e3a59 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#32 0xb76e3c7d in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#33 0xb770dbcf in ?? () from /usr/lib/libQtCore.so.4
#34 0xb6495dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#35 0xb6499193 in ?? () from /usr/lib/libglib-2.0.so.0
#36 0xb649974e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#37 0xb770df98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#38 0xb6ddf1b5 in ?? () from /usr/lib/libQtGui.so.4
#39 0xb76e192d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#40 0xb76e1abd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#41 0xb76e3d3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#42 0xb6d4b567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#43 0x0807847d in ?? ()
#44 0xb69e6450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#45 0x08058ac1 in _start ()
#0  0xb7fa5410 in __kernel_vsyscall ()
Comment 1 Urs Wolfer 2008-08-01 15:41:32 UTC
I think this is releated to bug 160728. Can you confirm? (Even though the backtrace looks a bit different...)
Comment 2 Urs Wolfer 2008-08-06 16:11:24 UTC

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