Jaunty: KDE4: Network manager widget kills plasma

[Edmundo]

I'm using KDE 4.3 but it happened in 4.2 as well.

Doesn't matter if I try to put it on the desktop or on the tray. Plasma will always crash.

Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 0 (LWP 6543)]

Thread 2 (Thread 0x7f8c393a8950 (LWP 6544)):
#0 0x00007f8c542da2e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1 0x00007f8c583ddd19 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#2 0x00007f8c5726781c in ?? () from /usr/lib/libQtNetwork.so.4
#3 0x00007f8c583dcd35 in ?? () from /usr/lib/libQtCore.so.4
#4 0x00007f8c542d63ba in start_thread () from /lib/libpthread.so.0
#5 0x00007f8c54ebafcd in clone () from /lib/libc.so.6
#6 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8c589a1750 (LWP 6543)):
[KCrash Handler]
#5 0x00007f8c57f9b7b4 in KConfigGroup::config () from /usr/lib/libkdecore.so.5
#6 0x00007f8c4fdeda18 in Plasma::Applet::saveState () from /usr/lib/libplasma.so.3
#7 0x00007f8c4fe03679 in Plasma::Containment::addApplet () from /usr/lib/libplasma.so.3
#8 0x00007f8c4fe03915 in ?? () from /usr/lib/libplasma.so.3
#9 0x00007f8c4c42813f in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#10 0x00007f8c4c42cdc8 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#11 0x00007f8c584dbea2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0x00007f8c56b18085 in KDialog::slotButtonClicked () from /usr/lib/libkdeui.so.5
#13 0x00007f8c56b1a29d in KDialog::qt_metacall () from /usr/lib/libkdeui.so.5
#14 0x00007f8c4c42c70d in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#15 0x00007f8c584dbea2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x00007f8c584dec3e in QSignalMapper::mapped () from /usr/lib/libQtCore.so.4
#17 0x00007f8c584df4e0 in QSignalMapper::map () from /usr/lib/libQtCore.so.4
#18 0x00007f8c584e00d0 in QSignalMapper::qt_metacall () from /usr/lib/libQtCore.so.4
#19 0x00007f8c584dbea2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#20 0x00007f8c560b3e27 in QAbstractButton::clicked () from /usr/lib/libQtGui.so.4
#21 0x00007f8c55e0dc6b in ?? () from /usr/lib/libQtGui.so.4
#22 0x00007f8c55e0f8c2 in ?? () from /usr/lib/libQtGui.so.4
#23 0x00007f8c55e0fb15 in QAbstractButton::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#24 0x00007f8c55ae30bf in QWidget::event () from /usr/lib/libQtGui.so.4
#25 0x00007f8c55a91f4d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#26 0x00007f8c55a9a8ea in QApplication::notify () from /usr/lib/libQtGui.so.4
#27 0x00007f8c56ba471b in KApplication::notify () from /usr/lib/libkdeui.so.5
#28 0x00007f8c584c66ac in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#29 0x00007f8c55a99b38 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#30 0x00007f8c55b03b19 in ?? () from /usr/lib/libQtGui.so.4
#31 0x00007f8c55b02b53 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#32 0x00007f8c55b2b454 in ?? () from /usr/lib/libQtGui.so.4
#33 0x00007f8c5452520a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0x00007f8c545288e0 in ?? () from /usr/lib/libglib-2.0.so.0
#35 0x00007f8c54528a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0x00007f8c584efa8f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#37 0x00007f8c55b2abdf in ?? () from /usr/lib/libQtGui.so.4
#38 0x00007f8c584c4f42 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#39 0x00007f8c584c5314 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#40 0x00007f8c584c75e4 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#41 0x00007f8c4c40a1eb in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#42 0x0000000000407215 in _start ()

[Edmundo (eantoranz)]

Oh, forgot to say that it's a 64-bit box.

[Edmundo (eantoranz)]

I think I found the reason for the error.

I was missing the plasma-widget-network-manager package. But that leads to another problem: Why was the widget listed as available to be added if the package was missing?

[Jonathan Thomas (echidnaman)]

My guess would be a stale cache. (Or, in technical terms, the ksycoca cache hadn't been updated after the widget was removed)
But since this was a one-off configuration glitch I'm afraid there's not much we can do. Thanks for the report, though.