Created attachment 126202 [details] Path does not exist error SUMMARY An AppImage application pinned to the Icon Only Task Manager cannot be started again from the pinned icon. Errors with "Path does not exist." Starting the application again, results in duplicate icon for the application. STEPS TO REPRODUCE 1. Start an AppImage application by click from dolphin 2. Pin (with right click on the icon) the application icon to the Task Manager 3. Close the application 4. Start the application from the icon in the Task Manager OBSERVED RESULT Receive error about some temporary path not being available. EXPECTED RESULT Application to start again. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 31 KDE (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION I've used Mattermost Linux client to get this behaviour.
Created attachment 126203 [details] Duplicate app icon on second start When starting the application again via click on the file in Dolphin, the icon ges duplicated in the Task Manager.
Can confirm. This is one of the problems that AppImageLauncher is supposed to solve, but maybe there's a way that we can support AppImages better natively...?
cannot reproduce with losslessCut and babe-qml appimages + icon-only task manager. Operating System: Arch Linux KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1
Looks like an old issue. Setting it to needs more info. Please try with a newer version(plasma 5.23.5) and if this is not an issue any more let us know. Bugs placed into NEEDSINFO status will receive a reminder if the ticket: Is at least 15 days old Has not received any comment within 15 days If a bug remains in NEEDSINFO for another 15 days with no comment, it will be closed as RESOLVED > WORKSFORME. If a bug remains in NEEDSINFO with a comment provided within less than 15 days, no action will be taken (as it does not meet the above criteria).
This issue was confirmed and is definitely still an issue. Please don't put bugs in NEEDSINFO WAITINGFORINFO status just because they're old--especially not if they've been marked as confirmed. At least try to reproduce them yourself first.
The problem is this: When launching an appimage its content is extracted to a temporary directory, e.g. /tmp/.mount_myapp123456/myapp When pinning the app Plasma saves that URL. The problem is that when the app is closed the temp dir is removed and the pinned URL is no longer useful. This is somewhat inherent to appimage's design, so I'm not sure there's much that can be done, except for preventing that appimages are pinned in the first place
Apparently some appimages behave differently. When pinning Krita the url of the original .appimage file is pinned and launching from the pinned launcher works fine. Not sure what the relevant difference is
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2557
This should be fixed in AppImages by using AppImageLauncher. Upstream doesn't like the idea to add AppImage desktop integration in libtaskmanager or kwin.