Hello, You...

If you, like me, have experienced the "NOT AUTHENTICATE" hang-up in Synaptic Pkg Mgr here is how I fixed mine...
[EDIT] NB This thread/post started out saying "Not Authorized" which was incorrect, and has been adjusted to read NOT AUTHENTICATED.
.
The problem for me was that I added a new repository (repo) to get a printer driver. Since it was a recommended method on the Net, and set to a big player in printers, the repo seemed genuine (and I still think it is). I "assume" I added the repo structure correctly - although indications (ie the problem) might mean that I didn't. (There did not seem to be any problem with it at the time.)

At some stage later (possibly after I clicked a "reload" of pkgs) Synaptic Pkg Mgr would - after being opening and readied for downloads - do a first download OK, but then bark at any subsequent download. It would say that something was "NOT AUTHENTICATED", and have one or more blank/empty lines after that notice. This symptom would occur every time I (re-)opened Synaptic Pkg Mgr.

I note this occurred even though I had "disabled" (ie unchecked) the repo site. [While there may be a reason for the initial problem (ie it might need some verifcation key) I had unchecked the repo - and therefore the problem should have been "nullified".]

My check on the Net forums showed this could have been a problem for (some) people since 2007. There were several solutions, each of which might prove to be right. Due to methodologies suggested in the fixes I decided on some other course of action.

What I did was this...

* Closed Synaptic Pkg Mgr.
* Opened Synaptic Pkg Mgr.
* In the "Sections" list I found Synaptic (itself) and marked it for "re-install".
* I did the re-install. (There was no "NOT AUTHENTICATED" notice.)
* Immediately upon completion notice I closed Synaptic Pkg Mgr.
* When I wanted to use Synaptic Mgr (ie test it) I opened it and did several installs - and without any problems showing up.

I hope that helps.

Regards,
aka boombaby

Sorry, sorry, sorry. Mea culpa.

The aforementioned solution CANNOT be sustained. It seems to work fine after the re-install, BUT...

Once I click to "reload" the repos, the problem (ie the "NOT AUTHORIZED" warning) returns.

If I then remove/delete the sus repo (ie the one I added, which is the "suspect") the problem remains.

So, I must withdraw the "fix" as described and apologize for any inconvenience.

.
If anyone KNOWS a fix - ie without me going hunting several choices down again - then please provide it. It would be appreciated.

Otherwise I have to mark this thread as [FAILED] or [HOPELESS] or [PNEWBIE SPEWBIE] something else, because it CANNOT exist as a fix.

Regrets,
aka boombaby

If you have inxi installed, can you run inxi -r and paste the output here.

Just a note that nowhere in your post, sidebar profile or signature do you mention your distro. It's always useful to add this and the distro flavour to your profile (Quick Links->Edit your details->Distribution) as the info is often useful in attempting to solve problems.

Hello, hydrurga...

$ inxi -r
Repos: Active apt sources in file: /etc/apt/sources.list.d/antix.list
deb http://mx.debian.nz/antix/jessie/ jessie main nosystemd
Active apt sources in file: /etc/apt/sources.list.d/debian.list
deb http://ftp.au.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free

.
.
As well, here is the repo site that I had used, which had been removed prior to your request, and which made no difference to any eventual outcome:

http://download.ebz.epson.net/dsc/op/stable/debian/ distro: jessie sections: main

FYI
I use Antix-16 (xfce) on a regular basis because it has turned out to be a very workable distro. With only an "odd" thing happening once or twice it is more or less under test, but it is shaping up very well.
My die-hard distro - one that never gives up, is very stable, and extremely reliable - is Mageia-5.
I occasionally use reliable PuppyTahr-6 for any recovery and ops, especially related to trying-out other distros in my multi-distro setup. (I have wanted to use it a bit more often though.)

Regards,

Hi boombaby,

Could you please copy-paste the entire output from that command and surround it here with CODE tags (see the # on the icon bar). Many thanks.

Der? That was it, Bud. There ain't no more!

That was the only output from the inxi -r command?

Yep! [What do you get? (Indication OK, not actual output.)]

Regards,

So where did you get the

that you listed in your previous post?

The reason I asked you to paste the entire output was that the snippet above was incomplete.

.
Whoa! Misunderstanding (looks like).

The first post of output for "inxi -r" was the complete output. After your re-request for something extra, the second quoted post was telling you there was "no more". Perhaps I should have used English, instead of the funny/wierd post/quote. (Actually I put the "." (dot) in because using quotes with "nothing" in between didn't work.) I thought my indication in the second was that the original posted output was all there was.

OK; so if we take a step back to the nanosecond after I posted the original (complete) output, what's next?

Regards,

Oops sorry, it was my misunderstanding. I get to say mea culpa this time.

Those repos look fine.

I just downloaded the source code of the Synaptic Package Manager so I could have a look to see what was triggering the "Not Authorized" error/warning message. However, the word "authorized" can be found nowhere in the source code (I'm using 0.81.2).

So, what version of Synaptic are you using, and can you check to see that Synaptic and not some other underlying program is producing that message?

Also, can you try from the command line:

and list any errors/warnings here.

hydrurga,

Sorry for delay responding. (Power-outage lead directly to an unwanted side-track.)


Firstly, note that I mentioned a "not authorized" notification however the actual notice is "NOT AUTHENTICATED". (Memory fade.) So I have adjusted the subject-line accordingly too. (Sorry AGAIN to all.)


The aforementioned power outage occurred while I was logged into LQ, so the implications of that are interesting (to me).

At the time I was checking Synaptics usage. It had downloaded packages multiple times without any problem - so that's puzzling. I was preparing to respond to you about that, but decided to do so AFTER a "reload repo info" check. However, as I was about to click RELOAD PACKAGES... ...phsssft. (No power.)

Now after the re-start, and clicking RELOAD PKGS, then afterwards attempting another download, the "NOT AUTHENTICATED" problem/notication popped up. (Attached is the screenshot.)


Note well, my Synaptics Mgr is exactly same version number that you have.

(I prefer not doing any update/check until you've had time to digest this info, and consider next step.)


Regards,
aka boombaby

Attached Thumbnails

 

Thanks.

Can you please generate the warning message again, then click the small arrows beside "NOT AUTHENTICATED", "To be installed" and "Unchanged" and post a screen shot so we can see which packages are involved.

The reason I've also asked for the "Unchanged" is that it's interesting that you have 23 packages held back and it would be good to sort that out too.

OK, hydrurga (et al), here's another "thing". When I started Synaptic Mgr and set up a download/install of a random pkg (ie Lincity) NO problems showed up. (As in the past, I expect that installation would have continued without incident.) However I cancelled the install, and unchecked the pkg. Then I did a "reload" of repos (ie click "reload"). After that I set up the same download (ie Lincity) and clicked Apply but this time the error (ie "NOT AUTHENICATED" showed up).

As far as your request, stop me if I am wrong but the fact that packages remain "unchanged" implies that dependencies in existing packages (in the system) are satisfactory to support the new download - doesn't it? Isn't that normal?

Anyway I have attached the screenshot of the warning "NOT AUTHENTICATED" notice (ie expanded, as requested) showing a blank line (but this can be more than one) and the pkg "to be installed" (ie expanded), but it can't include the full "unchanged" list within the screenshot. Anyway, at the moment I need convincing that attaching the long list is relevant in the thread, and have not included it yet.

Can you see how you go with that?

Regards,

There's no screenshot attached.