Application: knetworkmanager (v0.9) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: After configuring a PPTP-VPN connection, KNetworkManager crashes when told to connect to it. The crash can be reproduced every time. -- Backtrace: Application: KNetworkManager (knetworkmanager), signal: Segmentation fault [KCrash Handler] #6 QAction::isSeparator (this=0x9533638) at kernel/qaction.cpp:793 #7 0x01478668 in QMenu::mouseMoveEvent (this=0x9533638, e=0xbf87c3c0) at widgets/qmenu.cpp:2810 #8 0x0103069a in QWidget::event (this=0x95331c8, event=0xbf87c3c0) at kernel/qwidget.cpp:7983 #9 0x0147a0cc in QMenu::event (this=0x95331c8, e=0xbf87c3c0) at widgets/qmenu.cpp:2414 #10 0x019e7f3f in ?? () from /usr/lib/kde4/plugins/styles/oxygen.so #11 0x06fedcda in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x9470608, receiver=0x95331c8, event=0xbf87c3c0) at kernel/qcoreapplication.cpp:819 #12 0x00fd24b9 in QApplicationPrivate::notify_helper (this=0x9470608, receiver=0x95331c8, e=0xbf87c3c0) at kernel/qapplication.cpp:4296 #13 0x00fd99f7 in QApplication::notify (this=0xbf87e0f0, receiver=0x95331c8, e=0xbf87c3c0) at kernel/qapplication.cpp:3865 #14 0x00947f2a in KApplication::notify (this=0xbf87e0f0, receiver=0x95331c8, event=0xbf87c3c0) at ../../kdeui/kernel/kapplication.cpp:302 #15 0x06feea3b in QCoreApplication::notifyInternal (this=0xbf87e0f0, receiver=0x95331c8, event=0xbf87c3c0) at kernel/qcoreapplication.cpp:704 #16 0x00fd8952 in QCoreApplication::sendEvent (receiver=0x95331c8, event=0xbf87c3c0, alienWidget=0x0, nativeWidget=0x95331c8, buttonDown=0x1916058, lastMouseReceiver=..., spontaneous=true) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #17 QApplicationPrivate::sendMouseEvent (receiver=0x95331c8, event=0xbf87c3c0, alienWidget=0x0, nativeWidget=0x95331c8, buttonDown=0x1916058, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:2965 #18 0x00fd8e9a in QApplicationPrivate::sendSyntheticEnterLeave (this=0x9470608, widget=0x952f418) at kernel/qapplication.cpp:3051 #19 0x0102f236 in QWidgetPrivate::hideChildren (this=0x95016b8, spontaneous=false) at kernel/qwidget.cpp:7536 #20 0x0102f3ea in QWidgetPrivate::hide_helper (this=0x95016b8) at kernel/qwidget.cpp:7283 #21 0x01038b40 in QWidget::setVisible (this=0x9530638, visible=false) at kernel/qwidget.cpp:7455 #22 0x0103d0d0 in QWidget::hide (this=0x952e8f8, widget=0x9530638) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:489 #23 QWidgetAction::releaseWidget (this=0x952e8f8, widget=0x9530638) at kernel/qwidgetaction.cpp:206 #24 0x01474212 in QMenu::actionEvent (this=0x95331c8, e=0xbf87cba8) at widgets/qmenu.cpp:2883 #25 0x0103097d in QWidget::event (this=0x95331c8, event=0xbf87cba8) at kernel/qwidget.cpp:8373 #26 0x0147a0cc in QMenu::event (this=0x95331c8, e=0xbf87cba8) at widgets/qmenu.cpp:2414 #27 0x00fd24dc in QApplicationPrivate::notify_helper (this=0x9470608, receiver=0x95331c8, e=0xbf87cba8) at kernel/qapplication.cpp:4300 #28 0x00fd90f9 in QApplication::notify (this=0xbf87e0f0, receiver=0x95331c8, e=0xbf87cba8) at kernel/qapplication.cpp:4265 #29 0x00947f2a in KApplication::notify (this=0xbf87e0f0, receiver=0x95331c8, event=0xbf87cba8) at ../../kdeui/kernel/kapplication.cpp:302 #30 0x06feea3b in QCoreApplication::notifyInternal (this=0xbf87e0f0, receiver=0x95331c8, event=0xbf87cba8) at kernel/qcoreapplication.cpp:704 #31 0x010259a2 in QCoreApplication::sendEvent (this=0x95331c8, action=0x952e8f8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #32 QWidget::removeAction (this=0x95331c8, action=0x952e8f8) at kernel/qwidget.cpp:3018 #33 0x080565ef in _start () This bug may be a duplicate of or related to bug 237649, bug 237416. Possible duplicates by query: bug 237935, bug 237649, bug 237594, bug 237416, bug 237386. Reported using DrKonqi
Gawd, why didn't I fix this before Kubuntu released? Now even after I fix it there will be a ton of bug reports until they package the fix. *** This bug has been marked as a duplicate of bug 215080 ***