Bug 205192 - KRDC crash after disconnecting host
Summary: KRDC crash after disconnecting host
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-08-26 14:21 UTC by Johan Tornroos
Modified: 2009-08-26 15:34 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 Johan Tornroos 2009-08-26 14:21:20 UTC
Application that crashed: krdc
Version of the application: 4.3.00 (KDE 4.3.0) "release 158"
KDE Version: 4.3.00 (KDE 4.3.0) "release 152"
Qt Version: 4.5.2
Operating System: Linux 2.6.27.23-0.1-default x86_64

What I was doing when the application crashed:
Happens every time I log off and then press the disconnect button in fullscreen mode of a RDC session. I don't have any VNC server to try this with so I can't say if it is also happening with that protocol.

 -- Backtrace:
Application: KRDC (krdc), signal: Segmentation fault
[KCrash Handler]
#5  MainWindow::switchFullscreen (this=0x78d7a0) at /usr/src/debug/kdenetwork-4.3.0/krdc/mainwindow.cpp:526
#6  0x0000000000423b65 in MainWindow::disconnectHost (this=0x78d7a0) at /usr/src/debug/kdenetwork-4.3.0/krdc/mainwindow.cpp:614
#7  0x0000000000427de5 in MainWindow::qt_metacall (this=0x78d7a0, _c=QMetaObject::InvokeMetaMethod, _id=12885008, _a=0x7fff76561760) at /usr/src/debug/kdenetwork-4.3.0/build/krdc/mainwindow.moc:135
#8  0x00007f436b0116e2 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#9  0x00007f436bb70af7 in QAction::triggered(bool) () from /usr/lib64/libQtGui.so.4
#10 0x00007f436bb71f70 in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQtGui.so.4
#11 0x00007f436bed6cfa in ?? () from /usr/lib64/libQtGui.so.4
#12 0x00007f436bed6f95 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x00007f436bfa89ca in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007f436bbc7aed in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007f436bb76b0d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f436bb7f4fa in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f436c9f071b in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#18 0x00007f436affc94c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007f436bb7e748 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4
#20 0x00007f436bbe8519 in ?? () from /usr/lib64/libQtGui.so.4
#21 0x00007f436bbe7585 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#22 0x00007f436bc0e874 in ?? () from /usr/lib64/libQtGui.so.4
#23 0x00007f43673844fa in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f4367387bd0 in ?? () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f4367387d6c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f436b025d3f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f436bc0dfff in ?? () from /usr/lib64/libQtGui.so.4
#28 0x00007f436affb1d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f436affb5a4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00007f436affd894 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#31 0x0000000000428f6f in main (argc=3, argv=0x7fff765643d8) at /usr/src/debug/kdenetwork-4.3.0/krdc/main.cpp:101

Reported using DrKonqi
Comment 1 Dario Andres 2009-08-26 15:34:38 UTC
Merging with bug 200915. I wonder why the line numbers are different, may be Fedora introduced some patches ?
Thanks

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