Oh yes, I had forgotten. Thanks!
This is not about Architect ISO which is maybe old.
@ulugbeg and me are using current KDE ISOs.
If I will install Manjaro and disable trust for confuse package. Can this lead to problems in the future were I might not be able to update due to key problems?
After install with above method I am not able to reinstall confuse. Could this also happen with other packages? I believe a yes or no answer is not really possible, but do you have any suggestions?
The fact that the package has been there for a long time, doesn’t mean that it itself is still ‘safe’ or its contents haven’t been tampered with - that’s what the signatures are for. So I prefer not to force-trust keys manually, but trust the trust-chain.
In any case @Chrysostomus, I have uploaded a new build of architect ISO to a hidden folder for testing:
https://osdn.net/projects/manjaro/storage/architect/.20.2.1/
@oberon
tried the new build of architect you have submitted. Still the same error.
Keys were updated within the architect dialog before downloading and verifying of the packtes.
Solved by using older KDE Minimal Version for install.
https://osdn.net/projects/manjaro/storage/kde/20.1.2/manjaro-kde-20.1.2-201019-linux58.iso
Don’t know why. Everything the same as before regarding configuration… 5.10 Kernel also no problems.
Still have to install package sof-firmware manually after install because audio is not working otherwise.
Same problem here with the architect installer. Had this already on another machine and fixed it by hand but I guess its a real showstopper for new users.
downloading lib32-nss-3.60-1-x86_64.pkg.tar.zst...
downloading lib32-vulkan-icd-loader-1.2.162-1-x86_64.pkg.tar.zst...
downloading steam-manjaro-1.0.0.68-1-x86_64.pkg.tar.zst...
checking keyring...
checking package integrity...
error: confuse: signature from "Baptiste Jonglez <baptiste@bitsofnetworks.org>" is marginal trust
:: File /var/cache/pacman/pkg/confuse-3.3-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
==> ERROR: Failed to install packages to new root
I did a Refresh Pacman Keys
before starting the installation.
My ISO file: manjaro-xfce-2020.2.1-210103-linux59.iso
Update:
I was able to fix this by following this guide [FAQ] Issues with “signature is marginal trust” or “invalid or corrupted package” - Newbie - EndeavourOS to reinitialize the GPG keys:
pacman-key --keyserver keyserver.ubuntu.com --init
pacman-key --keyserver keyserver.ubuntu.com --populate archlinux
pacman-key --keyserver keyserver.ubuntu.com --populate manjaro
pacman-key --keyserver keyserver.ubuntu.com --refresh-keys
After this pacman-key --list
showed that the key from Baptiste Jonglez
went from marginal
to trust
.
Had troubles these 2 days to install from Architect with different isos (KDE 20.2, Budgie 20.2, Gnome 20.2.1). I tried Budgie with Full install.
There was a package (can’t remember which, though, and if it was the same each time) that cannot be installed and it broke the install process.
Both Budgie and Gnome were installed correctly by Calamares.
Surely, What you say is right!
But i needed a system anyways. I don’t what else could be done.
The confuse problem- I had it too. Just installed it on a Lenovo Gaming 3. The solution was simply skip refresh keys in Manjaro Architect e.g. don’t do pacman-key --refresh-keys. Then it works. When you do encryption, the GUI installer fails on creating a volume group. But overall it worked, the only system what can handle recent hardware.
Strange, but I’m having this issue as well in a pre-installed Xfce while switching from Unstable to Stable. Regular pacman-key commands aren’t helping so I guess I’ll try @SlowMotion’s fix first. It seems the safest…
and the last command ended in an error…the --refresh-keys command.
gpg: Total number processed: 146
gpg: unchanged: 116
gpg: new user IDs: 1
gpg: new signatures: 47
gpg: signatures cleaned: 105
gpg: user IDs cleaned: 2
gpg: public key DB323392796CA067 is 3037 days newer than the signature
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 25 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 25 signed: 85 trust: 0-, 0q, 0n, 25m, 0f, 0u
gpg: depth: 2 valid: 77 signed: 25 trust: 77-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2021-08-02
==> ERROR: A specified local key could not be updated from a keyserver.
and still fails to update
:: Proceed with installation? [Y/n]
(239/239) checking keys in keyring
[################################] 100%
(239/239) checking package integrity
[################################] 100%
error: confuse: key "Baptiste Jonglez <baptiste@bitsofnetworks.org>" is disabled
:: File /var/cache/pacman/pkg/confuse-3.3-2-x86_64.pkg.tar.zst is corrupted (invalid or
corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
I guess I will have to trust it if I want back into Stable Branch, which I need to do if I want my system tray back, I think. (long story here)
What is missing in my list is that before you execute the 4 commands, you’ll need to cleanup the current keylist. The --init
switch seems to not fullfill this:
cd /etc/pacman.d/gnupg
rm -r *
pacman-key --keyserver keyserver.ubuntu.com --init
pacman-key --keyserver keyserver.ubuntu.com --populate archlinux
pacman-key --keyserver keyserver.ubuntu.com --populate manjaro
pacman-key --keyserver keyserver.ubuntu.com --refresh-keys
This time it ended like this:
gpg: Total number processed: 144
gpg: unchanged: 105
gpg: new user IDs: 13
gpg: new subkeys: 5
gpg: new signatures: 92
gpg: signatures cleaned: 111
gpg: user IDs cleaned: 2
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: public key DB323392796CA067 is 3037 days newer than the signature
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 25 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 25 signed: 86 trust: 0-, 0q, 0n, 25m, 0f, 0u
gpg: depth: 2 valid: 77 signed: 25 trust: 77-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2021-08-02
==> ERROR: A specified local key could not be updated from a keyserver.
Looks nearly exactly like my output. After that the installation run successfully.
I tried -Syyuu again. Ended the same.
:: Proceed with installation? [Y/n]
(239/239) checking keys in keyring [##################################] 100%
(239/239) checking package integrity [##################################] 100%
error: confuse: key "Baptiste Jonglez <baptiste@bitsofnetworks.org>" is disabled
:: File /var/cache/pacman/pkg/confuse-3.3-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
Ok, next try. Please disable the first “Server =” entry in your /etc/pacman.d/mirrorlist
and try again. During one of my installs I had a server that seemed to be not in sync.
THAT sounds like a good idea. I think some mirrors may be off.
Ahhh yeah that was exactly this package that messed up all my recent tries with Architect.
Before, I sometimes had the Partition too full issue seen there [SOLVED]Pacman "Partition / too full" error, despite available space / Newbie Corner / Arch Linux Forums
I tried - and succeeded - yesterday by dowloading and using old (last version 20.0.3) Architect iso, instead of launching Architect from the latest Manjaro isos (Gnome, KDE, …)
That didn’t work either …I’ll try 1 mirror at a time…brb.
Maybe your cache is corrupted:
-
pacman -Sc
(cleans unused packages) -
pacman -Scc
(cleans all packages)