GNOME Bugzilla – Bug 796040
Cannot add GIMP 2.10 shortcut to Ubuntu 16.04 launcher
Last modified: 2018-06-17 20:08:33 UTC
Started GIMP and clicked "lock to launcher". An icon with question mark was locked to it. Whole shortcut disappeared after reboot. GIMP 2.10 installed with Flatpak to Ubuntu 16.04.
This reads like something that should be handled on the Ubuntu side, likely in the Desktop environment you are using. Could you file a bug in the Ubuntu bug tracker about this?
Yes, Ubuntu probably may not know what to do with a flatpak-launched application. Though it may also be how you started GIMP. Did you started it from the desktop (menu, or some icon or overview, etc.)? Or did you start it by command line for instance? Most desktop nowadays links launchers to a desktop file. But for this to work, you need to actually start the software through this desktop file. If you started by command line for instance, the desktop may not be able to create a launcher because it won't know where the desktop file is. This is for instance how it works in GNOME. So: how did you start GIMP before trying to lock it as a launcher?
Hello! I started it through Ubuntu's launchbar search, it finds GIMP and shows an icon for it. I actually found out now, that gimp shows an icon at the launchbar while the program is still starting, and If I manage to right-click it (lock to launcher) quickly, the launch icon will stay. If I wait too long, the icon gets grayed out and will disappear after closing the GIMP.
Well this definitely looks like either a bug or a lack of flatpak support in Ubuntu. You should report it upstream.
The first Ubuntu to have official flatpak packages was 17.10: https://packages.ubuntu.com/search?suite=all&arch=any&searchon=names&keywords=flatpak Still, I would expect a launcher to just stay there, it shouldn't matter what is launched (then again, this is Ubuntu...)
> Still, I would expect a launcher to just stay there, it shouldn't matter what is launched Yes definitely. As explained, nowadays most launchers/menus are based on the desktop files, not binaries. This means that there shouldn't be anything flatpak-specific there (flatpak modifies the desktop file directly, but that is transparent to a desktop which only cares about the file itself and not about how the application is actually run in a given field of this file). This is why I am a bit unsure when I say that this may be flatpak-support related. This should not make any problem to a modern desktop. But now I have no idea of the internals of the Ubuntu desktop, so who knows…
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1443.
Can you please answer my question at https://gitlab.gnome.org/GNOME/gimp/issues/1443