Summary: | Plasma crashed with multiple clocks and weather applets | ||
---|---|---|---|
Product: | [Plasma] plasma4 | Reporter: | Xavier Hourcade <public.oss> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | aseigo, public.oss |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Xavier Hourcade
2011-05-01 00:19:04 UTC
Created attachment 59472 [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
That was quick ! Just rebooted.
- What I was doing when the application crashed:
As previously: connection error at login, pyweather (it's only one left) don't refresh once online.
Checked its settings, close them, crashed within seconds.
Also, each clocks has a different vert pos again.
- Unusual behavior I noticed:
This time CPU usage was clearly high (and still is now): >= 70% incl. 45% to virtuoso-t alone, plasma-desktop appears as "stopped", getting hot at 70ÂșC ^^.
(this is an Asus V1S laptop, Core 2 Duo T7500 @ 2.20Ghz, 4GB RAM).
-- Backtrace (Reduced):
#6 QGraphicsItemPrivate::invalidateParentGraphicsEffectsRecursively (this=<value optimized out>) at graphicsview/qgraphicsitem.cpp:5372
#7 0x000000378938538e in QGraphicsItem::update (this=0x2167db0, rect=...) at graphicsview/qgraphicsitem.cpp:5679
#8 0x00007fc40e014e09 in update (sipSelf=<Applet at remote 0x2a6e5f0>, sipArgs=(), sipKwds=0x0) at /usr/include/QtGui/qgraphicsitem.h:505
#9 meth_QGraphicsItem_update (sipSelf=<Applet at remote 0x2a6e5f0>, sipArgs=(), sipKwds=0x0) at sipQtGuiQGraphicsItem.cpp:2840
#10 0x0000003ef96e965b in call_function (f=<value optimized out>, throwflag=<value optimized out>) at /usr/src/debug/Python-2.7/Python/ceval.c:4071
Removing pyWeather applet definitely ..remove the issue too. Auto-repositioning of clocks remains broken thou (separate issue I guess). *** This bug has been marked as a duplicate of bug 272457 *** |