I3wm installation problems: "endeavouros-skel-i3wm... is unknown trust"

So, I think I’ve made it! Let’s go through the process…

Early today I tried to install it on a virtual machine in another computer just to see if the story repeated itself. And it did. The same error that appeared at the manual-post-offline-installation occurred during the online installation on another machine:

[details="Summary"]
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: "Total Download Size:      0.02 MiB" 
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: "Total Installed Size:  1989.72 MiB" 
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: "" 
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: ":: Proceed with installation? [Y/n]" 
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: ":: Retrieving packages..." 
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: "xbindkeys-1.8.7-2-x86_64 downloading..." 
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: "checking keyring..." 
2022-07-15 - 09:54:00 [6]: [PYTHON JOB]: "checking package integrity..." 
2022-07-15 - 09:54:05 [6]: QML Component (default slideshow) Next slide
2022-07-15 - 09:54:18 [6]: [PYTHON JOB]: "error: xbindkeys: signature from \"Konstantin Gizdov <arch@kge.pw>\" is marginal trust" 
2022-07-15 - 09:54:18 [6]: [PYTHON JOB]: ":: File /var/cache/pacman/pkg/xbindkeys-1.8.7-2-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature))." 
2022-07-15 - 09:54:18 [6]: [PYTHON JOB]: "Do you want to delete it? [Y/n] error: failed to commit transaction (invalid or corrupted package)"
[/details] 

Full logs here.

This made me think that something was really going on with this package. The other day I was able to do an online installation of i3 EndeavourOS on another machine of mine under the same network and all went flawlessly so this made me think that from then to now something happened with the package that I wasn’t able to correct all by myself… Also, today, another user ran into the same error in the Arch Forum regarding the “xbindkeys package”, so that gave me another reason to think this was not my problem.

Then, I followed @jonathon FAQ entry on signature errors which actually partially solved my problem with the xbindkeys package yesterday but today it wasn’t working for some reason… But he wrote a beautiful post where he explained how the keyserver might need to be changed (to e,g, “pgp.,mit.edu”, “keyserver.ubuntu.com”, etc.) and refreshed and that really helps a lot of people out there, but wasn’t working for me. But then I decided to follow your latter instructions, @pycrk. I ran your commands thinking that they would probably solve the endeavouros package, but I still needed to solve the xbindkeys one. So I decided to run pacman-key --list-keys 'arch@kge.pw' to see the keys associated to it and I used the “–lsign-key” command with the keys that the “–list-keys” command gave me. I don’t know if this is safe really, but if your installation process requires that package from that address I would assume it is safe(?). Anyways… I did it and it worked like a charm! I will leave the commands that I used in order bellow:

sudo pacman-key --add /usr/share/pacman/keyrings/endeavouros.gpg 
sudo pacman-key --lsign-key 497AF50C92AD2384C56E1ACA003DB8B0CB23504F
sudo pacman-key --populate
sudo pacman-key --refresh-keys
sudo pacman -Syy

>Then i wrote:

sudo pacman-key --lsign-key 4BE61D684CB4E31741614E7089AA27231C530226
sudo pacman-key --lsign-key 0A9DDABB64B993D82AD45E4F32EAB0A976938292

>These are the two keys that showed to me at "pacman-key --list-keys 'arch@kge.pw'"

sudo pacman-key --populate
sudo pacman-key --refresh-keys
sudo pacman -Syy

[If you want to know the full diagnosis of the problem read the whole thread]

Thanks for your help guys. Can you let me know If i made the right decisions commandwise?

Also, sorry if I’m not formatting the post text right. This “Summary” thing, isn’t hiding anything is it? Still need to check up the tutorials about the posts (it’s also my first time writing in a real forum lol).

1 Like