Application that crashed: knetworkmanager Version of the application: v0.9 KDE Version: 4.3.1 (KDE 4.3.1) "release 5" Qt Version: 4.5.3 Operating System: Linux 2.6.32-rc5-wl x86_64 Distribution: "openSUSE 11.2 RC 1 (x86_64)" What I was doing when the application crashed: My wireless connection went offline. While trying to reconnect, kNMcrashed. -- Backtrace: Application: KNetworkManager (knetworkmanager), signal: Segmentation fault [KCrash Handler] #5 0x000000000082edb0 in ?? () #6 0x00007f49409cefcc in WirelessSecuritySettingWidget::writeConfig() () from /usr/lib64/libknmui.so.4 #7 0x00007f49409e59d2 in ConnectionSecretsJob::dialogAccepted() () from /usr/lib64/libknmui.so.4 #8 0x00007f49409b5144 in ConnectionSecretsJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libknmui.so.4 #9 0x00007f4943a48f7c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #10 0x00007f49457b1288 in KDialog::slotButtonClicked(int) () from /usr/lib64/libkdeui.so.5 #11 0x00007f49457b3499 in KDialog::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdeui.so.5 #12 0x00007f4943a48f7c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #13 0x00007f4943a4baae in QSignalMapper::mapped(int) () from /usr/lib64/libQtCore.so.4 #14 0x00007f4943a4cca0 in QSignalMapper::map(QObject*) () from /usr/lib64/libQtCore.so.4 #15 0x00007f4943a4cf10 in QSignalMapper::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtCore.so.4 #16 0x00007f4943a48f7c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #17 0x00007f4944715e07 in QAbstractButton::clicked(bool) () from /usr/lib64/libQtGui.so.4 #18 0x00007f4944477c0b in ?? () from /usr/lib64/libQtGui.so.4 #19 0x00007f494447981b in ?? () from /usr/lib64/libQtGui.so.4 #20 0x00007f4944479a65 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007f494417fcf0 in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #22 0x00007f49441312ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #23 0x00007f49441383c1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #24 0x00007f494583c8d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #25 0x00007f4943a33d9c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #26 0x00007f4944137c90 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4 #27 0x00007f494419dcfe in ?? () from /usr/lib64/libQtGui.so.4 #28 0x00007f494419cd9a in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #29 0x00007f49441c4b6c in ?? () from /usr/lib64/libQtGui.so.4 #30 0x00007f493fe3bdde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #31 0x00007f493fe3f7a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #32 0x00007f493fe3f8d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #33 0x00007f4943a5c356 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007f49441c431e in ?? () from /usr/lib64/libQtGui.so.4 #35 0x00007f4943a326d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #36 0x00007f4943a32aa4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #37 0x00007f4943a34c59 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #38 0x000000000040d13f in _start () Reported using DrKonqi
Please install debuginfo and repeat the crash.
@Will: should I assume this is bug 210785? Regards
I have now added debuginfo and will supply needed info if/when I get another crash. I had been running this version of kNM for about one week without problem.
Yes, it's 210785. I *think* this is something broken in the revision of KNM that Kubuntu shipped but that I serendipitously fixed before openSUSE 11.2 as Kubuntuists are reporting it like crazy but not SUSErs. *** This bug has been marked as a duplicate of bug 210785 ***