Created attachment 1834923 [details] screenshot for Firefox +++ This bug was initially created as a clone of Bug #2015569 +++ Description of problem: Fedora Workstation's GNOME Software often shows two results for some searches, when there's a flatpak and RPM available. But not all apps are affected. Examples include Thunderbird, Firefox. Version-Release number of selected component (if applicable): gnome-software-41.0-5.fc35.x86_64 firefox-93.0-2.fc35.x86_64 How reproducible: Seems always for certain apps (Firefox, Thunderbird) but not all apps. Not sure of the pattern. Steps to Reproduce: 1. Launch GNOME Software 2. Search for Firefox 3. Actual results: Two results show up, see screenshot. It's not obvious from the results that one is a flatpak and one is an RPM. When you click on the one that happens to be RPM, there's just an install button, no drop down menu, or any other indication, that it's an RPM. When you click on the one that happens to be flatpak, you can see a drop-down menu showing the repository options. Expected results: Somehow consolidate the search results into one choice. (Workstation defaults to RPM unless there is only a flatpak available. Silverblue defaults to flatpak.) Additional info: --- Additional comment from Chris Murphy on 2021-10-19 14:12:52 UTC --- --- Additional comment from Chris Murphy on 2021-10-19 14:29:08 UTC --- users@ list report is how I discovered this, in the following thread "How did I get a flatpack installed?" https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/DSAQ7B4SAO6SBMJPSV23B4TLDAG6S55Z/ --- Additional comment from Vincent Chernin on 2021-10-19 16:14:09 UTC --- The issue here is that the Fedora RPM and Flatpak packages don’t use the AppStream ID. The way GNOME Software differentiates between apps is their same AppStream ID—- if two packages have different IDs they are simply considered to be different apps. So the solution here is likely to fix the RPM package so it uses org.mozilla.Thunderbird like the Flatpak uses. For reference: https://src.fedoraproject.org/rpms/thunderbird/blob/f35/f/thunderbird.spec#_648 https://src.fedoraproject.org/flatpaks/thunderbird/blob/stable/f/container.yaml#_8 --- Additional comment from Vincent Chernin on 2021-10-19 16:15:47 UTC --- The issue here is that the Fedora RPM and Flatpak packages don’t use the *same* AppStream ID is what I meant to write, but I am on my phone so apologies. --- Additional comment from Chris Murphy on 2021-10-19 16:56:45 UTC --- Should we change the component of this bug to Thunderbird? Then clone+tidy a new bug report against each additional apparent duplicate, e.g. Firefox? --- Additional comment from Vincent Chernin on 2021-10-19 20:44:32 UTC --- > Should we change the component of this bug to Thunderbird? Then clone+tidy a new bug report against each additional apparent duplicate, e.g. Firefox? Sounds good to me. --- Additional comment from Michael Catanzaro on 2021-10-20 01:47:06 UTC --- (In reply to Chris Murphy from comment #5) > Should we change the component of this bug to Thunderbird? Then clone+tidy a > new bug report against each additional apparent duplicate, e.g. Firefox? I would report a separate bug against every component that makes the same mistake, yes. I can trivially reproduce with both Thunderbird and Firefox, and I agree it's not a GNOME Software bug because two apps with different app IDs are not the same app. Doesn't matter if they have the same name and icon: the ID is the ID.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.