https://bugs.kde.org/show_bug.cgi?id=527019
--- Comment #6 from cwo <[email protected]> --- (In reply to Stian from comment #4) > Just to clarify: this was with AppImageLauncher? Yes. > Oh does it not? I did not know that. In that case, what does the .desktop > file built-in to the AppImage do? AppImage as I understand it has no support for .desktop files. They may include one, but that is optional, and in any case is generally not in a folder where the system will look for it. But now that I look at the taskmanager-specific code, there is some special handling for AppImage. They have a .desktop file, but it's not available to the system generally and used for internal purposes. Task manager basically spies on the process id's environment variable and uses that to rummage around in the internals of the mounted appiage file. It's not very clean, but it is working on one of my computers with an older Plasma version. This is because ungoogled-chromium has multiple process ids, and the one that's associated with the window does not seem to be the one that has the correct environment variable. Though as far as I can tell the 6.7 version also reported the wrong pid, so I'm not sure what's going on here. In any case, I'd strongly recommend actually registering the appimage. It's more robust and it will also show up in launchers, Open With dialogs, etc. I was just about to mark this confirmed as it is technically a regression, but maybe we should just accept that our hack is not robust enough, and AppImage without separate registration by design does not support this. -- You are receiving this mail because: You are watching all bug changes.
