Bug 1706835 - Enabling bad rpm-ostree repository makes all repo entries disappear from Software repositories
Summary: Enabling bad rpm-ostree repository makes all repo entries disappear from Soft...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-06 11:30 UTC by Daniel Rusek
Modified: 2021-03-25 13:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-25 13:33:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-software issues 1194 0 None None None 2021-03-25 13:33:16 UTC

Description Daniel Rusek 2019-05-06 11:30:51 UTC
Description of problem:
After enabling rpm-ostree repository that has some issue (returns error), all rpm-ostree repo entries disappear from the Software repositories window in GNOME Software.

Version-Release number of selected component (if applicable):
gnome-software-3.32.1-4.fc31.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Use latest Fedora Silverblue Rawhide.
2. Open GNOME Software, Software repositories.
3. Try enabling the NVIDIA RPM Fusion repo.
4. Reboot the computer.

Actual results:
After a reboot, all rpm-ostree repo entries are gone from the Software repositories window.

Expected results:
After a reboot, all rpm-ostree repo entries are correctly displayed in the Software repositories window.

Additional info:
11:28:55:0973 Gs  not handling error failed for action refresh: cannot update repo 'rpmfusion-nonfree-nvidia-driver': Cannot prepare internal mirrorlist: file "repomd.xml" was not found in metalink

Comment 1 Daniel Rusek 2019-05-06 11:33:34 UTC
The rpm-ostree repos start showing again after manually setting "enabled=0" in the problematic repo file.

Comment 2 Ben Cotton 2019-08-13 17:12:35 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 3 Ben Cotton 2019-08-13 19:22:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 4 Ben Cotton 2020-02-11 15:41:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 5 Milan Crha 2021-03-25 13:33:19 UTC
I moved this upstream, because it's not Fedora specific. Please see [1] for any further updates.

[1] https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1194


Note You need to log in before you can comment on or make changes to this bug.