https://bugs.kde.org/show_bug.cgi?id=505066
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
Summary|Use |Pinning app to Task Manager
|`applications:signal.deskto |saves it to config file as
|p` instead of absolute path |an absolute path to its
|to desktop file when |.desktop file if it's
|dragging icon from |packaged in certain ways,
|Application Launcher to |which is fragile and can
|Icons Only Task Manager |break in the future
--- Comment #1 from Nate Graham <n...@kde.org> ---
In testing, it looks like the newly-pinned app gets saved with an absolute path
rather than just a desktop file name based on how it's packaged, not based on
how it's pinned.
For example, if I pin an app that came from Fedora packaging or was built-from
source, it always gets saved as a desktop file name. But if I pin an app from
Flathub, it always uses an absolute path.
Need to look into the exact conditions that trigger this logic, and possibly
move away from it.
--
You are receiving this mail because:
You are watching all bug changes.
