I think OP’s wording wasn’t super clear. A bot created the original post on !technology@lemmit.online, but a human saw the bot’s post there, and decided to cross-post it here to !technology@lemmy.world.

I’m not even sure to be honest, was just following the solution that others had posted.

Pop’s site says that the --configure -a command configures any unpacked but not yet configured packages. And someone on Pop’s github theorized it was related to Microsoft adding their own apt source for VSCode. So it was probably some issue with Microsoft’s new apt source being unpacked but unconfigured, and that caused something in apt/dpkg to freak out. That’s my best guess at least.

There were lots of other peope having this issue, including myself, who have never installed Mullvad. I think it’s related to something in the Ubuntu repos. What fixed it for me was to run:

sudo dpkg --configure -a
sudo apt update && sudo apt upgrade

Some people were also reporting a broken install due to missing packagekit, so maybe ensure packagekit is installed with:

sudo apt install packagekit

Then reboot, and you should be able to update stuff normally now.

When you hit the “login” button in Voyager, it asks you to choose your account’s server. The default is lemmy.world, but your account is on the sh.itjust.works instance. So when it asks for your server, you will have to hit “other” and type in sh.itjust.works, then enter your username and password.

I expect this is the issue, because I am also on CalyxOS without issues.