Hello world!
Tell me, please.
I’m just starting to get acquainted with Qubes. Recently installed the matrix element with great difficulty. And the other day I was faced with the inability to update workstation and debian. When updating, it gives an error that is somehow related to element, but my technical knowledge is not yet enough to figure it out and solve this problem on my own.
Same error when updating workstation. I really don’t want to reinstall the system, please help me figure it out…
It looks like apt is missing the signing key needed to verify packages from Element’s repository. This happens when the step to download and install the repository’s GPG key either didn’t complete successfully or was skipped. You need to perform these steps again in both whonix-workstation-17 and debian-12-xfce:
- Make sure
wget
is installed by runningsudo apt install wget -y
(Alternatively, if you’re comfortable usingcurl
, you can use that instead ofwget
) - Download and install the signingkey (according to the official Element download instruction):
sudo wget -O /usr/share/keyrings/element-io-archive-keyring.gpg https://packages.element.io/debian/element-io-archive-keyring.gpg
This key allows apt to verify that packages from packages.element.io are legitimate. If the key is outdated or missing (as in your case), you’ll see GPG errors like the one you’re currently experiencing.
After downloading the key, re-run your updates in both whonix-workstation-17 and debian-12-xfce to make sure that everything works correctly. That should fix this issue.
No worries; unless you’ve made a serious mistake in dom0, it should never be necessary to reinstalled Qubes.
Thank you! Debian is upgrading! I remembered why I could have had an unfinished installation, it was not completed. By default, Internet access is disabled in the main templates. I had to give it to them… True, the system warned me not to do this, but I think that nothing bad will happen if I turn on the Internet in standard templates while installing element. Thank you very much again, andreasglashauser. You saved me a headache! All the best to you.
this was not necessary. You could have made wget use the gateway proxy to get out.
export https_proxy=http://127.0.0.1:8082/
wget ....