plasma-desktop crashed with SIGSEGV in data()

[Max]

after reboot.
plasma-desktop just crash

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plasma-desktop 4:4.7.95-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic-pae 3.2.0-rc7
Uname: Linux 3.2.0-7-generic-pae i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Fri Dec 30 21:54:41 2011
ExecutablePath: /usr/bin/plasma-desktop
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111230)
ProcCmdline: /usr/bin/plasma-desktop --nocrashhandler
ProcEnviron:
 LANGUAGE=zh_TW:zh
 LANG=zh_TW.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb59a0bde <_ZNK7QAction4textEv+30>: mov 0x4(%eax),%edx
 PC (0xb59a0bde) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde-workspace
StacktraceTop:
 QAction::text() const () from /usr/lib/i386-linux-gnu/libQtGui.so.4
 ?? () from /usr/lib/kde4/plasma_applet_folderview.so
 ?? () from /usr/lib/libplasma.so.3
 Plasma::Applet::showConfigurationInterface() () from /usr/lib/libplasma.so.3
 Plasma::Containment::showConfigurationInterface() () from /usr/lib/libplasma.so.3
Title: plasma-desktop crashed with SIGSEGV in QAction::text()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 data (this=0x4) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
 qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2343
 d_func (this=0x0) at kernel/qaction.h:67
 QAction::text (this=0x0) at kernel/qaction.cpp:824
 FolderView::createConfigurationInterface (this=0x91eb0e8, parent=0xa094388) at ../../../../plasma/applets/folderview/folderview.cpp:691

[Harald Sitter (apachelogger)]

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!