Bug 201234 - when close KRDC this windows appear
Summary: when close KRDC this windows appear
Status: RESOLVED DUPLICATE of bug 200915
Alias: None
Product: krdc
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-23 15:41 UTC by bruno
Modified: 2009-08-04 21:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bruno 2009-07-23 15:41:56 UTC
Application that crashed: krdc
Version of the application: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2))
KDE Version: 4.2.98 (KDE 4.2.98 (KDE 4.3 RC3))
Qt Version: 4.5.2
Operating System: Linux 2.6.30.2-desktop-1mnb i686
Distribution: "Mandriva Linux 2009.1"

What I was doing when the application crashed:
I was in a server win 2000 and when I close the window I had a crash bug appearing
also the look and the appearance is a lot nicer , thank you ,but when I quit my login session it is ther it crash ,I was not able to close the window of the program

 -- Backtrace:
Application: KRDC (krdc), signal: Aborted
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb679e9e1 in raise () from /lib/i686/libc.so.6
#8  0xb67a0374 in abort () from /lib/i686/libc.so.6
#9  0xb6a0aad4 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb6a0abd8 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb6a0ac8d in qt_assert_x () from /usr/lib/libQtCore.so.4
#12 0x0805ffd7 in ?? ()
#13 0x08064faf in ?? ()
#14 0x080668db in ?? ()
#15 0xb6b22f29 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb6b23411 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb6f6b9a5 in QAction::triggered () from /usr/lib/libQtGui.so.4
#18 0xb6f6cfd2 in QAction::activate () from /usr/lib/libQtGui.so.4
#19 0xb7427fa0 in QToolButton::nextCheckState () from /usr/lib/libQtGui.so.4
#20 0xb733c4e7 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb733c7c6 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#22 0xb74284ad in QToolButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#23 0xb6fc99ae in QWidget::event () from /usr/lib/libQtGui.so.4
#24 0xb733a650 in QAbstractButton::event () from /usr/lib/libQtGui.so.4
#25 0xb742af7c in QToolButton::event () from /usr/lib/libQtGui.so.4
#26 0xb6f723ac in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#27 0xb6f7a7c3 in QApplication::notify () from /usr/lib/libQtGui.so.4
#28 0xb79c9e88 in KApplication::notify () from /usr/lib/libkdeui.so.5
#29 0xb6b0c79e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#30 0xb6f797ec in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#31 0xb6feb21a in ?? () from /usr/lib/libQtGui.so.4
#32 0xb6fea70b in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#33 0xb7015b28 in ?? () from /usr/lib/libQtGui.so.4
#34 0xb607aed2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#35 0xb607e888 in ?? () from /usr/lib/libglib-2.0.so.0
#36 0xb607e9ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#37 0xb6b389d8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#38 0xb701525a in ?? () from /usr/lib/libQtGui.so.4
#39 0xb6b0ad8d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#40 0xb6b0b1d9 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#41 0xb6b0d6c0 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#42 0xb6f72214 in QApplication::exec () from /usr/lib/libQtGui.so.4
#43 0x0806b857 in ?? ()
#44 0xb678ba36 in __libc_start_main () from /lib/i686/libc.so.6
#45 0x08055891 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-07-24 02:57:02 UTC
If you can reproduce the crash at will, may you install the "kdelibs5-debuginfo" and "kdenetwork4-debuginfo" packages and then paste here a complete backtrace ? Thanks
Comment 2 Pino Toscano 2009-08-04 00:16:44 UTC
Possible dupe of #200915?
Comment 3 Urs Wolfer 2009-08-04 21:01:04 UTC

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