The Gimp application appears twice in the search results for 'gimp'. PROBLEM: People will install the old version (2.8 bionic universe) because it ist 1st on the list. They will miss the newer (snap) version 2.10 which is the 7th in the list. 'OFF the screen' on my laptop!! Presumed CAUSE: The old one is titled "GNU Image Manipulation Program" the new version (snap) is titled "GIMP". SUGGESTION: The proper fix would have just one Gimp search result. Not duplicating the description and images. With an option to choose which source to install inside this single Gimp result. Have a default source for those who do not know the difference. With an "Advanced" option for those who do. QUICK FIX: Rename the entries to be the same. NOTE: In Ubuntu 19.04 the Snap entry appears first. STEPS TO REPRODUCE 1. Open Discover 2. Search for gimp 3. Look for all gimps in the search results
I just got the Snap guys to rename their GIMP snap in the Snap store. Lets see if that clears this up.
SNAP store UPDATE: Search "gimp" still gets 2 separate "GIMP" search entries. Both now called "GNU Image Manipulation Program" from different sources Bionic and Snap. Search "GNU image" gets 3 separate entries!! Bionic/Snap/Flathub. And the out of date version 2.8 bionic is still listed at the top with the other 2 way below.
Isn't that a problem with the data sources instead of the Discover application?
The source of the problem my be the data sources are incorrectly tagged. The snap store guys corrected their entry. But the problem is still there in Discover. Should we assume that the different repositories are going to fix this for all apps? I suspect not. The 'result' is, that Discover does not display "Identically named" entries as a single entry that us helpful to users. Adding some logic to Discover would make the user experience more reliable. If it is INTENDED that the entries remain separate, the user still has no obvious way of making a choice between 2 identical entries. Even if they know what snaps and flatpacks are.
*** This bug has been marked as a duplicate of bug 399530 ***