https://bugs.kde.org/show_bug.cgi?id=490657

--- Comment #3 from Ralf S <shopp...@ralfschmid.net> ---
OK, thanks for your replies. Before I report the issue to AppImmageLauncher,
just one more question. I get this, when I use Terminal to integrate the
Appimage:

$ chmod a+x /home/rs/Applications/digiKam-8.4.0-Qt6-x86-64.appimage 
$ /home/rs/Applications/digiKam-8.4.0-Qt6-x86-64.appimage install

AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1)
AppImageLauncher error: appimage_is_terminal_app() failed (returned -1)

(process:5399): GLib-CRITICAL **: 10:03:35.339: g_file_test: assertion
'filename != NULL' failed
(process:5399): GLib-CRITICAL **: 10:03:46.030: g_path_get_basename: assertion
'file_name != NULL' failed
** (process:5399): CRITICAL **: 10:03:46.030: Failed to find desktop file path

Can you see anything AppImage related there? Or does ir rather confirm the
AppImageLauncher problem assumption?

Off topic: Is there a good method to integrate the AppImage manually the same
way as AppImageLauncher does? I’m not too experienced with appimages yet but
see pretty much advantages in the concept and plan to use them more often.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to