WARNING: The following packages cannot be authenticated!

happydog500 · 10-03-2016, 12:51 AM

Using Mint 17.3, I use k3b for burning. I needed to noralize the files. When I checked the box, I got a message that said it can't do that unless I install "normalize audio."

It showed I can get it by opening up a terminal and running,"sudo apt-get install normalize-audio". I did and got this,

Code:

sudo apt-get install normalize-audio
[sudo] password for xxxx: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libaudiofile1
Suggested packages:
  mpg321
Recommended packages:
  vorbis-tools flac
The following NEW packages will be installed:
  libaudiofile1 normalize-audio
0 upgraded, 2 newly installed, 0 to remove and 9 not upgraded.
Need to get 148 kB of archives.
After this operation, 470 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
WARNING: The following packages cannot be authenticated!
  libaudiofile1
Install these packages without verification? [y/N]

Should I be worried about the "WARNING: The following packages cannot be authenticated!"?

Thank you,
Chris.

ondoho · 10-03-2016, 01:22 AM

linux mint.
hmmm. (*)
i think you should use the graphical software updater (or whatever it's called) to update & upgrade your system.
does the error persist after that?

(*) it is not recommend to update your system with command line apt-get, because linux mint has its own secure updates mechanism...

happydog500 · 10-03-2016, 01:31 AM

I got k3b from the package manager in Mint. I was following directions from the software I was using.

Chris.

sundialsvcs · 10-03-2016, 12:28 PM

You should stop and check the distro's support forums.

All of the packages produced by a distro should be digitally signed by the publisher of that distro. You should not install a package that comes from their site if it does not pass digital-signature verification.

However, you do need to make sure that your updater is up-to-date: that is to say, that it contains the most-recent set of digital public keys. (Perhaps the package has been legitimately signed using an authorized key that you do not yet have?)

If this is the case, then I suggest that you stop and open a support-ticket with the distro publisher, asking that the signature problem be checked. All packages ought to be properly signed, of course, but there are thousands of them . . .

happydog500 · 10-03-2016, 02:17 PM

Thank you for the reply. I took your advice. Thank you.

You can post in the distro publisher forum and not get an answer, then post here and get 3 in one day that solve the problem.

Chris.

sundialsvcs · 10-03-2016, 08:35 PM

"Hey, let's just be easy on 'em ..."

He who can say that he has not "been there, answered that pager," let him cast the first stone.

ondoho · 10-05-2016, 01:14 AM

Quote:

Originally Posted by happydog500

I took your advice. Thank you.

sundialcvs gave you a detailed answer with about 3 seperate things that should be done, and that is all?

it makes me wonder if you did any of these things at all, but call me misanthropic if you like.

anyhow, why don't you describe the process in much more detail, so that other people that have the same or similar problems can find this thread and apply the solutions?

happydog500 · 10-06-2016, 07:16 PM

Quote:

Originally Posted by ondoho

sundialcvs gave you a detailed answer with about 3 seperate things that should be done, and that is all?

it makes me wonder if you did any of these things at all, but call me misanthropic if you like.

anyhow, why don't you describe the process in much more detail, so that other people that have the same or similar problems can find this thread and apply the solutions?

If you where misanthropic, I wouldn't call you that. I don't want to.

I got slammed with stuff, best friend is in the hospital, car problems, one of the three 3 things suggested take time, and has to rely on others. No control over that. Home now, going through emails.

Wish you where that supportive, of me, when I got no answers to other way bigger problems.

Thank you for backing up a fellow Linux user by getting me into gear.

Chris.

ondoho · 10-07-2016, 01:00 PM

deleted.

replica9000 · 10-08-2016, 07:54 PM

What does apt-cache policy libaudiofile1 output?

Habitual · 10-09-2016, 01:48 PM

Quote:

Originally Posted by ondoho

linux mint.
hmmm. (*)
i think you should use the graphical software updater (or whatever it's called) to update & upgrade your system.
does the error persist after that?

(*) it is not recommend to update your system with command line apt-get, because linux mint has its own secure updates mechanism...

since LinuxMint 17.x is 'based on' Ubu 14.x,

17.x should spew:

Code:

apt-cache policy libaudiofile1
libaudiofile1:
  Installed: (none)
  Candidate: 0.3.6-2ubuntu0.14.04.1
  Version table:
     0.3.6-2ubuntu0.14.04.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
     0.3.6-2 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

The OPs result should be identical.

If not, foreign PPA/source/deb?

Code:

inxi -R | pastebin

and paste the resulting link.

Thank You.

replica9000 nailed it.

happydog500 · 10-09-2016, 11:18 PM

The output I got was this;

Code:

~ $  apt-cache policy libaudiofile1
libaudiofile1:
  Installed: 0.3.6-2ubuntu0.14.04.1
  Candidate: 0.3.6-2ubuntu0.14.04.1
  Version table:
 *** 0.3.6-2ubuntu0.14.04.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
        100 /var/lib/dpkg/status
     0.3.6-2 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

Thank you for replying to this,

Chris.

Habitual · 10-10-2016, 06:07 AM

Chris:
Thanks. I blew it, please paste the resulting link from

Code:

inxi -Sr | pastebin

happydog500 · 10-10-2016, 08:00 PM

Quote:

Originally Posted by Habitual

Chris:
Thanks. I blew it, please paste the resulting link from

Code:

inxi -Sr | pastebin

Here's what I got. Thank you for replying.

Code:

~ $ inxi -Sr | pastebin
https://gist.github.com/52825339d80bec3afff57365493e7fcc

Chris.

Habitual · 10-11-2016, 08:21 AM

You're very welcome Chris.
Here's what I see: extraneous ppa/sources.

Since libaudiofile1 is already installed it is interesting that

Code:

sudo apt-get install normalize-audio

identifies libaudiofile1 as both "NEW" and "extra".

Here's my estimate of the problem.
You have mixed repos, or a FrankenMint. No harm no foul. Stuff happens.
I'd run

Code:

mintsources

in terminal and it will prompt you for privilege escalation
I would then navigate to the PPAs tab and disable all foreign repos (They can remain, just disable them)
and lastly, hit the "update the cache" button/function.

During the "update the cache" routine, you get a new window and if it errors, it may be shown.
No worries.
the "update the cache" button is pretty much the same as

Code:

sudo apt-get update

Close Mintsources and in terminal you may see (ignore these...)

Code:

(gksu:16517): Gtk-WARNING **: Unable to locate theme engine in module_path: "oxygen-gtk",

(synaptic:16551): Gtk-CRITICAL **: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed

It's a non-issue.

Now run in your terminal:

Code:

sudo apt-get install normalize-audio

If after the install is successful, don't be too hasty to re-enable those disabled repos.
This time enable one at a time and hit the "update the cache" button each time a new one is enabled and the problem
child should make itself known.

Please let us know.