Bug 229280 - One failing plasmoid will harm the whole plasma workspace
Summary: One failing plasmoid will harm the whole plasma workspace
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-03 18:56 UTC by Alvise
Modified: 2010-05-07 23:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alvise 2010-03-03 18:56:11 UTC 
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    openSUSE RPMs

I have seen this problem with the whole series of KDE SC4.x :

-When a plasmoid freezes, the whole workspace becomes frozen or quite unresponsive. I've had this problem with yawp or with a stocks widget (stockoid?) that would freeze in case of failing net connection. Then the whole desktop would become hardly usable.

- When a plasmoid crashes, the whole plasma workspace crashes. I have this problem with SC4.4.0 and SC4.4.1 each time I login in the OpenDesktop widget: the widget crashes and so does plasma.

Plasma should be more robust, in a way that a bug in a plasmoid cannot spoil the other plasmoids or the whole desktop
Comment 1 Aaron J. Seigo 2010-03-03 19:01:34 UTC 
this is a design trade-o decision that has been discussed extensively elsewhere.
Comment 2 Bryan Cebuliak 2010-05-07 23:17:28 UTC 
sounds  similar  to  this report.
https://bugs.kde.org/show_bug.cgi?id=222223
 "design  decision"? Funny, if it were not sad. By any other name, still a bug to be  fixed.