One of the major complaints of Plasma is that you can’t remove the annoying icon from your panels or desktop. Oh yes, I’m talking about the infamous Cashew of Plasma.
Before
This is a small guide on how to get rid of the cashews. You probably need version 4.1 of KDE or higher and know a little bit about how to use the terminal.
Panel Cashew
The cashew here let’s you configure the panel by clicking on. If you feel that you’re satisfied with your setup and don’t need the cashew anymore, you can hide it be choosing “Lock Widgets”. This option can be found in many places, such as the right click menu, when you configure the panel or by clicking on the cashew in the upper right corner.
See, I’m not completely useless
Once you’ve locked your widgets, they can’t be moved, resized/rotated or removed anymore. The option to add new widgets will also be gone. If you want to change anything, simply unlock the widgets in the same way as you locked them.
Desktop Cashew
Edit 16 October, 2012: If you use a relatively new version of KDE Plasma Workspace, which you really should do, the instructions below probably won’t work. Instead I recommend that you install Stealth Cashew:
- Right click on your desktop -> Add widgets… -> Get new widgets -> Download New Plasma Widgets.
- Search for “Stealth Cashew” and then click on “Install” next to it.
- Also make sure that plasma-scriptengine-ruby (or equivalent) is installed; you usually install it using your distribution’s package manager.
- Now you can add the widget to your desktop, adjust the transparency levels, and suddenly you have invisible cashews! (May require that you log out and log in again.)
Original: This one is a little bit tougher. You’ll notice that it won’t go away when you lock the widgets, which has caused frustration among many KDE4 users. One particular person decided to do something about it, and thus the I HATE the Cashew plasmoid was born.
Note: The preferable way to install this widget is through your package manager if it’s in the repositories. The steps below describe how to compile it from source.
- Download the plasmoid here and save it somewhere in your home directory.
- Extract the tbz file with the following command:
- Run the following commands:
- Now we’re ready to compile the plasmoid:
- In most cases, you need root access to install the widget:
- You should find your new plasmoid in the Add Widgets dialog. Add I HATE the cashew to your desktop (remember that you have to unlock the widgets first).
tar -xjvf filename
where filename
is the name of the downloaded file, for example 91009-iHateTheCashew.tbz
.
cd iHateTheCashew
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ..
make
If you run into errors in this step, it’s most likely a dependency problem. Check that you have all necessary packages installed.
sudo make install
When you’ve typed your password and hit Enter, the plasmoid will be installed – you should now be ready for step 6. Below are some corner cases.
If the sudo
command isn’t available, you can use the regular su
command:
su
<type root password>
make install
Sometimes your user has write access to the directory where KDE4 is installed, for example if you have a KDE development environment set up according to this Techbase Tutorial. In that case, you can run make install
without using sudo
or su.
If you use the .bashrc in the link above, you can compile and install the plasmoid with a single command:
cmakekde ..
And we’re done! Lock your widgets again and all cashews should have disappeared.
After
If you want back on your desktop, simply remove the I HATE the cashew plasmoid by clicking on
in the Add Widgets dialog. Nice, isn’t it?
October 31, 2008 at 23:01
There is also a desktop containment withouth the cashew at KDE svn in playground/base/plasma/containments/cluttereddesktop/
November 4, 2008 at 17:38
Yeah, the more “clean” way to get a desktop without the cashew is to use a containment which has disabled the toolbox.
It seems that the default desktop activity in openSUSE 11.1 doesn’t have the desktop cashew.
April 9, 2009 at 17:34
[…] | Como eliminar el icono de Plasma | Errores al compilar con […]
August 14, 2009 at 16:44
[…] Plasma – How to remove the cashew « Who Says Penguins Can’t Fly? […]
December 8, 2009 at 18:28
Am I the only one in the world that really likes the cashew? It’s neat 😀
December 8, 2009 at 22:40
I don’t hate it, but I appreciate that you can remove the cashew. =)
January 22, 2010 at 15:14
I tried to follow the instruction above but didn’t work. Then I discovered a tricky way to, not remove, but hide the cashew nut in the jar. That jar is your panel. Just move your main panel to one edge of the screen (probably left) and then drag the cashew right to the bottom of the screen (of course widgets must be in “unlock” mode). Now bring back the panel to its original position (bottom of the screen). The cashew is covered by the panel now. Might sound funny but at least its out of your sight. Ha ha…
January 23, 2010 at 16:42
What exactly didn’t work Newar? Do you use KDE SC 4.4 RC or Beta? I haven’t tried yet, but I don’t think this plasmoid works well in 4.4. And even if it did, it’s not as easy to remove using the new widget explorer.
If I remember correctly, it wasn’t possible to move the cashew when I published this post. But yeah, now your method works as well. 🙂 There’s also another widget called Stealth Cashew to deal with that yellow thingy.
August 3, 2010 at 11:28
[…] Tma Glassfield + íconos Bespin-black – Cashew. […]
June 2, 2011 at 0:38
Just passing on that “I hate the cashew” plasmoid doesn’t work with KDE 4.6.2. Neither does the Stealth Cashew mentioned in one of the comments. The hiding behind a panel trick works fine. With at least KDE 4.6.2, the cashew is also part of the panel, beats me why. So I had two cashews, or 4 if I am using dual monitors. I really can’t find a use for even one. I’m looking for a way to remove them from the panels now.
June 2, 2011 at 10:16
There’s a patch for iHateTheCashew that make it work with 4.6 (see comments on KDE-look for more details).
The panel cashew has pretty much always been there, it disappears when you lock your widgets.
January 26, 2013 at 16:34
Can’t make. Can anybody make a working edition for current KDE with cmake 2.8.x?
I get a error message with „cmake -DCMAKE_INSTALL_PREFIX=`kde4-config –prefix` ..
“. File was patched before run cmake.
CMake Error at /usr/share/cmake-2.8/Modules/FindKDE4.cmake:98 (MESSAGE):
ERROR: cmake/modules/FindKDE4Internal.cmake not found in
/home/user1/.kde/share/apps;/usr/share/kde4/apps
Call Stack (most recent call first):
CMakeLists.txt:3 (find_package)
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.8)
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run “cmake –help-policy CMP0000”.
This warning is for project developers. Use -Wno-dev to suppress it.
— Configuring incomplete, errors occurred!
January 26, 2013 at 16:44
@Alex:
iHateTheCashew hasn’t been updated in a long time and probably won’t work even if you manage to compile it. Instead I recommend that you try the Stealth Plasmoid plasmoid, which I write about in the updated text.
November 19, 2016 at 22:52
It’s trivial to patch kde4-workspace t make the desktop toolbox AutoHide just like the panel toolbox. Plasma devs are just dirty liars that deny user choice.
The “ClutteredDesktop” in the playground is just a copy of standard Desktop plus a couple options; one to output some informative text, and the other the option to show the cashew, which when unset will call the DesktopToolBox’s hide function on init. Show when unlocked, hide when locked, like the PanelToolBox, is much more logical than an extra option dialog with an option to always show or never show the DesktopToolBox. Surprise, the solution is basically copy’n’paste from the PanelToolBox to the DesktopTookBox and works as perfect as expected.
— plasma/desktop/toolboxes/desktoptoolbox.cpp.orig
+++ plasma/desktop/toolboxes/desktoptoolbox.cpp
@@ -177,6 +177,8 @@ void DesktopToolBox::init()
connect(Plasma::Theme::defaultTheme(), SIGNAL(themeChanged()),
this, SLOT(updateTheming()));
Plasma::ToolTipManager::self()->registerWidget(this);
+ QObject::connect(m_containment, SIGNAL(immutabilityChanged(Plasma::ImmutabilityType)),
+ this, SLOT(immutabilityChanged(Plasma::ImmutabilityType)));
if (KAuthorized::authorizeKAction(“logout”)) {
QAction *action = new QAction(i18n(“Leave…”), this);
@@ -761,6 +763,11 @@ void DesktopToolBox::toggle()
setShowing(!isShowing());
}
+void DesktopToolBox::immutabilityChanged(Plasma::ImmutabilityType immutability)
+{
+ setVisible(immutability == Plasma::Mutable);
+}
+
void DesktopToolBox::adjustBackgroundBorders() const
{
Plasma::FrameSvg *background = const_cast(m_background);
— plasma/desktop/toolboxes/desktoptoolbox.h.orig
+++ plasma/desktop/toolboxes/desktoptoolbox.h
@@ -81,6 +81,7 @@ protected Q_SLOTS:
* show/hide the toolbox
*/
void toggle();
+ void immutabilityChanged(Plasma::ImmutabilityType immutability);
// basic desktop controls
void startLogout();
November 20, 2016 at 11:23
@Fuck Plasma5:
And what exactly would the developers get by lying about this?
From a technical point of view this is easy to implement (which already proves that the developers have thought about the possibility of hiding the cashew), but the developers also have to think about the user experience – what happens if you’ve removed the cashew, as well as disabled the right-click menu, removed all panels, etc.? Could you end up with a broken desktop? I personally don’t agree with the solution of having the desktop toolbox, because I simply think it looks ugly, but that doesn’t mean that the developers are lying.
Ironically, you can remove the cashew in Plasma 5, which I get the impression you hate based on your user name.
For future reference I expect all comments on my blog to abide by the KDE Code of Conduct: https://www.kde.org/code-of-conduct/
That doesn’t mean that you can’t criticize the KDE, but calling developers “dirty liars that deny user choice” isn’t constructive to anyone.
February 22, 2017 at 18:43
The reason to lie is obvious; remove user choice for greater control. The current developers’ way is the ONLY way henceforth, to hell with the hard work of the previous developers that cared about functionality and user choice.
KDE’s code of conduct appear to be “fuck the user”, so NO, I will not abide by it. If you don’t like the way I presented my solution to your problem, then you may fuck off and die with the cashew. What an unappreciative twat you are…
P.S. The ease of implementation does not show that the developers thought of it, rather this is part of the nature of Qt. That the developers claim it would be unduly hard makes it obvious that the either did not consider the implementation or are simply lying when they say it is “too difficult.”
March 25, 2017 at 15:49
@Fuck Plasma5:
Given your username and the posts you’ve written, it seems like you’re here only to rant about Plasma, so I don’t see any point in continuing this discussion with you.
November 9, 2022 at 11:36
Thank yoou for sharing