No Flatpak applications listed in Pop!_Shop about beta HOT 12 CLOSED

You were correct. I ran flatpak uninstall --all, followed by flatpak remote-delete flathub and registered the Flathub repository via Repoman. The Flathub remote is now listed as User instead of System and flatpak apps are correctly listed and searchable. Thanks @isantop

If not done already, it might be worth to add a comment to the release note regarding the migration of existing flatpak setup to 20.04. I suppose other flatpak users upgrading from 18.04 or 19.10 may face the same issue later.

from beta.

Shall I report this issue directly to https://github.com/pop-os/shop ?

from beta.

I looked at the Pop!_Shop and some of the apps that you said were unavailable could be downloaded, there are also flatpak versions of some, but not all dual-version apps.

from beta.

I'm unable to reproduce this on upgrades and fresh installs. When you open Pop Shop, click the cog at the top right. Click the Flatpak tab and make sure the repo is there.

from beta.

When you open Pop Shop, click the cog at the top right. Click the Flatpak tab and make sure the repo is there.

This is what I got:

Now I suspect you did not exactly follow the reproducibility steps I highlighted, since your Flathub Type is different than mine (System vs User). I am glad to hear the issue does not manifest itself when installing fresh from the new 20.04 beta 👍 .

Nevertheless, the point of this issue is to show that Pop!_Shop can end up in a state where flatpak support is broken despite a healthy initial flatpak setup before upgrade to 20.04. I don't know whether it's a software, config or cache issue, the point remains that it can.

from beta.

The issue here appears to be that the flatpakrepo was added in System mode (which is the default for the flatpak CLI). Pop Shop currently only supports remotes and Apps installed in user mode, which allows each user to have their own apps installed, and doesn't require authentication to install, update, or remove apps.

System- and User-mode Flatpak repositories are treated differently by the flatpak system. The only way to correct this is to remove existing Flatpak Apps and remove the remote, then re-add the remote using the Pop Shop settings (or via the command line using the --user flag) to set them up in User mode.

from beta.

I think we want to have a "Convert" button which will automatically add the remote in user-mode, then reinstall any applications from the System remote in the new user-mode one.

from beta.

i've encountered this feature in a different way. i have system flatpaks available to all users. there's a fun discrepancy in this approach, each user can install multiple versions of the same flatpak, which is undesirable. however, from the user's perspective in the pop shop it looks like that application isn't installed, so everything looks legitimate.

i was wondering if there could be a user experience that could include system flatpaks in the pop shop in a meaningful way?

from beta.

@tobaccoblonde elementary appcenter doesn't support it, but I believe they're working on it. It's just considered ideal for flatpaks to be installed by users instead of system-wide. No root required that way. Different users have different software needs.

from beta.

@mmstick that's cool they might be working on it, i hope something like it happens. i agree that system wide flatpak's might not be ideal. but it has less unique quirks per application than installing everything in /usr/share/... the last piece of my little project is easy GUI updates. sudo flatpak update will have to suffice.

maybe there is another way to do this, so that a small suite of applications are recognised system wide for all users, and there is no significant challenge to update them.

from beta.

Support for system-wide Flatpaks in AppCenter was merged a couple of weeks ago and is due for the 3.5 release which is being reviewed.

from beta.

Thank you for your report! With 21.04 fast approaching we're closing older issues from previous betas. If you would like to try the latest beta and report issue you find there check out the latest install instructions here.

from beta.