pre-installed flatpak remote doesn't work

We pre-configure the flathub remote for flatpak when building images, however this seems to be broken at least on the systemd branch (but likely affects edge too).

On a fresh install, running flatpak remotes shows flathub as expected, however flatpak remote-ls yields

error: Unable to load summary from remote flathub: Signature made Sat Nov 16 19:28:38 2024 using RSA key ID 562702E9E3ED7EE8
Can't check signature: public key not found

So it seems like we're missing a piece here.

This might(?) be a regression due to !5726 (merged) but really i have no idea (cc @craftyguy )

added type::bug label

Hmm, works as expected on my systemd VM.

I encounter the same problem on a new installation (image from Nov 18)

Can you check if the issue still persists after running apk upgrade -a?

Yes, it persisted after upgrade -a and a reboot, I'm still getting "public key not found"

The Alpine wiki mentions doing this for adding the flathub repo:

$ flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

I took the .flatpakrepo file from flathub.org and packaged it in pmaports here, and that file is installed in the rootfs at a location that flatpak autoloads remote config from. As of the posting of this comment, those files are identical, so I don't think keys changed, maybe they expired and no one has noticed on flathub.org?

I've seen vague 'key not found' errors in the past elsewhere when the system clock was wrong. The next time this is reproduced, can you immediately check that the system time is correct?

qcom-msm8953:~$ date && flatpak remote-ls
Fri Nov 22 21:33:16 +04 2024
error: Unable to load summary from remote flathub: Signature made Fri Nov 22 21:23:56 2024 using RSA key ID 562702E9E3ED7EE8
Can't check signature: public key not found
qcom-msm8953:~$

Thanks! So maybe key fetching(?) and/or verification is broken on pmOS somehow? Hmm.

I'm kinda curious if this works or not: flatpak remote-add --verbose --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

This one-liner is from the Alpine wiki, and it targets the flatpak user scope instead of the system scope that the file I installed above uses.

It doesn't work even after this

qcom-msm8953:~$ flatpak remote-add --verbose --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
F: Opening user flatpak installation at path /home/vipaol/.local/share/flatpak
F: Loading https://flathub.org/repo/flathub.flatpakrepo using curl
F: Received 4040 bytes
F: Imported 1 GPG key to remote "flathub"
F: Clearing cached summaries for remote flathub
F: Fetching summary index file for remote ‘flathub’
F: Loading https://dl.flathub.org/repo/summary.idx using curl
F: Received 10001 bytes
F: Loading https://dl.flathub.org/repo/summaries/8d5ae9378ebd01f83517c7c5e08f484a037be8b60746276b11c962515753a082.idx.sig using curl
F: Received 592 bytes
F: Fetching indexed summary file e8df6546c1f060ea240d0db0c1e98cbe5aef8900021274ab2e18f60a55d792c9.gz for remote ‘flathub’
F: Loading https://dl.flathub.org/repo/summaries/e8df6546c1f060ea240d0db0c1e98cbe5aef8900021274ab2e18f60a55d792c9.gz using curl
F: Received 776005 bytes
qcom-msm8953:~$ flatpak remote-ls
error: Unable to load summary from remote flathub: Signature made Fri Nov 22 21:38:40 2024 using RSA key ID 562702E9E3ED7EE8
Can't check signature: public key not found

How about flatpak remote-ls --user ?

works and prints a long list of packages

Ok, so this tells us that:

1. flatpak --user "installation" is fine, the remote could be added and used

2. flatpak --system "installation" (what we're trying to configure with the .flatpakrepo above) is borked somehow

@mariob and @cosmo reported in chat that v24.12 is affected from this too and this works around it:

flatpak remote-delete --force flathub
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

changed milestone to %v24.12 Release

added release-edge release-v24.12 labels