[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    containing plasmoid crashes
From:       Bogdan Bivolaru <bogdan.bivolaru () gmail ! com>
Date:       2009-07-25 9:40:52
Message-ID: a86b2f600907250240n79911d93kd63a11dd5b268532 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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 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.

I am not writing this mail to whine about my issue:
I think building a fence/containment for errors around each plasmoid should
solve a lot of bugs in Bugs.Kde.Org, or even if it doesn't fix the plasmoid
errors, this should make them bearable for end-users: they can ignore or
remove the offending plasmoid and be merry with it.

There's also the issue of reporting krashes in BKO: if a containment is
build around plasmoids, crashes will not be caught by Dr Krash. But can't
you launch Krash from the plasma containment to build the report?



-- 
"The best way to predict the future is to invent it.", 1971, Alan Kay:
http://www.smalltalk.org/alankay.html

[Attachment #5 (text/html)]

Hello guys,<br><br>I&#39;m writing to you because I&#39;d like to make a suggestion \
to make a containment for errors around each plasmoid, so that when one crashes, it \
doesn&#39;t take the whole plasma environment with it.<br> <br>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 wouldn&#39;t even get to see the \
panel containing the offending plasmoid, so the only workaround I could find was to \
&#39;bastardize&#39; the plasma config files to remove the plasmoid from the panel. \
After removing it from the panel plasma works fine.<br> <br>I am not writing this \
mail to whine about my issue:<br>I think building a fence/containment for errors \
around each plasmoid should solve a lot of bugs in <a \
href="http://Bugs.Kde.Org">Bugs.Kde.Org</a>, or even if it doesn&#39;t fix the \
plasmoid errors, this should make them bearable for end-users: they can ignore or \
remove the offending plasmoid and be merry with it.<br> <br>There&#39;s also the \
issue of reporting krashes in BKO: if a containment is build around plasmoids, \
crashes will not be caught by Dr Krash. But can&#39;t you launch Krash from the \
plasma containment to build the report?<br>  <br><br clear="all"><br>-- <br>&quot;The \
best way to predict the future is to invent it.&quot;, 1971, Alan Kay: <a \
href="http://www.smalltalk.org/alankay.html">http://www.smalltalk.org/alankay.html</a><br>




_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]