I have issues with updates for the OwnCloud desktop release:  teddy@Yoga-2:~$ sudo apt-get update --allow-unauthenticated [sudo] password for teddy:  Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Ign:2 http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_15.10  InRelease Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [94,5 kB] Get:4 http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_15.10  Release [1023 B] Get:5 http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_15.10  Release.gpg [189 B] Ign:5 http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_15.10  Release.gpg Hit:6 http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_15.10  Packages Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease Get:8 http://archive.ubuntu.com/ubuntu xenial-security InRelease [94,5 kB] Get:9 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [242 kB] Get:10 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [238 kB] Get:11 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [130 kB] Get:12 http://archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [127 kB] Fetched 927 kB in 0s (1111 kB/s)                           Reading package lists... Done W: GPG error: http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_15.10  Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 977C43A8BA684223 W: The repository 'http://download.opensuse.org/repositories/isv:/ownCloud:/desktop/Ubuntu_15.10  Release' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details.   This is no the first time I have issues updating Ownclous but this time I cannot resolve this. Can you please help? How do I authenticate explicitly the repo? P.S. Adding the GPG key as suggested does not resolve the issue. I remember adding it when installing the client.
3882
I added some extra repositories with the Software Sources program. But when I reload the package database, I get an error like the following:     W: GPG error:  trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8BAF9A6F   I know I can fix it using apt-key in a terminal, according to the official Ubuntu documentation. But I would have liked to do it graphically. Is there a way to do this without using a terminal?
15860
Are repository updates secure?  As a bear of little brain from the developer side, I cannot understand why the repository list is http://security.ubuntu.com and the other http(unsecured) sites listed in /etc/apt/sources.list.  Without a certificate chain match this appears as "ask any responder for a list of packages to update" instead of "ask the ubuntu.com site..."  Can any network choose to spoof the update sites, and is this a common practice to provide a locally cached and vetted copy?
96964
I'm trying to update from ubuntu 12.10 lately but I keep getting the "Failed to fetch" error.  W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/quantal-security/Release  Unable to find expected entry 'independent/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/quantal/Release  Unable to find expected entry 'independent/source/Sources' in Release file (Wrong sources.list entry or malformed file)  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/quantal-updates/Release  Unable to find expected entry 'independent/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/quantal-backports/Release  Unable to find expected entry 'independent/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)  E: Some index files failed to download. They have been ignored, or old ones used instead.   I changed the server and deleted the source lists from /var/lib/apt/lists/ like some answers say but still. This is really annoying.
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.
8121
I started setting up by adding repositories and then went to run a sudo apt-get update again before I started installing other software, and I get the Signature key lines and it stops. So it essentially won't let me update any packages now.  d@EliteBook:~/Downloads$ sudo apt-get update Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease Hit:2 http://dl.google.com/linux/chrome/deb stable Release                      Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease               Get:5 http://ca.archive.ubuntu.com/ubuntu xenial InRelease [247 kB] Hit:6 http://ca.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:7 http://ca.archive.ubuntu.com/ubuntu xenial-backports InRelease Fetched 247 kB in 0s (256 kB/s)                    Reading package lists... Done W: http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: Signature by  key 4CCA1EAF950CEE4AB83976DCA040830F7FAC5991 uses weak digest algorithm (SHA1) d@EliteBook:~/Downloads$   I've never seen this before whenever I setup and start installing things in Ubuntu. Is there something else I can do?
9997
I am wondering what sudo apt-get update does?  What does it update?
70813
I don't know what caused the following to happen:    The content of /etc/apt/sources-list.d/mono-xamarin.list is sudo apt-get update.
104258
I'm trying to do an apt-get update or apt-get install xyz and I'm seeing timeouts like this:  W: Failed to fetch http://eu-west-1.ec2.archive.ubuntu.com/ubuntu/dists/oneiric-updates/Release.gpg   Unable to connect to eu-west-1.ec2.archive.ubuntu.com:http: [IP: 10.224.87.159 80]   Is this a transient issue with Ubuntu, or maybe it's something on my end. The box I'm accessing it from is in EC2-EU.  Perhaps there is a way to force the installer to use the US servers which seem to work?
32564
I'be been running 18.04 since a clean SSD install on the day of it's official release, without issues. Power on to login was seconds (max 10)  Then, I did a regular upgrade this morning:  $ sudo apt update &amp;&amp; sudo apt dist-upgrade   The packages installed/upgraded were:  Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic) Upgrade: gnome-control-center-data:amd64 (1:3.28.1-0ubuntu1.18.04.1, 1:3.28.1-0ubuntu1.18.04.2), linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), gnome-control-center:amd64 (1:3.28.1-0ubuntu1.18.04.1, 1:3.28.1-0ubuntu1.18.04.2), linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-signed-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), gnome-control-center-faces:amd64 (1:3.28.1-0ubuntu1.18.04.1, 1:3.28.1-0ubuntu1.18.04.2), linux-generic:amd64 (4.15.0.23.25, 4.15.0.24.26)   I rebooted once the upgrade had completed, and noted a 2-3 minute delay on the Ubuntu loading/splash screen (prior to login) (without any progress/activity indicated on the dots).  I powered off and tried to boot again, but am getting this delay consistently now. Also close down is much slower too.  Update #1 (2018-07-03): Analysis on systemd:  $ sudo systemd-analyze blame 3min 53.073s plymouth-quit-wait.service     2min 20.699s snapd.seeded.service          49.949s snapd.service           6.186s NetworkManager-wait-online.service           1.148s dev-sda2.device           1.098s plymouth-start.service   Showing that plymouth-quit-wait.service (which I now believe is related to the Ubuntu loading/splash screen) and snapd.seeded.service were by far the longest running services to initiate. So I compared the times before the dist-upgrade and after:  $ journalctl -u plymouth-quit-wait.service --since today -- Logs begin at Fri 2018-04-27 13:01:30 BST, end at Tue 2018-07-03 12:38:05 BST. -- Jul 03 04:15:43 user-laptop systemd[1]: Starting Hold until boot process finishes up... Jul 03 04:15:46 user-laptop systemd[1]: Started Hold until boot process finishes up. -- Reboot -- Jul 03 04:21:17 user-laptop systemd[1]: Starting Hold until boot process finishes up... Jul 03 04:24:52 user-laptop systemd[1]: Started Hold until boot process finishes up.   Before the upgrade plymouth-quit-wait.service took 3 seconds. After the upgrade it took 3 minutes 35 seconds  $ journalctl -u snapd.seeded.service --since today -- Logs begin at Fri 2018-04-27 13:01:30 BST, end at Tue 2018-07-03 12:42:14 BST. -- Jul 03 04:15:43 user-laptop systemd[1]: Starting Wait until snapd is fully seeded... Jul 03 04:15:43 user-laptop systemd[1]: Started Wait until snapd is fully seeded. -- Reboot -- Jul 03 04:22:47 user-laptop systemd[1]: Starting Wait until snapd is fully seeded... Jul 03 04:24:49 user-laptop systemd[1]: Started Wait until snapd is fully seeded.   Before the upgrade snapd.seeded.service took 0 seconds. After the upgrade it took 2 minutes 2 seconds.  Update #2 (2018-07-06): This morning's boot saw the return of the delay. So I guess we're still waiting for the kernel/plymouth/snapd update.  Update #3 (2018-07-12): The problem seems to be resolved, but I didn't see any update to snap or plymouth, and I'm still running 4.15.0-24 kernel. So I'm not sure which package update fixed the problem, or if it just resolved itself somehow. Reading the bug updates on launchpad it's unclear to me what was done (or is being done) to what package/s. If anyone can clarify that would be very useful.
89523
I'm using Ubuntu 11.04. The update manager once found the new release 'oneiric', and still shows up this screen when I log on use ssh:  Welcome to Ubuntu 11.04 (GNU/Linux 2.6.38-14-generic x86_64)   * Documentation:  https://help.ubuntu.com/  0 packages can be updated. 0 updates are security updates.  New release 'oneiric' available. Run 'do-release-upgrade' to upgrade to it.  Last login: Wed Apr 25 16:22:48 2012 from ***   But I didn't upgrade then, and change my apt sources. And now I cannot upgrade to 'oneiric'. do-relase-upgrade shows:  $ sudo do-release-upgrade Checking for a new ubuntu release No new release found $   And apt-get dist-upgrade shows:  $ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. $   I can successfully update all my packages.    File contents of source.list:  $ cat /etc/apt/sources.list ## See sources.list(5) for more information, especialy # Remember that you can only use http, ftp or file URIs  deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty main universe restricted multiverse deb-src http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty main universe restricted multiverse deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty-security universe main multiverse restricted deb-src http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty-security universe main multiverse restricted deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty-updates universe main multiverse restricted deb-src http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty-updates universe main multiverse restricted deb http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty-backports universe main multiverse restricted deb-src http://mirrors.tuna.tsinghua.edu.cn/ubuntu/ natty-backports universe main multiverse restricted   # deb http://ubuntu.dormforce.net/ubuntu/ lucid main universe restricted multiverse # deb-src http://ubuntu.dormforce.net/ubuntu/ lucid main universe restricted multiverse # deb http://ubuntu.dormforce.net/ubuntu/ lucid-security universe main multiverse restricted # deb-src http://ubuntu.dormforce.net/ubuntu/ lucid-security universe main multiverse restricted # deb http://ubuntu.dormforce.net/ubuntu/ lucid-updates universe main multiverse restricted # deb-src http://ubuntu.dormforce.net/ubuntu/ lucid-updates universe main multiverse restricted  # CDROMs are managed through the apt-cdrom tool. # deb http://archive.canonical.com lucid partner # deb http://archive.canonical.com lucid-security partner # deb http://archive.canonical.com lucid-updates partner # deb-src http://archive.canonical.com lucid partner # deb-src http://archive.canonical.com lucid-security partner # deb-src http://archive.canonical.com lucid-updates partner   #medibuntu repo # deb http://packages.medibuntu.org/ lucid free non-free # deb-src http://packages.medibuntu.org/ lucid free non-free  # deb http://extras.ubuntu.com/ubuntu maverick main #Third party developers repository deb http://mirrors.sohu.com/ubuntu/ natty main restricted multiverse universe deb-src http://mirrors.sohu.com/ubuntu/ natty main universe restricted multiverse #Added by software-properties deb http://security.ubuntu.com/ubuntu/ natty-security universe main multiverse restricted deb-src http://mirrors.sohu.com/ubuntu/ natty-security universe main multiverse restricted deb http://mirrors.sohu.com/ubuntu/ natty-updates universe main multiverse restricted deb-src http://mirrors.sohu.com/ubuntu/ natty-updates universe main multiverse restricted   File contents of /etc/update-manager/meta-release:  $ cat /etc/update-manager/meta-release # default location for the meta-release file  [METARELEASE] URI = http://changelogs.ubuntu.com/meta-release URI_LTS = http://changelogs.ubuntu.com/meta-release-lts URI_UNSTABLE_POSTFIX = -development URI_PROPOSED_POSTFIX = -proposed   What may be the problem of this?
22830
I need the update manager to only download a single package at a time and not try to download multiple packages at once.  My slow internet cannot handle multiple connections; slows the download to a crawl and some packages will reset themselves halfway through when they time-out.  EDIT  When using apt-get update multiple repositories get checked:   When using apt-get upgrade multiple packages are downloaded:
103211
When I ssh into the server it says:  11 packages can be updated. 11 updates are security updates.   Then I verify that everything is installed:  canonical-livepatch status --verbose   And this is what I get:  client-version: 9.3.0 machine-id: xxx machine-token: xxx architecture: x86_64 cpu-model: Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz last-check: 2019-05-15T18:08:12Z boot-time: 2019-05-11T10:06:52Z uptime: 104h34m56s status: - kernel: 4.15.0-48.51-generic   running: true   livepatch:     checkState: checked     patchState: nothing-to-apply     version: ""     fixes: ""   So there is nothing to apply? How about those 11 security updates then?  UPDATE:  As requested this is the list of upgradeable:  apt list --upgradable    intel-microcode/bionic-security,bionic-updates,bionic-updates,bionic-security 3.20190514.0ubuntu0.18.04.2 amd64 [upgradable from: 3.20180807a.0ubuntu0.18.04.1] libwbclient0/bionic-security,bionic-updates,bionic-updates,bionic-security 2:4.7.6+dfsg~ubuntu-0ubuntu2.10 amd64 [upgradable from: 2:4.7.6+dfsg~ubuntu-0ubuntu2.9] linux-generic/bionic-security,bionic-updates,bionic-updates,bionic-security 4.15.0.50.52 amd64 [upgradable from: 4.15.0.48.50] linux-headers-generic/bionic-security,bionic-updates,bionic-updates,bionic-security 4.15.0.50.52 amd64 [upgradable from: 4.15.0.48.50] linux-image-generic/bionic-security,bionic-updates,bionic-updates,bionic-security 4.15.0.50.52 amd64 [upgradable from: 4.15.0.48.50] linux-libc-dev/bionic-security,bionic-updates,bionic-updates,bionic-security 4.15.0-50.54 amd64 [upgradable from: 4.15.0-48.51] python3-distupgrade/bionic-updates,bionic-updates,bionic-updates,bionic-updates 1:18.04.32 all [upgradable from: 1:18.04.31] ubuntu-release-upgrader-core/bionic-updates,bionic-updates,bionic-updates,bionic-updates 1:18.04.32 all [upgradable from: 1:18.04.31]
2202
Every time I try update (using sudo apt-get update) my Ubuntu I get this problem:  W: The repository 'cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. W: The repository 'ppa.launchpad.net/kirillshkrogalev/ffmpeg-next/ubuntu xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1)/dists/xenial/main/binary-amd64/Packages  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs E: Failed to fetch cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1)/dists/xenial/main/binary-i386/Packages  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs E: Failed to fetch ppa.launchpad.net/kirillshkrogalev/ffmpeg-next/ubuntu/dists/xenial/main/binary-amd64/Packages  404  Not Found E: Failed to fetch ppa.launchpad.net/kirillshkrogalev/ffmpeg-next/ubuntu/dists/xenial/main/binary-i386/Packages  404  Not Found E: Some index files failed to download. They have been ignored, or old ones used instead.   How can I fix it? I use Ubuntu 16.04 LTS
20816
I had a bunch of errors in the output of sudo apt-get update:  duplicate entries and 404 not found errors.  Figured those out, I hope: I removed PPAs that didn't have any packages associated with them, then I removed out a duplicate entry in /etc/apt/sources.list.  It seems I have royally buggered it up.  Now most of the lines say Ign when I do sudo apt-get update.  How do I go about straightening out what I have screwed up?  I need to get rid of these Igns that are all over the place.  There are about 50% (eyeball guess) Igns!
99634
I'm trying to upgrade some package in a VM, but I dpkg refuses to apply the upgrades due the following:  dpkg: error processing /var/cache/apt/archives/ifupdown_0.7.5ubuntu2.2_amd64.deb (--unpack):  unable to make backup link of `./sbin/ifquery' before installing new version: No such file or directory Preparing to replace unzip 6.0-8ubuntu1 (using .../unzip_6.0-8ubuntu2_amd64.deb) ... Unpacking replacement unzip ... dpkg: error processing /var/cache/apt/archives/unzip_6.0-8ubuntu2_amd64.deb (--unpack):  unable to make backup link of `./usr/bin/unzip' before installing new version: No such file or directory dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)   What it means? The permissions are fine and the file definitively exist:  ls -l /sbin/ifquery -rwxr-xr-x 1 1500000 1500000 58496 dic 12  2012 /sbin/ifquery
57234
W: GPG error: http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F7F0DA5FD5B64B9 W: The repository 'http://download.opensuse.org/repositories/home:/strycore/xUbuntu_16.04 ./ Release' is not signed. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details.   I am trying to get rid of the above error message seemingly related to release key and opensuse url.  What would be the proper solution?
10540
When I log into my web server via SSH I see the information:  88 packages can be updated. 80 updates are security updates   I tried apt-get update then apt-get upgrade but each time I log in I still see the message about updates. How do I install them?