apt-get update fails for missing GPG keys but keys are present
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I am trying to run apt-get update on a newly upgraded to 16.04 machine.
It complains about missing keys. But when I query apt-key it shows the keys as present. I have tried removing the keys and getting them again but I still get the errors.
Here is the output of apt-get update:
# apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Err:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
trimmed to remove what looked like excessive links to avoid the
"You need at least 10 reputation to post more than 8 links." message
And here is the output of apt-key list:
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/FBB75451 2004-12-30
uid Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>
pub 4096R/EFE21092 2012-05-11
uid Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>
pub 1024D/437D05B5 2004-09-12
uid Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
sub 2048g/79164387 2004-09-12
pub 4096R/C0B21F32 2012-05-11
uid Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>
I have even tried taking the /etc/apt/trusted.gpg file from this machine and moved it to another machine and it works fine there.
ETA:
The /etc/apt/trusted.gpg.d directory is empty.
apt
edited May 4 at 15:32
danzel
1,346512
asked May 4 at 13:51
John DeHart
63
add a comment |Â
up vote
1
down vote
favorite
I am trying to run apt-get update on a newly upgraded to 16.04 machine.
It complains about missing keys. But when I query apt-key it shows the keys as present. I have tried removing the keys and getting them again but I still get the errors.
Here is the output of apt-get update:
# apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Err:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
trimmed to remove what looked like excessive links to avoid the
"You need at least 10 reputation to post more than 8 links." message
And here is the output of apt-key list:
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/FBB75451 2004-12-30
uid Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>
pub 4096R/EFE21092 2012-05-11
uid Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>
pub 1024D/437D05B5 2004-09-12
uid Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
sub 2048g/79164387 2004-09-12
pub 4096R/C0B21F32 2012-05-11
uid Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>
I have even tried taking the /etc/apt/trusted.gpg file from this machine and moved it to another machine and it works fine there.
ETA:
The /etc/apt/trusted.gpg.d directory is empty.
apt
edited May 4 at 15:32
danzel
1,346512
asked May 4 at 13:51
John DeHart
63
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to run apt-get update on a newly upgraded to 16.04 machine.
It complains about missing keys. But when I query apt-key it shows the keys as present. I have tried removing the keys and getting them again but I still get the errors.
Here is the output of apt-get update:
# apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Err:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
trimmed to remove what looked like excessive links to avoid the
"You need at least 10 reputation to post more than 8 links." message
And here is the output of apt-key list:
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/FBB75451 2004-12-30
uid Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>
pub 4096R/EFE21092 2012-05-11
uid Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>
pub 1024D/437D05B5 2004-09-12
uid Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
sub 2048g/79164387 2004-09-12
pub 4096R/C0B21F32 2012-05-11
uid Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>
I have even tried taking the /etc/apt/trusted.gpg file from this machine and moved it to another machine and it works fine there.
ETA:
The /etc/apt/trusted.gpg.d directory is empty.
apt
edited May 4 at 15:32
danzel
1,346512
asked May 4 at 13:51
John DeHart
63
I am trying to run apt-get update on a newly upgraded to 16.04 machine.
It complains about missing keys. But when I query apt-key it shows the keys as present. I have tried removing the keys and getting them again but I still get the errors.
Here is the output of apt-get update:
# apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Err:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
trimmed to remove what looked like excessive links to avoid the
"You need at least 10 reputation to post more than 8 links." message
And here is the output of apt-key list:
# apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/FBB75451 2004-12-30
uid Ubuntu CD Image Automatic Signing Key <cdimage@ubuntu.com>
pub 4096R/EFE21092 2012-05-11
uid Ubuntu CD Image Automatic Signing Key (2012) <cdimage@ubuntu.com>
pub 1024D/437D05B5 2004-09-12
uid Ubuntu Archive Automatic Signing Key <ftpmaster@ubuntu.com>
sub 2048g/79164387 2004-09-12
pub 4096R/C0B21F32 2012-05-11
uid Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>
I have even tried taking the /etc/apt/trusted.gpg file from this machine and moved it to another machine and it works fine there.
ETA:
The /etc/apt/trusted.gpg.d directory is empty.
apt
edited May 4 at 15:32
danzel
1,346512
asked May 4 at 13:51
John DeHart
63
edited May 4 at 15:32
danzel
1,346512
edited May 4 at 15:32
danzel
1,346512
edited May 4 at 15:32
danzel
1,346512
1,346512
asked May 4 at 13:51
John DeHart
63
asked May 4 at 13:51
John DeHart
63
asked May 4 at 13:51
John DeHart
63
63
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
Looks like it was the permissions on the /etc/apt directory.
Somehow it got set to 700 . On working machines it was 755. When I changed it to 755 on my newly upgraded machine it worked fine.
answered May 4 at 22:22
John DeHart
63
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Looks like it was the permissions on the /etc/apt directory.
Somehow it got set to 700 . On working machines it was 755. When I changed it to 755 on my newly upgraded machine it worked fine.
answered May 4 at 22:22
John DeHart
63
add a comment |Â
up vote
0
down vote
Looks like it was the permissions on the /etc/apt directory.
Somehow it got set to 700 . On working machines it was 755. When I changed it to 755 on my newly upgraded machine it worked fine.
answered May 4 at 22:22
John DeHart
63
add a comment |Â
up vote
0
down vote
up vote
0
down vote
Looks like it was the permissions on the /etc/apt directory.
Somehow it got set to 700 . On working machines it was 755. When I changed it to 755 on my newly upgraded machine it worked fine.
answered May 4 at 22:22
John DeHart
63
Looks like it was the permissions on the /etc/apt directory.
Somehow it got set to 700 . On working machines it was 755. When I changed it to 755 on my newly upgraded machine it worked fine.
answered May 4 at 22:22
John DeHart
63
answered May 4 at 22:22
John DeHart
63
answered May 4 at 22:22
John DeHart
63
answered May 4 at 22:22
John DeHart
63
63
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1031997%2fapt-get-update-fails-for-missing-gpg-keys-but-keys-are-present%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password