MXPI chokes on security key [Solved]

[paul1149]

Merry Christmas everyone! Thank you for what you do to bring MX to us and to support users!

This morning I decided to upgrade some upgradables under the Debian Backports tab of MXPI. I'm on MX23/kde. It choked on a keyring problem. Hitting Enter in Console Output does nothing, neither does ctrl-c or ctrl-x, so the process is stuck, and I'd like to either complete it or exit without breaking anything.

Any ideas? Thank you.

Code: Select all

Unpacking webcamoid (9.1.1-1~mx23+1) over (9.0.0-6) ...
Setting up filelight (4:23.08.4-0.1~mx23+1) ...
Setting up webcamoid-data (9.1.1-1~mx23+1) ...
Setting up libavkys9:amd64 (9.1.1-1~mx23+1) ...
Setting up webcamoid-plugins:amd64 (9.1.1-1~mx23+1) ...
Setting up webcamoid (9.1.1-1~mx23+1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://security.debian.org/debian-security bookworm-security InRelease
Hit:4 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo bookworm InRelease
Hit:5 http://deb.debian.org/debian bookworm InRelease
Hit:6 https://brave-browser-apt-release.s3.brave.com stable InRelease
Get:7 https://repos.azul.com/zulu/deb stable InRelease [5,289 B]
Ign:1 https://repos.azulsystems.com/debian stable InRelease
Ign:8 https://repo.vivaldi.com/snapshot/deb stable InRelease
Hit:9 https://repo.nextdns.io/deb stable InRelease
Hit:10 https://repo.vivaldi.com/snapshot/deb stable Release
Hit:11 https://repos.azulsystems.com/debian stable Release
Get:12 https://mega.nz/linux/repo/Debian_12 ./ InRelease [2,953 B]
Fetched 8,242 B in 1s (9,448 B/s)
Reading package lists...
W: https://repos.azul.com/zulu/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: http://repos.azulsystems.com/debian/dists/stable/Release.gpg: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

[Jerry3904]

That screen iirc is not actually an active console but a display so commands can't be entered.

Normally gpg problems can be solved by using MX Tool> Fix GPG etc.

[Eadwine Rose]

I had a similar kind of problem with Slack a while ago.

viewtopic.php?p=737803#p737803

@dolphin_oracle told me in post 8 to get the key for slack into the new location and remove the old /etc/apt/trusted.gpg file.

viewtopic.php?p=737817#p737817


You might want to take a looksee through it, see if it is indeed similar. I am not going to trust my own judgement on this one to say it's the same, but it sure looks like it.

[paul1149]

Ok, thanks much. I've run the fix-gpg, which I didn't know existed, so maybe the problem is solved. If not, I'll return to your post.

[Eadwine Rose]

If the fix GPG fixed it, great!! :D