Summary: | Running [killall plasma-desktop] crashes plasma-desktop | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Adam <armware> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | aseigo, david.mears, notmart |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Adam
2010-05-26 02:24:16 UTC
backup the plasma-desktop*rc files, then try removing the widgets you have running. it's crashing somewhere in ruby bindings in that backtrace. note that killall is not supported (it's a forced unclean termination of the app); kquitapp works better, but really the issue here is "what widget is making it take cpu". what ruby plasmoids do you have running? i removed the cpu and wifi system monitors, and all seems well. i did have the cpu monitor refresh rate set at 0.1s, which i know will eat cpu. when i first added it, it would put cpu at around 10-20%. it was only after a few hours that it would start using 50-90%. *** Bug 240016 has been marked as a duplicate of this bug. *** the system monitors were using 100% cpu; this seems to have been rectified as i can no longer reproduce it (and i used to be able to do so 100% of the time quite easily by simply creating one of them). the python issues .. well, we've forwarded enough of those issues on. several samplings of these problems have been forwarded on to the bindings team. this feature set is not maintained by the core plasma team, however, so marking as 'upstream' as the closest accurate resolution. |