This is a clean stable 20.04 install of the Raspberry PI image.  $ sudo apt update [sudo] password for admn: Ign:1 http://ppa.launchpad.net/certbot/certbot/ubuntu focal InRelease Hit:2 http://ports.ubuntu.com/ubuntu-ports focal InRelease Get:3 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [106 kB] Err:4 http://ppa.launchpad.net/certbot/certbot/ubuntu focal Release   404  Not Found [IP: 2001:67c:1560:8008::15 80] Hit:5 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease Get:6 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [107 kB] Reading package lists... Done E: The repository 'http://ppa.launchpad.net/certbot/certbot/ubuntu focal Release' does not have a Release file. 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.   I would expect that this PPA should either not be included in the default image, or that the Release file should be there.  I suspect that this is a stripped-down Ubuntu server image, and that the PPA should not be included in the image.  But which, or another option?
952
When updating, I get the following error message:   W: The repository 'http://ppa.launchpad.net/mc3man/trusty-media/ubuntu xenial Release' does not have a Release file.   Here, I find another statement on this error:   This recommends removing certain PPAs; and, I'm not sure if I should do that since it might mean not getting the updates that I need.    Is this what I should do?
75647
There is no PPTP VPN in network manager connection type dialogue.  Packages pptp-linux network-manager-pptp are installed.
71967
I've noticed that running apt-get update recently has resulted in quite a few ppa's returning "403 Forbidden".  In and effort to clean them up I had a look:  W: Failed to fetch http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/dists/raring/main/binary-amd64/Packages  403  Forbidden  W: Failed to fetch http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/dists/raring/main/binary-i386/Packages  403  Forbidden  E: Some index files failed to download. They have been ignored, or old ones used instead.   The strange things is, if I copy these URLs into my browser I can access the files just fine.  Why would apt-get report "403 Forbidden" if they're still accessible?  I tried re-adding the ppa through add-apt-repository which downloads the signing key again, and it still reported "403 Forbidden".
85552
I am performing an update and its failing on the following:  The repository 'http://ppa.launchpad.net/izx/askubuntu/ubuntu xenial Release' does not have a Release file..   Running a local Ubuntu server 16.04
54551
I just installed a fresh version of Ubuntu 19.10 today, and the first thing I decided to do was to install GNU Screen, using sudo apt-get install screen. my output was: Reading package lists... Done Building dependency tree        Reading state information... Done E: Unable to locate package screen  I figured the package archives were not quite updated as it was a clean install so I tried sudo apt-get update. This is what I got: Get:1 http://security.ubuntu.com/ubuntu eoan-security InRelease [97.5 kB]       Err:2 http://au.archive.ubuntu.com/ubuntu eoan InRelease   Cannot initiate the connection to au.archive.ubuntu.com:80 (2001:388:30bc:cafe::beef). - connect (101: Network is unreachable) Could not connect to au.archive.ubuntu.com:80 (202.158.214.106), connection timed out Err:3 http://au.archive.ubuntu.com/ubuntu eoan-updates InRelease      Cannot initiate the connection to au.archive.ubuntu.com:80 (2001:388:30bc:cafe::beef). - connect (101: Network is unreachable) Err:4 http://au.archive.ubuntu.com/ubuntu eoan-backports InRelease   Cannot initiate the connection to au.archive.ubuntu.com:80 (2001:388:30bc:cafe::beef). - connect (101: Network is unreachable) Fetched 97.5 kB in 31s (3,106 B/s) Reading package lists... Done Building dependency tree        Reading state information... Done All packages are up to date. W: Failed to fetch http://au.archive.ubuntu.com/ubuntu/dists/eoan/InRelease  Cannot initiate the connection to au.archive.ubuntu.com:80 (2001:388:30bc:cafe::beef). - connect (101: Network is unreachable) Could not connect to au.archive.ubuntu.com:80 (202.158.214.106), connection timed out W: Failed to fetch http://au.archive.ubuntu.com/ubuntu/dists/eoan-updates/InRelease  Cannot initiate the connection to au.archive.ubuntu.com:80 (2001:388:30bc:cafe::beef). - connect (101: Network is unreachable) W: Failed to fetch http://au.archive.ubuntu.com/ubuntu/dists/eoan-backports/InRelease  Cannot initiate the connection to au.archive.ubuntu.com:80 (2001:388:30bc:cafe::beef). - connect (101: Network is unreachable) W: Some index files failed to download. They have been ignored, or old ones used instead.  I'm really not sure why it would be doing this, other than maybe some first-use hiccups? The computer is definitely connected to the internet, as I am writing this from that machine, and I have tried running the commands after rebooting and it still gives the errors. I can't seem to be able to connect to au.archive.ubuntu.com at all. ping au.archive.ubuntu.com just sits there without a response. If anyone could help, that would be great! If any extra information is required I'd be happy to edit it into the question.
710
Update  appear to have been updated recently (as of writing this the last update appears to have taken place on 3rd of June) to include the following statement:  The -d switch is necessary to upgrade from Ubuntu 18.04 LTS as upgrades have not yet been enabled and will only be enabled after the first point release of 20.04 LTS.  Also note that .  TLDR (as of 15 Aug 2020):   is the canonical tracking document for the first Focal Fossa point-release (20.04.1). It’s a live document. The Ubuntu release team will be updating it as we work on releasing 20.04.1. […] Upgrades from 18.04 to 20.04.1 are still disabled as we are working through a few upgrade blockers   Edit The answers (so far) do not answer the question. The question is pretty simple. Ubuntu.com points to a &quot;FinalRelease&quot;, which turns out to be a &quot;Development Release&quot;, see evidence below. I'm not asking how and when to upgrade. I'm pointing out what seems to me to be an apparent inconcistency (in semantics, linguistics, logic) in the way Ubuntu names or labels its releases. From an answer to the question I'd except someone to pick up and acknowledge this inconsistency. An answer could start with a &quot;Yes, ...&quot; or a &quot;No, ...&quot;, for starters. (Moreover, a good answer could distinguish between the release being in dev stage and/or the upgrade process (e.g. from LTS to LTS) being in dev stage, if appropriate.) This question, as I see it, is not a duplicate. Futher, I think it is a question which deserves a non-patronizing answer. Thanks.   indicates that today (23rd April 2020) the new Ubuntu 20.04 LTS is to be released.  See &quot;condensed screenshot&quot; here:  Indeed, it seems that that's what happened, see  and :  However, when following the instructions to upgrade (from 18.04 LTS to 20.04 LTS) found  and elsewhere (edit: actually , too!), even prior to the July point release, I'm a bit confused to see that the instruction is to use update-manager -d which also points to the &quot;Development Release&quot; (see screenshot below) rather than the &quot;FinalRelease&quot; (see screenshot and link above). Is the &quot;Final Release&quot; (which I'm after) the/a &quot;Development Release&quot;? Why isn't it called something like &quot;Production Release&quot; or &quot;Final Release&quot;? When will it no longer be referred to as &quot;Development Release&quot;? In July? I'm confused :(
61079
I am running Ubuntu Bionic Beaver. I was trying to download the pantheon desktop environment on Ubuntu and it didn't work so I gave up. Now when I try to download themes or other things from the terminal I get an error code mentioning Elementary OS even though what I am downloading doesn't have to do with Elementary or pantheon. Here is what the terminal says:   jacob@jacob-MacBookPro:~$ sudo apt-add-repository ppa:tista/adapta -y …                                           E: The repository 'http://ppa.launchpad.net/elementary-os/testing/ubuntu bionic Release' does not have a Release file. 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. E: The repository 'http://ppa.launchpad.net/mpstark/elementary-tweaks-daily/ubuntu bionic Release' does not have a Release file. 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.
104098
Ubuntu 11.10 (oneiric ocelot): When I try to add a new ppa through add-apt-repository, it returns with:  rene@rene-MS-N104:~$ sudo add-apt-repository ppa:tualatrix/ppa Traceback (most recent call last):   File "/usr/bin/add-apt-repository", line 88, in &lt;module&gt;     ppa info = get_ppa_info_from_lp(usr, ppa_name)   File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 80, in get_ppa_info_from_lp     curl.perform() pycurl.error(35, 'gnutls_handshake() failed: A TLS packet with unexpected length was recieved.')   I'm fairly new to Ubuntu and am not sure how to proceed.
49885
I am using Ubuntu 16.04 Beta 2 at the moment and every time I try to update at home via sudo apt-get update or upgrade trough sudo apt-get upgrade I wont get any feedback. Even installing of anything will have the same result. It will just "hang up" on 0% while fetching data.  $ sudo apt-get update [sudo] password for niclas:  0% [Connecting to archive.ubuntu.com (2001:67c:1560:8001::11)] [Connecting to archive.canonical.com (2001:67c:1360:8c01::1b)]   I have no idea how to solve the problem. I already tried to ping6 archive.ubuntu.com with 100% packet loss while just ping wont have any loss.  I changed the DNS-Server (IPv4 &amp; IPv6) to Google's one no solution either.
33767
I tried sudo apt-get update in the new Windows Subsystem for Linux, but I get the following error:    The most relevant parts seem to be the "could not resolve" lines about Ubuntu servers, like:  Could not resolve 'archive.ubuntu.com'
54837
After installing Ubuntu 18.04 from the Windows store I open Bash and want to run sudo apt-get update, but this returns the following errors:  Err:1 http://security.ubuntu.com/ubuntu bionic-security InRelease   Connection failed [IP: 91.189.91.26 80] Err:2 http://archive.ubuntu.com/ubuntu bionic InRelease   Connection failed [IP: 91.189.88.162 80] Err:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease   Connection failed [IP: 91.189.88.161 80] Err:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease   Connection failed [IP: 91.189.88.162 80] Reading package lists... Done W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease  Connection failed [IP: 91.189.88.162 80] W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease  Connection failed [IP: 91.189.88.161 80] W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease  Connection failed [IP: 91.189.88.162 80] W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease  Connection failed [IP: 91.189.91.26 80] W: Some index files failed to download. They have been ignored, or old ones used instead.   When I open 91.189.91.26 in a browser, it shows the site without a problem.  Previously this worked without any problem, but I did a clean reinstall of Windows and now it doesn't work anymore. It seems some firewall or proxy issue, but I tried with the firewall disabled and I got the same result.  Any idea why this is happening? Maybe it is a 18.04 issue? If so, is it possible to return to 16.04 on Windows 10? Becasue I don't see a uninstall option.
3632
I've added many PPAs using the add-apt-repository command. Is there a simple way to remove these PPAs? I've checked in /etc/apt/sources.list for the appropriate deb lines but they aren't there.   This is on a server system so a command line solution would be great!
86889
Since I updated from Ubuntu 10.04 (Lucid Lynx) to Ubuntu 12.04 (Precise Pangolin), I am unable to access the device connected in /ttyUSB0 if I don't have root access.  To be more specific, I use a USB-to-serial com port converter to access and configure Cisco equipment with software called . It happens that, since I upgraded to 12.04, PuTTY only sees the connected device when I run it as gksudo putty. If not, it says "unable to connect to port /ttyUSB0".  I have managed to change the permissions via chmod 666, and it works, but if I disconnect the USB device and reconnect, it goes back to root only. How do I permanently allow non-root access? I have a clue it might be via  rules, but I have no idea how to do it.  Obs.: Manufacturer and drivers are "PROLIFIC"
106640
I saw this answer - , but the getdeb links seem to be broken or gone.  I also tried the appImage file for Linux here - , but it would not execute at all. (I did set the file properties to "executable".)  Also no results on Ubuntu package search.  So is there any currently available solution to run this on 16.04?
22928
I'm using an unsigned repo in Ubuntu 16.04 from Debian multimedia:  deb http://www.deb-multimedia.org jessie main   To install deb-multimedia-keyring, I'm running:  apt-get update &amp;&amp; apt-get install deb-multimedia-keyring -y   This gives an error:  W: GPG error: http://www.deb-multimedia.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117 E: The repository 'http://www.deb-multimedia.org jessie 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.
22461
Any questions relating to status updates, or asking if anything is going to be patched for these vulnerabilities should be closed as duplicates of this question.    are in the news right now and sound pretty severe. I don't see any security updates from Ubuntu that cover these vulnerabilities.  What is Ubuntu doing about these vulnerabilities, and what should Ubuntu users be doing?  These are CVE-2017-5753, CVE-2017-5715 and CVE-2017-5754.
55630
I tried the following but no use: sudo add-apt-repository ppa:fingerprint/fingerprint-gui sudo apt update sudo apt install libbsapi policykit-1-fingerprint-gui fingerprint-gui  I got this error: E: Unable to locate package policykit-1-fingerprint-gui E: Unable to locate package fingerprint-gui