Article 6E66J Errors while updating my apps, is this anything to worry about?

Errors while updating my apps, is this anything to worry about?

by
Pagan4338
from LinuxQuestions.org on (#6E66J)
Quote:
$ sudo apt update
[sudo] password for bob:
Hit:1 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Get:3 https://typora.io/linux ./ InRelease [793 B]
Ign:4 http://ppa.launchpad.net/rvm/smplayer/ubuntu mantic InRelease
Hit:5 https://brave-browser-apt-release.s3.brave.com stable InRelease
Get:6 http://ppa.launchpad.net/diodon-team/stable/ubuntu mantic InRelease [17.5 kB]
Hit:7 https://repo.protonvpn.com/debian stable InRelease
Hit:8 http://deb.debian.org/debian bullseye-updates InRelease
Err:6 http://ppa.launchpad.net/diodon-team/stable/ubuntu mantic InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 751A20CF523884B2
Hit:9 http://mirrors.piconets.webwerks.in/...ckages/mx/repo bullseye InRelease
Hit:10 http://deb.debian.org/debian bullseye InRelease
Err:11 http://ppa.launchpad.net/rvm/smplayer/ubuntu mantic Release
404 Not Found [IP: 2620:2d:4000:1::3e 80]
Hit:12 https://apt.syncthing.net syncthing InRelease
Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://brave-browser-apt-release.s3.brave.com stable InRelease' doesn't support architecture 'i386'
W: GPG error: http://ppa.launchpad.net/diodon-team/stable/ubuntu mantic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 751A20CF523884B2
E: The repository 'http://ppa.launchpad.net/diodon-team/stable/ubuntu mantic InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/rvm/smplayer/ubuntu mantic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
(base) bob@bob:~
I am getting these errors when I try to update my MX-Linux system. Is this something to be worried about?
Should I remove the repositories and the applications which are causing this problem?

Also, will these errors exist even if I remove the application which needed the repository (as many errors are not being able to reach the repository.)

I usually install applications through my terminal as I find it to be easy, should I stop doing this and instead stick to mxpi-launcher (mx package installer)? I mean, I think I have added these repos which aren't right for my system because I basically copied and pasted what some random person wrote on the internet, it might have been right for his system, but not for mine.
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments