[YAY - SOLVED] "NOT AUTHENTICATED" in Synaptics Pkg Mgr, then Repo key failure
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Oops; here's the screenshot (unsure what happened there)...
It is a little fortunate that my screenshot wasn't included (not by design) because I was unaware that Synaptics' "Apply Changes (Summary)" lists box could be easily expanded to show the whole list by simply opening up the whole window. I discovered that after doing the following...
*
I also commenced discussion about this error in the Antix forum since it is occurring under their distro - ALTHOUGH it may NOT be distro-based. Antix is a non-systemd environ and that MIGHT be significant. I just don't know. (Personally, I am happy to see both forums go at this, since resolution will benefit both groups.)
My recent response in that other thread has a bit more finer-grained detail ONLY because of the points put to me (to respond). So, in laying out a concise sequence of events for them to understand it might ALSO be a bit more clearer for you too. In particular, the last bits of info there - particularly about "clicking on the 'show screenshot' button after which the error re-occurs" - might be relevant.
If you manage to read that forum BUT respond in LQ with any info/resolution please do so.
[Again, "hydrurga" (et al), my only reason for going down that path was that I thought it's their distro and they may have a quicker technical understanding of what's going on "underneath" the desktop.]
Here's the screenshot (of the error being generated), and includes the full "unchanged" list...
When you set up a PPA, you also have to set up the authentication key for that PPA. If you install the PPA using add-apt-repository ppa:ppa_name, then it will automatically do that for you. If however you manually add the PPA into Software Sources then you also have to download the key with something like sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys key-id.
If one of the PPAs that you are using doesn't have an authentication key set up for it, then you will get the "Not Authenticated" error.
The fact that your package system is generating that error, but is not listing the problem package, indicates that your package database could well be garbled somehow. I was hoping that listing the repos earlier with the inxi command earlier on would show the PPA that was to blame but it didn't.
So, what you need to do first of all is go into the Synaptic Package Manager and choose Settings->Repositories (which opens up Software Sources). Then check the PPA, Additional Repositories and Authentication Keys sections - do these contain any entries at all?
Ah, my bad. I had forgotten that PPAs were a Ubuntu "add-on".
I'll have to leave you to the AntiX/Debian crew then.
However, as it remains, it appears that you have some sort of weirdness going on in your package database. You appear to have an unnamed repo that's missing or has a bad authentication key. You also have a significant number of packages "held back", which probably means that, because of changing dependencies, more up-to-date versions of the packages exist but apt-get won't upgrade them because to do so it would have to install a new package(s).
That's nice of you to say so, boombaby, but I feel like I've let you down by not solving the problem. Hopefully however you'll find resolution elsewhere. Don't give up. :-) Oh, and as a general rule, keep on top of those dependencies and held back packages. If sudo apt-get upgrade ever reports that you have packages held back, investigate it at the time and find out what's causing it. It stops the string getting tied into knots as time goes on.
Nope. Any help where you learn something, in my opinion, is good help. You did your best, and I learned stuff. That's all I can ask. You did not resolve the "NOT AUTHENTICATED" notification, BUT you did NOT fail me. Anyway I might be totally ignorant even if you did provide the solution. (P.S. That happened to me in an Antix Forum thread. Very embarrassing too.) Rest easy, hydrurga. Thanks.
.
hydrurga, I have the feeling that YOU were on the right track in post #17. (Whether that ultimately WAS the solution, sorry, I just can't tell. In that post when I did not understand the "PPA's" etc, I wasn't sure what was happening. Then you advised me you were using a different distro, and I balked. However I feel that if I had understood things (CLI etc) a bit better therein, or better across distros, you might have nailed it for me. (In the Antix forum I rounded up the fix in my last post today.) Thanks.
Great. So it *was* an authentication key error, but associated with one of your main repos. I've never seen that before in my limited experience, but I'll sure as heck remember it now. Have fun!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.