Summary: | Plasma Desktop crashes when starting Eclipse | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Radu Solomon <rsolomon> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | andresbajotierra, asraniel, me |
Priority: | NOR | ||
Version First Reported In: | 4.5 and older | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Radu Solomon
2010-04-08 15:40:00 UTC
The error is related to the Daisy widget. #5 TaskManager::Task::icon (this=0x0, width=32, height=32, allowResize=true) at ../../../libs/taskmanager/task.cpp:406 #6 0x00007f2999112869 in ?? () from /usr/lib/kde4/plasma_applet_daisy.so - Was it recompiled/updated after the update to KDE SC 4.4.2 ? Regards *** Bug 234890 has been marked as a duplicate of this bug. *** Info from the other bugreport: Also just to give complete info: I am using plasma-widget-daisy version 0.0.4.22a-0ubuntu2 and it was not manually compiled or anything just installed/upgraded using synaptic. I'm experiencing exactly the same issue ("RenderBadPicture (invalid Picture parameter)"), but unfortunately I can't debug since eclipse segfaults before it even fully loaded its UI. This is openSUSE 11.3 with KDE 4.4.4 and eclipse 3.6 (Helios). I have no extra plasma widgets installed: $ rpm -qa | grep plasma plasma-theme-oxygen-4.4.4-2.4.i586 plasma-theme-aya-4.4.4-1.4.noarch plasma-addons-4.4.4-1.3.i586 (In reply to comment #4) > I'm experiencing exactly the same issue ("RenderBadPicture (invalid Picture > parameter)"), but unfortunately I can't debug since eclipse segfaults segfauls in gdb, that is, i.e. I also experience segfaults when using the autocompleter when eclipse is not run under gdb. Ok, the issue boils down to be Mozilla-specific https://bugs.eclipse.org/bugs/show_bug.cgi?id=303372 https://bugzilla.mozilla.org/show_bug.cgi?id=522635#c21 so probably not a KDE bug at all. I could fix it by removing a stale mozilla-xulrunner package on my system. Sorry for the noise. Closing based on comments #1 and 3 |