Red Hat Bugzilla – Bug 571311
[abrt] crash in kdebase-workspace-4.4.0-8.fc12: Process /usr/bin/plasma-desktop was killed by signal 6 (SIGABRT)
Last modified: 2010-04-13 08:22:52 EDT
abrt 1.0.7 detected a crash.
Attached file: backtrace
cmdline: plasma-desktop --nocrashhandler
comment: Putting the knetworkmanager plasmoid fully in charge (killing and disabling nm-applet) caused my kde4 to enter a continual series of plasma-desktop crashes. If I restarted plasma-desktop(using yakuake) it would immediately crash again, and again. The only solution was to wipe my .kde folder.
reason: Process /usr/bin/plasma-desktop was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
How to reproduce
1.Enable knetworkmanager plasmoid
Created attachment 398425 [details]
The network management plasmoid (kde-plasma-networkmanagement) is known to be unstable, don't use it, use the plain knetworkmanager (system tray applet) instead.
Thank you for taking the time to report this issue to us. This is an issue which is best addressed by the upstream developers.
Please file a report at bugs.kde.org , and when done add the upstream report info to this report.
We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
Thank you for the bug report.
*** This bug has been marked as a duplicate of bug 571054 ***