Bug 435746 - Ability to use icon from .appimage files
Summary: Ability to use icon from .appimage files
Status: CONFIRMED
Alias: None
Product: kmenuedit
Classification: Applications
Component: general (show other bugs)
Version: 5.21.4
Platform: Other Linux
: LO wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-14 23:55 UTC by Dan Dascalescu
Modified: 2021-04-16 16:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Dascalescu 2021-04-14 23:55:05 UTC
When creating a new item, the "Select Icon" file picker -> Browse, only offers image file type options (*.png, *.svg etc.). Even if I override that with `*`, it can't read the icon from self-contained .AppOmage files.

However, Dolphin does show correctly the icons appimage files, so perhaps that code could be reused?

An even more user-friendly solution: when the Command field contains precisely one existing file path ending in .AppImage, the Menu Editor could automatically read the icon from that file.
Comment 1 Nate Graham 2021-04-16 16:38:12 UTC
Dolphin gets the icons from the thumbnailer which is generating a thumbnail. If you turn off previews, you'll see that the appimages in question revert to the stock Breeze icon.

> An even more user-friendly solution: when the Command field contains precisely
> one existing file path ending in .AppImage, the Menu Editor could automatically
> read the icon from that file.
Something like that would probably be the most user-friendly solution when not using AppImageLauncher.

However this type of system integration issue is the exact problem that AppImageLauncher was designed to solve. I believe Neon ships it out of the box now? Dunno about other distros.