0

I am aware that if one googles the error above, then he would get tons of results. However, after trying many of the proposed solutions, and after working on this error for about a week in full-time, it's time to seek some help.

I am using Oracle VirtualBox on my Windows 10 machine. As a guest OS I installed Ubuntu 16.04.04.

This is what I tried:

  • As mentioned here, I have

    deb https://apt.dockerproject.org/repo ubuntu-xenial main line in my sources list. How I checked that? by running

find /etc/apt/ -name '*.list' -exec bash -c 'echo -e "\n$1\n"; cat -n "$1"' _ '{}' \;

in the command line, which gives:

`/etc/apt/sources.list.d/docker.list

 1  deb https://apt.dockerproject.org/repo ubuntu-xenial main

/etc/apt/sources.list

 1  deb http://de.archive.ubuntu.com/ubuntu/ xenial main universe restricted multiverse
 2  deb-src http://de.archive.ubuntu.com/ubuntu/ xenial main universe restricted multiverse #Added by software-properties
 3  deb http://de.archive.ubuntu.com/ubuntu/ xenial-updates universe restricted main multiverse
 4  deb http://security.ubuntu.com/ubuntu/ xenial-security universe restricted main multiverse
 5  deb https://packages.ubuntu.com/xenial/screen/ubuntu xenial main
 6  deb-src https://packages.ubuntu.com/xenial/screen/ubuntu xenial main
 7  deb-src https://apt.dockerproject.org/repo ubuntu-xenial main`

However, this did not resolve the error, even after sudo apt-get update which gives:

Reading package lists... Done
W: The repository 'http://de.archive.ubuntu.com/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.
W: The repository 'http://de.archive.ubuntu.com/ubuntu xenial-updates 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 'http://security.ubuntu.com/ubuntu xenial-security 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: Failed to fetch https://packages.ubuntu.com/xenial/screen/ubuntu/dists/xenial/InRelease  Could not resolve host: packages.ubuntu.com
W: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-xenial/InRelease  Could not resolve host: apt.dockerproject.org
E: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/main/source/Sources  Something wicked happened resolving 'de.archive.ubuntu.com:http' (-5 - No address associated with hostname)
E: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/universe/binary-amd64/Packages  Something wicked happened resolving 'de.archive.ubuntu.com:http' (-5 - No address associated with hostname)
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/universe/binary-amd64/Packages  Something wicked happened resolving 'security.ubuntu.com:http' (-5 - No address associated with hostname)
W: Some index files failed to download. They have been ignored, or old ones used instead.
  • I should mention that when I add a new source to the list, and press "Reload" in the following pop-up

enter image description here

I get the following error even though I have a working internet for sure.

enter image description here

The E: Unable to locate package XXX error occurs whenever I want to install a new package, not only with screen.

So now when I try to install screen using sudo apt-get install screen, I get:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package screen

It is also import to note that I am using proxy.

Since this error already overwhelmed me, I would highly appreciate any help

Alsharif
  • 31

1 Answers1

0

The solution is that apt has to be corrected configured with the proxy, which must be done both in /etc/environment and /etc/apt/apt.conf For example, in /etc/environment I should have something like this:

http_proxy="http://XXX.XX.XXX.XX:XX"
https_proxy="http://XXX.XX.XXX.XX:XX"
no_proxy=1,2,3,4,5,6,7,8,9,0

whereas in /etc/apt/apt.conf

Acquire::http::Proxy "http://XXX.XX.XXX.XX:XX";
Acquire::http::proxy::XX.XXX.X.XXX "DIRECT";
Acquire::https::Proxy "http://XXX.XX.XXX.XX:XX";

of course with the Xs replaced by the correct numbers.

Alsharif
  • 31