https://bugs.kde.org/show_bug.cgi?id=510031
Bug ID: 510031
Summary: Discover only shows settings for one user repo and one
system repo at a time
Classification: Applications
Product: Discover
Version First unspecified
Reported In:
Platform: KDE Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Flatpak Backend
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected]
Target Milestone: ---
Created attachment 185349
--> https://bugs.kde.org/attachment.cgi?id=185349&action=edit
flatpak default setup
Hi,
I’ve been trying to add several flatpak repos to my system but discover doesn’t
seem to recognise them properly. My flatpak setup is in screenshot [1]. This is
the flathub repo that comes with the system. This is reflected correctly in
discover's settings menu, as expected.
Added another repo with the command;
flatpak remote-add --subset=verified_floss --prio=2
--title=“Flathub-Verified-FLOSS” flathub-verified-floss
https://dl.flathub.org/repo/flathub.flatpakrepo
The ‘–prio=2’ argument sets the repositories’ priority, higher the number =
higher priority.
The commands "flatpak remotes" and "flatpak remotes -d" show the newly added
repo, but discover still only shows the original, pre-installed repo. Closed
discover and reopened, nothing. Closed discover and deleted the ‘.cache’ folder
in the home directory then reopened discover, and discover now *only* shows the
newly created flathub-verified-floss repo. The buttons to increase or decrease
priority are greyed out.
Deleted the verified repo;
flatpak remote-delete flathub-verified-floss
and re-added it with the ‘–user’ argument;
flatpak remote-add --subset=verified_floss --prio=2
--title="Flathub-Verified-FLOSS" --user flathub-verified-floss
https://dl.flathub.org/repo/flathub.flatpakrepo
This worked! Discover now shows both repos, in the correct order according to
repo priority. The commands ‘flatpak remotes’ and ‘flatpak remotes -d’ both
verify the existence of the new repo.
The problem now, though, is I can add additional repos, either system (which is
the default) or user (using the –user switch), but discover doesn’t acknowledge
them.
Added a third repo (a user repo);
flatpak remote-add --subset=floss --prio=3 --title="Flathub-FLOSS" --user
flathub-floss https://dl.flathub.org/repo/flathub.flatpakrepo
Added a fourth repo (no –user switch, i.e. default)
flatpak remote-add --subset=verified --prio=4 --title="Flathub-Verified-Only"
flathub-verified-only https://dl.flathub.org/repo/flathub.flatpakrepo
Opened discover to find both the third & fourth repo’s missing in discovers
settings. Closed and reopened, nothing. Closed, deleted ‘.cache’ folder again,
reopened discover only to find the original ‘system’ repo (the one that came
preconfigured with the system) has been replaced with the fourth repo, and the
‘flathub-verified’ user repo has now been replaced with the ‘flathub-floss’
user repo.
…So, here’s where I am with this. It appears discover is only capable of
showing one 'user' repo and one 'system' repo at a time in the settings menu.
The only way to get around this, as far as I can tell, is by changing the repo
priority in the command line. For example, if I run the command;
flatpak remote-modify flathub-verified-floss --prio=9
I’ve changed the second 'user' repo to a higher priority. Verified with
"flatpak remotes -d”
Opened discover and found the user repo has changed to “flathub-verified-floss
(user)”, as expected.
To add a spanner into the works, although discover won’t show all repo’s in
settings, it does actually seem like discover can “see” all the configured
repos, and it allows you to install software from all of them.
Firefox is both FLOSS and verified, so I get the option of all 4 repos for
installation, as expected.
VLC media player is FLOSS but not verified, so I get the options of installing
from “flathub” or “flathub-floss”, as expected. Blender is the same.
Spotify is neither FLOSS nor verified, so the only install option is “flathub”,
as expected. Chrome is another example of this.
To test this even further, I’ve disabled the flathub repo “flathub” that came
preinstalled with the system. The expected outcome here is software that is
non-verified and non-floss software should no longer be available for
installation via discover. Ran the command;
flatpak remote-modify --disable flathub
verified the repo is disabled with “flatpak remotes --show-disabled”
Open discover and searched for spotify, chrome, etc etc.
All gone, as expected. Closed discover, re-enabled the repo with;
flatpak remote-modify --enable flathub
All apps are back, as expected.
So, I’m kind of baffled really. Discover has no issue “seeing” the repositories
configured via the command line, nor does it have any issue recognising
configuration changes via the command line, but in the settings menu it only
seems to show one user repository and one system repository at a time when
added via command line.
--
You are receiving this mail because:
You are watching all bug changes.
