MX Linux Forum

zukahn1 wrote: Tue Aug 27, 2019 10:12 pm Have come across one minor issue Chromium won't start after install click on icon and nothing happens running on USB everything else and the other browsers work fine on a couple of different computers.

Hit:1 http://deb.debian.org/debian buster-updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://linux.teamviewer.com/deb stable InRelease
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Get:5 http://shop.softmaker.com/repo/apt wheezy InRelease [2,322 B]
Hit:6 http://iso.mxrepo.com/antix/buster buster InRelease
Hit:7 http://mxrepo.com/mx/repo buster InRelease
Err:5 http://shop.softmaker.com/repo/apt wheezy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3413DA98AA3E7F5E
Hit:8 https://packagecloud.io/AtomEditor/atom/any any InRelease
Reading package lists... Done
W: GPG error: http://shop.softmaker.com/repo/apt wheezy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3413DA98AA3E7F5E
E: The repository 'http://shop.softmaker.com/repo/apt wheezy 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.

https://atom.io/

AK-47 wrote: Wed Aug 28, 2019 2:20 am The softmaker.com repos are not official Debian or MX repos. We can't guarantee that the softmaker.com repos will work, and if something breaks, we may not be able to support them.

However it sounds like you don't have a public key for those repos installed. You need to get the public key for those repos from SoftMaker and install it using sudo apt key add <gpg-key-file> and then run sudo apt update to sync it all up.

Eadwine Rose wrote: Tue Aug 27, 2019 9:40 am I encountered a little looks thing, moved the panel to the bottom and got this. The wired Synaptic icon behaved the same way.

Screenshot.png

zebedeeboss wrote: Wed Aug 28, 2019 2:31 amThanks - I do understand that - however you are proving the installation process via the MX Package Installer - so that method should work? Should it not ?

Regards Zeb

AK-47 wrote: Wed Aug 28, 2019 3:01 am

zebedeeboss wrote: Wed Aug 28, 2019 2:31 amThanks - I do understand that - however you are proving the installation process via the MX Package Installer - so that method should work? Should it not ?

Regards Zeb

The installation process via MX Package Installer should work, and by all means if your package presents an issue with MXPI then please report it to us as well as what package you're trying to install.
However because the package comes from a foreign (non-Debian, non-MX repo), once it's installed, we can try to help to a limited extent, but we can't guarantee any results.

Err:5 http://shop.softmaker.com/repo/apt wheezy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3413DA98AA3E7F5E
Hit:8 https://packagecloud.io/AtomEditor/atom/any any InRelease
Reading package lists... Done
W: GPG error: http://shop.softmaker.com/repo/apt wheezy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3413DA98AA3E7F5E
E: The repository 'http://shop.softmaker.com/repo/apt wheezy 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.