unable update 1password on fedora 36
Comments
-
I also have problems installing the Flatpak. Something seems to be broken on the flatpak ref:
Error: Error deploying: While trying to checkout 2042ea48690aa383c9d67fff71971947f9f7fabb7191c15b5c1377284cc4e52d into /var/lib/flatpak/app/com.onepassword.OnePassword/x86_64/stable/.2042ea48690aa383c9d67fff71971947f9f7fabb7191c15b5c1377284cc4e52d-AH8FN1: No such metadata object 09a1d18967142012c1e351c92cc4a693be9d5a83c5f4bd9fe4ef340146654227.dirtree
error: Failed to install com.onepassword.OnePassword: Error deploying: While trying to checkout 2042ea48690aa383c9d67fff71971947f9f7fabb7191c15b5c1377284cc4e52d into /var/lib/flatpak/app/com.onepassword.OnePassword/x86_64/stable/.2042ea48690aa383c9d67fff71971947f9f7fabb7191c15b5c1377284cc4e52d-AH8FN1: No such metadata object 09a1d18967142012c1e351c92cc4a693be9d5a83c5f4bd9fe4ef340146654227.dirtree0 -
Hello, @PeterG_1P
Thank you. Your advice per email did help. Thank you.0 -
Any possibility of putting the fix for @trap2006 in the thread? I am having (similar / same) issue; though mine is saying Invalid package file.
Invalid package file:
package 1password-8.7.3-1.x86_64 cannot be verified and repo 1password is GPG enabled: /var/cache/PackageKit/36/metadata/1password-36-x86_64/packages/1password-8.7.3.x86_64.rpm could not be verified.
/var/cache/PackageKit/36/metadata/1password-36-x86_64/packages/1password-8.7.3.x86_64.rpm: digest: SIGNATURE: NOT OK1Password version: 8.7.1
80701002, on PRODUCTION channelFedora 36 (KDE Plasma)
Operating System: Fedora Linux 36
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.3
Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-6100T CPU @ 3.20GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5300 -
I had been trying to update in the Discover app.
I decided to do sudo rpm upgrade in terminal, and it worked fine.
Is that what the fix for trap2006 was?0 -
Hi @Lirleni, I can't share the specific troubleshooting steps we've taken with another user without their permission, but running these installation steps again (even if you installed with .rpm before) can reliably fix that GPG issue. 👍
0