containing plasmoid crashes

[Sebastian Kügler]

On Saturday 25 July 2009 11:40:52 Bogdan Bivolaru wrote:
> Hello guys,
>
> I'm writing to you because I'd like to make a suggestion to make a
> containment for errors around each plasmoid, so that when one crashes, it
> doesn't take the whole plasma environment with it.
>
> For example, I had a problem with KDE Network Manager plasmoid crashing and
> taking with it the whole plasma-desktop process before displaying anything.

I might add that the networkmanager plasmoid has never been released, it's still in 
playground and as such *expected* to be unstable.

I know that at least Kubuntu ships it, and I've already asked them not to ship it 
until we are actually confident that it's not totally in flux (which it is right 
now). I'm CC:ing kubuntu-devel here, to illustrate why I'd rather not see it shipped 
until further notice, and certainly not as part of the default install.

really, the Right Thing To Do is: DO NOT RUN UNSTABLE CODE (unless you want to help 
developing it ;-)).

> I wouldn't even get to see the panel containing the offending plasmoid, so
> the only workaround I could find was to 'bastardize' the plasma config
> files to remove the plasmoid from the panel. After removing it from the
> panel plasma works fine.
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20090727/92fa52b3/attachment-0001.sig