Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot use/add any repositories, receive "error: GPG: regfile copy: Invalid argument" #4048

Open
Caligatio opened this issue Jan 3, 2021 · 10 comments

Comments

@Caligatio
Copy link

Linux distribution and version

Arch Linux

Flatpak version

1.9.2

Description of the problem

I believe that my Flatpak install is somehow incapable of importing GPG keys which manifests as several errors: GNOME Software Center throws an error when trying to update software and Flatpak won't install any packages.

I am running Arch on ZFS but my searching leads me to believe most of the ZFS bugs are ironed out.

Steps to reproduce

flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
error: GPG: regfile copy: Invalid argument
@ServerBBQ
Copy link

Hello there, I have the same issue on my live usb of pop os(encrypted home using encryptfs). Have you found a way to solve this yet?

@Caligatio
Copy link
Author

Sadly I have not and just gave up.

@ServerBBQ
Copy link

For some reason, system flatpak repos work, but not ones for the user.

@emanuelserpa
Copy link

emanuelserpa commented Jun 9, 2021

Same problem here.

Hello there, I have the same issue on my live usb of pop os(encrypted home using encryptfs). Have you found a way to solve this yet?

I'm using ecryptfs too.

@vinhtq115
Copy link

I'm using Ubuntu 20.04 with ecryptfs (for encrypting my home folder) and I also have this issue too.

@rany2
Copy link

rany2 commented Dec 19, 2021

I was also on Ubuntu 20.04 LTS with ecryptfs and faced the same issue. If you want a quick workaround:

curl -s https://dl.flathub.org/repo/flathub.flatpakrepo | grep -E ^GPGKey= | cut -d= -f2- | base64 -d | gpg --dearmor > ~/.local/share/flatpak/repo/flathub.trustedkeys.gpg
flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

It will give the same GPG warning but it does work.

@johannesjh
Copy link

johannesjh commented Feb 22, 2022

Link to a related ticket: We believe that this issue produces build failures in GNOME builder when trying to export a flatpak bundle, for user accounts that are encrypted using ecryptfs. See https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1637.

specifically, flatpak build-finish produces the following error when run as part of GNOME builder's flatpak bundle export action, if using an ecryptfs-encrypted homedir:

flatpak build-finish --command testp --share=network --share=ipc --socket=fallback-x11 --device=dri --socket=wayland /home/jh/.var/app/org.gnome.Builder/cache/gnome-builder/projects/testp/flatpak/staging/x86_64-master
Not exporting share/applications/mimeinfo.cache, wrong extension
Exporting share/applications/io.github.johannesjh.testp.desktop
error: regfile copy: Invalid argument

@TheHolm
Copy link

TheHolm commented Mar 7, 2022

Have some problem. But I do not use "ecryptfs". Running debian bookworm on pure ZFS.

@smcv
Copy link
Collaborator

smcv commented Mar 8, 2022

if using an ecryptfs-encrypted homedir

This is really a libostree bug rather than a Flatpak bug, and libostree 2022.2 should fix this. Specifically, the relevant change is https://gitlab.gnome.org/GNOME/libglnx/-/merge_requests/30.

ZFS

It would not surprise me if ZFS has the same copy_file_range() behaviour as ecryptfs. Please try libostree 2022.2 when available.

@johannesjh
Copy link

"when available", for ubuntu users waiting for a package update, should translate to the 2022.04 "jammy jellyfish" release of ubuntu.

for future reference, hoping I looked it up correctly: see https://packages.ubuntu.com/jammy/libostree-1-1 where the package version of libostree-1-1 is currently specified as 2022.2-3. (In contrast, ubuntu impish still includes version 2020.8-2 of libostree-1.1, and impish-updates do not yet include an update for libostree-1-1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants