Summary: | Plasma crashed without reason (maybe related with closed SOHO Explorer plasmoid) | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | gerlos <gerlosgm> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | aseigo, nheckromancer |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
gerlos
2010-09-24 02:07:20 UTC
looks very much like a bug in the Soho plasmoid (or less likely in the python bindings). it's evidently trying to do something after it's been deleted, or at least after the plasmoid was deleted. looks like there was some non-deleted objects still hanging around expecting blindly that the widget is still there. i'd recommend reporting this to the author of that plasmoid. thanks :) Created attachment 63830 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
- What I was doing when the application crashed:
I was programming on java ide eclipse indigo and i was the jboss-eap 5.1 server up... this is all.
- Unusual behavior I noticed:
Plasma crashes sometimes with eclipse and java apps, I disabled all effects of plasma and the performance is better now and the crashes are less.
:)
-- Backtrace (Reduced):
#7 QGraphicsItemPrivate::invalidateParentGraphicsEffectsRecursively (this=0x21) at graphicsview/qgraphicsitem.cpp:5372
#8 0xb6214a09 in QGraphicsItem::update (this=0xb30cef0, rect=...) at graphicsview/qgraphicsitem.cpp:5679
[...]
#10 0x9d59a338 in PyCFunction_Call (func=0xae3b46c, arg=0xa93c02c, kw=0x0) at ../Objects/methodobject.c:85
#11 0x9d601500 in call_function (f=0xaee4e1c, throwflag=0) at ../Python/ceval.c:4013
#12 PyEval_EvalFrameEx (f=0xaee4e1c, throwflag=0) at ../Python/ceval.c:2666
|