Jaan Vajakas

Plasma 4 Widgets 28 comments

Score 76%
24 Dislikes
Aug 31 2013
soger, frumble, thank you for the tips! I moved the cashew under the clock, so it didn't interact with mouse any more and became only barely visible (because the panel is semi-transparent). Then I applied Stealth Cashew to make it totally invisible. I guess the Stealth Cashew script will now be eating some milliseconds of KDE startup time and some memory (it needs to load Ruby and all), but probably not very much compared to the rest. - May 24 2014
After enabling plasma-desktop, plasma and libplasma in kdebugdialog, I could see the following error in the file ~/.xsession-errors-:0 :

File "/usr/share/kde4/apps/plasma_scriptengine_python/", line 75, in init
File "/home/jv/.kde4/share/apps/plasma/plasmoids/py-cashew/contents/code/", line 40, in init
self.cashews = self.getCashew()
File "/home/jv/.kde4/share/apps/plasma/plasmoids/py-cashew/contents/code/", line 66, in getCashew
if c.toolBoxItem() != None]
RuntimeError: no access to protected functions or signals for objects not created from Python

So it seems that the reason is bug . I am not an expert in Plasma, but I understand from the bug description that the mechanism used by PyCashew is deprecated now by the Plasma API developers. But I wonder: does this mean that there is currently no workaround to fix PyCashew and we should ask the Plasma developers to add a new feature that would allow disabling the cashew (either built in or using a widget like PyCashew)? Is there a bug to vote for? - May 23 2014