https://bugs.kde.org/show_bug.cgi?id=397109
Bug ID: 397109
Summary: Plasma doesn't recognize new icons in
~/.local/share/icons/* unless it is restarted
Product: plasmashell
Version: 5.13.3
Platform: Netrunner Rolling
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: theassas...@assassinate-you.net
CC: plasma-b...@kde.org
Target Milestone: 1.0
Follow-up from #plasma on Freenode.
We've been looking into an issue that AppImage users have had to face for a
long time today, and it turned out to be a bug in Plasma.
When integrating an AppImage, a desktop file and one or more icons are copied
into ~/.local/share/{applications,icons}, respectively. These directories are
"monitored" by Plasma. Plasma correctly detects the new desktop file, as
there's a new entry in the launcher. However, the icon is missing.
To fix the issue, you have to restart the plasma shell somehow (e.g., by
logging out and in again).
The reason is that Plasma, on startup, tries to list all directories in
~/.local/share/icons and starts watching them. If these directories don't
exist, changes won't be recognized until plasmashell is restarted. While
initializing, it now finds directories there to monitor. This behavior has
apparently been introduced by
https://phabricator.kde.org/R135:f9e5b852faa78f6d67615ea3c435b10b393cdaa5.
A workaround for older versions of KDE for
https://github.com/TheAssassin/AppImageLauncher will be to create all possible
directories ~/.local/share/icons/hicolor/<all resolutions + scalable>/apps, and
have the user restart plasma once then to permantently fix this issue. This is,
however, just a workaround. Please fix Plasma upstream to watch these
directories even if they're not existing (yet) during startup.
--
You are receiving this mail because:
You are watching all bug changes.
