Created attachment 1878824 [details] Source dropdown Created attachment 1878824 [details] Source dropdown Created attachment 1878824 [details] Source dropdown Created attachment 1878824 [details] Source dropdown Description of problem: Version-Release number of selected component (if applicable): 42.1 How reproducible: Always Steps to Reproduce: 1. Go to Software > Software Repositories and look at the Fedora Flathub Selection item at the bottom of the list; 2. Add Flathub repo (flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo); 3. Reboot; 3. Search for Flatpak applications available only in Flathub. Actual results: - Source is shown as "Fedora Flathub Selection (Flatpak)"; - Flathub doesn't get enabled by default; - "Fedora Flathub Selection" moves from Fedora Third-Party Repositories section to the Applications (Flatpak) section. Expected results: - Source being shown as "Flathub (Flatpak)". - Flathub getting enabled by default Additional info: - Removing flathub and adding it back fixes the problem; - Readding flathub makes "Fedora Flathub Selection (Flatpak)" to disappear from the Fedora Third-Party Repositories section; - I installed F36 in a VM and same thing occurred.
Created attachment 1878825 [details] "Applications (Flatpak)" section "Applications (Flatpak)" section
Created attachment 1878826 [details] "Fedora Third-Party Repositories" section "Fedora Third-Party Repositories" section
Thanks for a bug report. I guess the gnome-software version is a typo, you probably meant 42.1. Anyway, could you run: $ flatpak remotes --show-disabled $ fedora-third-party list --csv $ fedora-third-party list --csv -a Could you provide versions of the flatpak and fedora-third-party, please? You can do it with: $ rpm -q flatpak fedora-third-party As far as I know, Flatpak doesn't allow having the same named remote in the installation (system installation in your case, according to the screenshots). I do not much understand when the screenshots were taken, it's confusing to me, I'm sorry. It's surely not at the same time, because the remote is always shown in a single section. That is moves around is correct, because the fedora-third-party stops claiming the ownership of it once the filtering is turned off for the remote and/or when the user re-installs it.
(In reply to Milan Crha from comment #3) Ops! Yes, it's 42.1. I boot into a live media and ran the commands without adding Flathub: [liveuser@localhost-live ~]$ flatpak remotes --show-disabled Name Options fedora system,oci fedora-testing system,disabled,oci [liveuser@localhost-live ~]$ fedora-third-party list --csv flathub,flatpak google-chrome,dnf phracek-PyCharm,dnf rpmfusion-nonfree-nvidia-driver,dnf rpmfusion-nonfree-steam,dnf [liveuser@localhost-live ~]$ fedora-third-party list --csv -a flathub,flatpak google-chrome,dnf phracek-PyCharm,dnf rpmfusion-nonfree-nvidia-driver,dnf rpmfusion-nonfree-steam,dnf [liveuser@localhost-live ~]$ rpm -q flatpak fedora-third-party flatpak-1.12.7-2.fc36.x86_64 fedora-third-party-0.10-1.fc36.noarch
- "'Fedora Third-Party Repositories' section" attachment = before adding the Flathub. - "'Applications (Flatpak)' section" and "Source dropdown" attachments = after adding Flathub
Thanks for the update. The live media is not the same as your system. Nonetheless, I think I know what's going on here. If I understand your claim properly, then what you expect is that, after installing complete Flathub with the `flatpak` command: - the existing 'flathub' remote changes its name - the existing 'flathub' remote is enabled, in case it was disabled. The two above are the only problems I see (the flatpak command removes the filter on the existing 'flathub' remote already). That the 'flathub' moves to a different section in the Repositories Dialog of the Software is correct, because fedora-third-party stops claiming the 'flathub' remote as being provided by it, due to it being changed (filter removed). I move this to the flatpak, because it should be fixed there (you used that command, not the Software, to install the remote).
U(In reply to Milan Crha from comment #6) > Thanks for the update. The live media is not the same as your system. > Nonetheless, I think I know what's going on here. If I understand your claim > properly, then what you expect is that, after installing complete Flathub > with the `flatpak` command: > > - the existing 'flathub' remote changes its name > - the existing 'flathub' remote is enabled, in case it was disabled. > > The two above are the only problems I see (the flatpak command removes the > filter on the existing 'flathub' remote already). That the 'flathub' moves > to a different section in the Repositories Dialog of the Software is > correct, because fedora-third-party stops claiming the 'flathub' remote as > being provided by it, due to it being changed (filter removed). > > I move this to the flatpak, because it should be fixed there (you used that > command, not the Software, to install the remote). Understood. I forgot to mention that this problem happens in a fresh install too. This bug always happens when setting up Flathub for the first time in F36.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 '36'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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.