Sfdwhf

How big is a framed opening for a door relative to the finished door opening width?

Stuck on a Geometry Puzzle

How are the system health extended events files rolling over?

Custom shape shows unwanted extra line

Does Skippy chunky peanut butter contain trans fat?

Does it take energy to move something in a circle?

Why did Luke use his left hand to shoot?

What is a good reason for every spaceship to carry a weapon on board?

Can we "borrow" our answers to populate our own websites?

Concatenating two int[]

Not a Long-Winded Riddle

How do you get out of your own psychology to write characters?

Why is that max-Q doesn't occur in transonic regime?

Article. The word "Respect"

Is there a file that always exists and a 'normal' user can't lstat it?

Is there a way to not have to poll the UART of an AVR?

I have trouble understanding this fallacy: "If A, then B. Therefore if not-B, then not-A."

Does an Eldritch Knight's Weapon Bond protect him from losing his weapon to a Telekinesis spell?

Website seeing my Facebook data?

Is there a way to store 9th-level spells in a Glyph of Warding or similar method?

What species should be used for storage of human minds?

What is the wife of a henpecked husband called?

Why does 0.-5 evaluate to -5?

What to do with threats of blacklisting?

Unable to update Ubuntu 18.04

How do I fix the GPG error “NO_PUBKEY”?W: GPG error: http://ppa.launchpad.net lucid Release:error message with apt-get update commandIs this an error => Starting pkgProblemResolver with broken count: 0Software Updater gives “Failed to download repository information - Public key is not available” Ubuntu 17.10Software Updater crashesappstreamcli: AppStream system cache was updated, but problems were found: Metadata files have errors: /var/cache/app-info/xmls/fwupd.xmlUbuntu server 18.04 LTS apt unable updateUbuntu 18.04.1 repositores are not workingCannot add ppa:graphics-drivers

0

When I run the command: root@versinator:~# apt-get update
I get the following error:

Hit:1 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic InRelease

Hit:2 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates InRelease

Hit:3 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-backports InRelease

Hit:4 http://archive.canonical.com/ubuntu bionic InRelease

Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease

Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu bionic InRelease

Get:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease [17.5 kB]

Err:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease

  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

Reading package lists... Done

W: GPG error: http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

E: The repository 'http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial 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.

How can I remove this error and get back to the secured state?

apt 18.04 updates ppa update-manager

share|improve this question

asked Jan 31 at 14:55

aviral sanjayaviral sanjay

1012

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Looks like you unwisely added a Xenial (16.04) PPA to a Bionic (18.04) system. Remove it.
  
  – user535733
  Jan 31 at 15:58
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How can I remove it?
  
  – aviral sanjay
  Jan 31 at 16:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How did you add it?
  
  – user535733
  Jan 31 at 16:54
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I can't actually remember but most prolly it was: ` && apt-add-repository -y 'deb ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial main' `
  
  – aviral sanjay
  Jan 31 at 17:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Then look up man apt-add-repository to see how to remove it.
  
  – user535733
  Jan 31 at 17:58
  
  
  

  
  
  
  

add a comment | 

0

When I run the command: root@versinator:~# apt-get update
I get the following error:

Hit:1 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic InRelease

Hit:2 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates InRelease

Hit:3 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-backports InRelease

Hit:4 http://archive.canonical.com/ubuntu bionic InRelease

Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease

Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu bionic InRelease

Get:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease [17.5 kB]

Err:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease

  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

Reading package lists... Done

W: GPG error: http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

E: The repository 'http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial 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.

How can I remove this error and get back to the secured state?

apt 18.04 updates ppa update-manager

share|improve this question

asked Jan 31 at 14:55

aviral sanjayaviral sanjay

1012

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  Looks like you unwisely added a Xenial (16.04) PPA to a Bionic (18.04) system. Remove it.
  
  – user535733
  Jan 31 at 15:58
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How can I remove it?
  
  – aviral sanjay
  Jan 31 at 16:43
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  How did you add it?
  
  – user535733
  Jan 31 at 16:54
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I can't actually remember but most prolly it was: ` && apt-add-repository -y 'deb ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial main' `
  
  – aviral sanjay
  Jan 31 at 17:39
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Then look up man apt-add-repository to see how to remove it.
  
  – user535733
  Jan 31 at 17:58
  
  
  

  
  
  
  

add a comment | 

When I run the command: root@versinator:~# apt-get update
I get the following error:

Hit:1 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic InRelease

Hit:2 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates InRelease

Hit:3 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-backports InRelease

Hit:4 http://archive.canonical.com/ubuntu bionic InRelease

Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease

Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu bionic InRelease

Get:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease [17.5 kB]

Err:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease

  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

Reading package lists... Done

W: GPG error: http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

E: The repository 'http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial 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.

How can I remove this error and get back to the secured state?

apt 18.04 updates ppa update-manager

share|improve this question

asked Jan 31 at 14:55

aviral sanjayaviral sanjay

1012

Hit:1 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic InRelease

Hit:2 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-updates InRelease

Hit:3 http://us-east1.gce.archive.ubuntu.com/ubuntu bionic-backports InRelease

Hit:4 http://archive.canonical.com/ubuntu bionic InRelease

Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease

Hit:7 http://ppa.launchpad.net/webupd8team/y-ppa-manager/ubuntu bionic InRelease

Get:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease [17.5 kB]

Err:5 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease

  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

Reading package lists... Done

W: GPG error: http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1E9377A2BA9EF27F

E: The repository 'http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial 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.

share|improve this question

asked Jan 31 at 14:55

aviral sanjayaviral sanjay

1012

share|improve this question

asked Jan 31 at 14:55

aviral sanjayaviral sanjay

1012

asked Jan 31 at 14:55

aviral sanjayaviral sanjay

1012

asked Jan 31 at 14:55

aviral sanjayaviral sanjay

1012

3 Answers
3

active

oldest

votes

0

Edit the file :

sudo nano /etc/apt/sources.list

Put a # as the first character on the line.

The do a :

sudo apt update

If the errors disappear you can remove the remarked lines.

share|improve this answer

answered Jan 31 at 20:02

MatsKMatsK

471211

add a comment | 

0

Go to synaptic then settings tab repositories then other software. uncheck the box in front of the ppa for Ubuntu-toolchain-r. the reload.

share|improve this answer

answered Jan 31 at 20:34

kc1dikc1di

845

add a comment | 

0

The issue of "apt-get update" is that you are missing the public key 1E9377A2BA9EF27F. You can add this key to your keyring through executing:

sudo apt-key adv --recv-key 1E9377A2BA9EF27F

It will show you something like:

Executing: /tmp/apt-key-gpghome.IA65nrxcnz/gpg.1.sh --recv-key 1E9377A2BA9EF27F

gpg: key 1E9377A2BA9EF27F: public key "Launchpad Toolchain builds" imported

gpg: Total number processed: 1

gpg:               imported: 1

Now you can run "apt-get update", or "apt update" and it will fetch the index of "http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease" as well.

share|improve this answer

answered 6 hours ago

PixelschleuderPixelschleuder

1

New contributor

Pixelschleuder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1114438%2funable-to-update-ubuntu-18-04%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

Edit the file :

sudo nano /etc/apt/sources.list

Put a # as the first character on the line.

The do a :

sudo apt update

If the errors disappear you can remove the remarked lines.

share|improve this answer

answered Jan 31 at 20:02

MatsKMatsK

471211

add a comment | 

0

Edit the file :

sudo nano /etc/apt/sources.list

Put a # as the first character on the line.

The do a :

sudo apt update

If the errors disappear you can remove the remarked lines.

share|improve this answer

answered Jan 31 at 20:02

MatsKMatsK

471211

add a comment | 

Edit the file :

sudo nano /etc/apt/sources.list

Put a # as the first character on the line.

The do a :

sudo apt update

If the errors disappear you can remove the remarked lines.

share|improve this answer

answered Jan 31 at 20:02

MatsKMatsK

471211

sudo nano /etc/apt/sources.list

sudo apt update

share|improve this answer

answered Jan 31 at 20:02

MatsKMatsK

471211

answered Jan 31 at 20:02

MatsKMatsK

471211

answered Jan 31 at 20:02

MatsKMatsK

471211

0

Go to synaptic then settings tab repositories then other software. uncheck the box in front of the ppa for Ubuntu-toolchain-r. the reload.

share|improve this answer

answered Jan 31 at 20:34

kc1dikc1di

845

add a comment | 

0

Go to synaptic then settings tab repositories then other software. uncheck the box in front of the ppa for Ubuntu-toolchain-r. the reload.

share|improve this answer

answered Jan 31 at 20:34

kc1dikc1di

845

add a comment | 

Go to synaptic then settings tab repositories then other software. uncheck the box in front of the ppa for Ubuntu-toolchain-r. the reload.

share|improve this answer

answered Jan 31 at 20:34

kc1dikc1di

845

share|improve this answer

answered Jan 31 at 20:34

kc1dikc1di

845

answered Jan 31 at 20:34

kc1dikc1di

845

answered Jan 31 at 20:34

kc1dikc1di

845

0

The issue of "apt-get update" is that you are missing the public key 1E9377A2BA9EF27F. You can add this key to your keyring through executing:

sudo apt-key adv --recv-key 1E9377A2BA9EF27F

It will show you something like:

Executing: /tmp/apt-key-gpghome.IA65nrxcnz/gpg.1.sh --recv-key 1E9377A2BA9EF27F

gpg: key 1E9377A2BA9EF27F: public key "Launchpad Toolchain builds" imported

gpg: Total number processed: 1

gpg:               imported: 1

Now you can run "apt-get update", or "apt update" and it will fetch the index of "http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease" as well.

share|improve this answer

answered 6 hours ago

PixelschleuderPixelschleuder

1

New contributor

Pixelschleuder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

0

The issue of "apt-get update" is that you are missing the public key 1E9377A2BA9EF27F. You can add this key to your keyring through executing:

sudo apt-key adv --recv-key 1E9377A2BA9EF27F

It will show you something like:

Executing: /tmp/apt-key-gpghome.IA65nrxcnz/gpg.1.sh --recv-key 1E9377A2BA9EF27F

gpg: key 1E9377A2BA9EF27F: public key "Launchpad Toolchain builds" imported

gpg: Total number processed: 1

gpg:               imported: 1

Now you can run "apt-get update", or "apt update" and it will fetch the index of "http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease" as well.

share|improve this answer

answered 6 hours ago

PixelschleuderPixelschleuder

1

New contributor

Pixelschleuder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

The issue of "apt-get update" is that you are missing the public key 1E9377A2BA9EF27F. You can add this key to your keyring through executing:

sudo apt-key adv --recv-key 1E9377A2BA9EF27F

It will show you something like:

Executing: /tmp/apt-key-gpghome.IA65nrxcnz/gpg.1.sh --recv-key 1E9377A2BA9EF27F

gpg: key 1E9377A2BA9EF27F: public key "Launchpad Toolchain builds" imported

gpg: Total number processed: 1

gpg:               imported: 1

Now you can run "apt-get update", or "apt update" and it will fetch the index of "http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial InRelease" as well.

share|improve this answer

answered 6 hours ago

PixelschleuderPixelschleuder

1

New contributor

Pixelschleuder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

sudo apt-key adv --recv-key 1E9377A2BA9EF27F

Executing: /tmp/apt-key-gpghome.IA65nrxcnz/gpg.1.sh --recv-key 1E9377A2BA9EF27F

gpg: key 1E9377A2BA9EF27F: public key "Launchpad Toolchain builds" imported

gpg: Total number processed: 1

gpg:               imported: 1

share|improve this answer

answered 6 hours ago

PixelschleuderPixelschleuder

1

New contributor

Pixelschleuder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 6 hours ago

PixelschleuderPixelschleuder

1

New contributor

Pixelschleuder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

answered 6 hours ago

PixelschleuderPixelschleuder

1