Application that crashed: plasma Version of the application: 0.3 KDE Version: 4.3.2 (KDE 4.3.2) Qt Version: 4.5.2 Operating System: Linux 2.6.31-14-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Did upgrade from Jaunty to Karmic, attempted to login via KDE and Plasma error reported. System not usable from KDE at this point. -- Backtrace: Application: Plasma Workspace (kdeinit4), signal: Segmentation fault [KCrash Handler] #6 0x077279e1 in ?? () from /usr/lib/libsolidcontrol.so.4 #7 0x0773126a in ?? () from /usr/lib/libsolidcontrol.so.4 #8 0x0772a81c in ?? () from /usr/lib/libsolidcontrol.so.4 #9 0x0772af7b in ?? () from /usr/lib/libsolidcontrol.so.4 #10 0x0772b100 in ?? () from /usr/lib/libsolidcontrol.so.4 #11 0x0772b189 in Solid::Control::NetworkManager::networkInterfaces() () from /usr/lib/libsolidcontrol.so.4 #12 0x04bbc5a8 in ?? () from /usr/lib/kde4/plasma_applet_networkmanagement.so #13 0x04bbf6c7 in ?? () from /usr/lib/kde4/plasma_applet_networkmanagement.so #14 0x04bc27d8 in QObject* KPluginFactory::createInstance<NetworkManagerApplet, QObject>(QWidget*, QObject*, QList<QVariant> const&) () from /usr/lib/kde4/plasma_applet_networkmanagement.so #15 0x00303175 in KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) () from /usr/lib/libkdecore.so.5 #16 0x04e4e7c8 in Plasma::Applet::load(QString const&, unsigned int, QList<QVariant> const&) () from /usr/lib/libplasma.so.3 #17 0x04e5e5b9 in ?? () from /usr/lib/libplasma.so.3 #18 0x04e61744 in Plasma::Containment::restoreContents(KConfigGroup&) () from /usr/lib/libplasma.so.3 #19 0x04e64087 in Plasma::Containment::restore(KConfigGroup&) () from /usr/lib/libplasma.so.3 #20 0x04e67bff in Plasma::Corona::loadLayout(QString const&) () from /usr/lib/libplasma.so.3 #21 0x04e688be in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib/libplasma.so.3 #22 0x07d51a1d in ?? () from /usr/lib/libkdeinit4_plasma.so #23 0x07d52035 in ?? () from /usr/lib/libkdeinit4_plasma.so #24 0x07d5556b in ?? () from /usr/lib/libkdeinit4_plasma.so #25 0x00ac3263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #26 0x00ac3ec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #27 0x00ac8387 in ?? () from /usr/lib/libQtCore.so.4 #28 0x00ac849c in ?? () from /usr/lib/libQtCore.so.4 #29 0x00abd3bf in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #30 0x061f9f54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #31 0x0620167c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #32 0x010edbfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #33 0x00aad6cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #34 0x00ada7ce in ?? () from /usr/lib/libQtCore.so.4 #35 0x00ad80e0 in ?? () from /usr/lib/libQtCore.so.4 #36 0x005d0e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #37 0x005d4720 in ?? () from /lib/libglib-2.0.so.0 #38 0x005d4853 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #39 0x00ad802c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #40 0x0629abe5 in ?? () from /usr/lib/libQtGui.so.4 #41 0x00aabc79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #42 0x00aac0ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #43 0x00aae53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #44 0x061f9dd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #45 0x07d3db56 in kdemain () from /usr/lib/libkdeinit4_plasma.so #46 0x0804dde1 in _start () This bug may be a duplicate of or related to bug 214754 Reported using DrKonqi
The network manager plasma widget was removed from Kubuntu 9.10 as it was unstable. You probably have it from a previous install. Try updating/removing the "plasma-widget-network-manager" package. Also, try using the standalone application "knetworkmanager4". Thanks *** This bug has been marked as a duplicate of bug 201425 ***