"Add to Favorites" not working

Hi all,

i’ve removed an application via pacman and added it again. The application got removed from KDE menu and the favorites. So far all fine.
But if i want to add the App icon again to the favorites, it only let me “remove from favorites”. Feels like the app is still there, but that’s not the case.

Any ideas how to solve that? Tried reinstalling, but won’t fix it.

Try removing the application again,

sudo pacman -Rns <appname>

Then manually remove the .desktop file(s) from /usr/share/applications and also ~/.local/share/applications (if there’s a launcher for the application there).

sudo rm /usr/share/applications/<appname>.desktop
rm ~/.local/share/applications/<appname>.desktop

Finally, install the application again.

sudo pacman -S <appname>
2 Likes

Will try it, thanks.
It’s an application from AUR, but that shouldn’t matter. It was working before.

Does KDE have a cache which is worth to clear?

EDIT: I got it. The application was installed in /opt/ with capitals and a space in the folder. The installation did not add the quotation marks of the folder to include the space.

Or, maybe it does

pamac build <appname>

You could delete the ~/.cache directory (must be from a TTY after logging out of the GUI).

rm -rf ~/.cache

Then logout from the TTY, switch back to SDDM/PlasmaLogin and reboot.

This is quite safe – the cache will rebuild itself as you continue using the OS.

I got it. The application was installed in /opt/ with capitals and a space in the folder. The installation did not add the quotation marks of the folder to include the space.

The application was not really to “be built”. The AUR package simply converted a DEB package to make it available in Arch.

Thanks for your help!

1 Like

Which application was it, or is that a secret? :wink:

:blush:Ups, sorry

The application was Snapmaker Luban. It’s an application to generate GCODE required for a Snapmaker 3D printer/laser/CNC combi.
They have builds for different flavors, but not as Arch package:

1 Like

Sorry to butt in, but could you enlighten us less knowledgeable why that last step about switching back to the GUI login is necessary? Wouldn’t it be just as safe to just systemctl reboot while in the TTY?

If it’s enlightenment you desire, it might be arguably safer to first kill SDDM/PlasmaLogin, or even to REISUB/REISUO, despite it not being intended as a casual shutdown/restart method:

However you reboot is irrelevant to the topic.

Easier still, just use CtrlAltDel while in the tty. `systemd will catch that and issue a clean reboot. :wink:

You’re saying that this can also cause a problem if it is not shut down properly?

Interesting. Somewhat annoying if it is that sensitive, but something to consider.

Thanks.

Usually, whatever shutdown/restart mechanism is used, most everything is safely terminated, but sometimes not.

It’s really a question of habit, and whatever may feel more comfortable. Usually, when suggestions/instructions are given, it’s with the lowest common denominator in mind – newer users – at least, that’s usually the case for me, when I remember to.

Suggesting to switch back to SDDM in this case serves to at least remind them that something is still active. Other times, I might simply say “and reboot”.

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.