The updater can't connect, though the internet is connected via wireless. I have recently replaced the i3 cpu with an i7 630M in a thinkpad 14 and everything is fine except for the updater that won't connect (it did for a while). I would like to update the cpu microcode from intell with the driver manager and that won't activate the continue button to let me install that either.

This is what the update manager prints after the refresh updates fails...

Failed to fetch http://packages.domain.com/dists/xenial/InRelease Could not connect to packages.domain.com:80 (127.0.0.1). - connect (111: Connection refused)Some index files failed to download. They have been ignored, or old ones used instead.

Address 127.0.0.1 is called the "loopback" address, by definition. Therefore it appears you are not connected.

If you go to the command prompt and type "sudo ifconfig", or just "ifconfig", it should print out your network interfaces and there should be a wireless one in that list, like wlan0 or something similar. From there you can see if there is an IP address. Example from my system, my wired Ethernet:The paragraph of output contains other stuff, but the important part is the "inet addr" as emphasized in my example.

Wireless:The beginning of that term shows "wl" and typically a wireless adapter is given a "w" to start the name to indicate that it is wireless.

We'll have to first determine if you are truly connected and then see if the updater really does have any problems.

I had a similar issue yesterday, Linux Mint 19 “Tara” beta

the internet was working fine on news channels etc.,

but could not connect to any update site, I tried changing sources

with no effect, however today it has sorted its self out and all is well again.

Thanks for the reply. the terminal output reads thus...

wlp3s0 Link encap:Ethernet HWaddr <removed>
inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0
<removed>

Then it appears you do have a valid address from your router.

Please note that I edited to remove hardware addresses from your post. Not all of it was, however the details are best reduced to the fact that you do have an address.

What is the contents of your /etc/apt/sources.list file? I ask because it seems that there's something wrong with your repository.

I haven't much skill with linux. Addresses of files are kinda vague.

Where is this- /etc/apt/sources.list file


Actually the repository location; is that the one
main (Sylvia) http://mirrors.usinternet.com/mint/packages? or
base (xenial) http://archive.linux.duke.edu/ubuntu

the term 'xenial' is unknown to me as well. It seems like 'denial'

Alternatively, I understand apt-get updates and etc somewhat, yet the etc apt sources/list isn't plain.

thanks

here is the result of sudo apt-get update
sudo apt-get update
Err:1 http://packages.domain.com xenial InRelease
Could not connect to packages.domain.com:80 (127.0.0.1). - connect (111: Connection refused)
Ign:2 http://mirrors.usinternet.com/mint/packages sylvia InRelease
Ign:3 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:5 http://archive.canonical.com/ubuntu xenial InRelease
Hit:6 http://archive.linux.duke.edu/ubuntu xenial InRelease
Hit:7 http://dl.google.com/linux/chrome/deb stable Release
Hit:8 http://mirrors.usinternet.com/mint/packages sylvia Release
Get:9 http://archive.linux.duke.edu/ubuntu xenial-updates InRelease [109 kB]
Get:12 http://archive.linux.duke.edu/ubuntu xenial-backports InRelease [107 kB]
Fetched 216 kB in 3s (70.7 kB/s)
Reading package lists... Done
W: Failed to fetch http://packages.domain.com/dists/xenial/InRelease Could not connect to packages.domain.com:80 (127.0.0.1). - connect (111: Connection refused)
W: Some index files failed to download. They have been ignored, or old ones used instead

The sources you posted sources.list seem OK. Could you post the entire sources.list file? And, BTW, this has nothing to do with the CPU upgrade.

I've opened a command line to ping packages.domain.com and it resolves to 127.0.0.1

There's something wrong with that domain or the entry from their repository. I'd contact Ubuntu to advise them that one of their repositories is mis-named or that there is some sort of server error there.

I get the same thing with ping packages.domain.com. But with ping domain.com I get a real IP. But I'm rest assured the entry is incorrect, as here: https://forums.linuxmint.com/viewtopic.php?t=163925

I wonder if there could be some kind of server ID problem on this end rather than with Ubuntu xenial sources. I have no idea what most of the stuff is and need to explore and discover terminology. I tried a few of the optional locations and none of them worked.ie http://mirror.clarkson.edu/ubuntu
http://reflection.oss.ou.edu/linuxmint/repos
http://mirrordenver.fdcservers.net/ubuntu

i followed the link from AwesomeMachine about disabling http://packages.domain.com/ in software sources. Unfortunately I don't know how to find or disable that in software sources.

http://packages.domain.com/

https://forums.linuxmint.com/viewtopic.php?t=163925

Someone else had a similar problem of not knowing how to remove packages.domain

https://superuser.com/questions/1179...inux-mint-17-3

The final advice about how to check for broken pckages was this...

sudo nano /etc/apt/sources.list.d/official-package-repositories.list

I used that and got the following list...


deb http://packages.linuxmint.com sylvia main upstream import backport

deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe mu$
deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe $

deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted universe$
deb http://archive.canonical.com/ubuntu/ xenial partner

There isn't a http://packages.domain.com to disable (if I knew how to disable it. It only show up for me in the results from update manager refresh failure

I also tried this command in terminal- inxi -r

the output is- Repos: Active apt sources in file: /etc/apt/sources.list.d/additional-repositories.list
deb http://packages.domain.com/ xenial main
Active apt sources in file: /etc/apt/sources.list.d/google-chrome.list
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
deb http://packages.linuxmint.com sylvia main upstream import backport
deb http://archive.ubuntu.com/ubuntu xenial main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu xenial-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted universe multiverse
deb http://archive.canonical.com/ubuntu/ xenial partner


Ok- So I see that http://packages.domain.com/ is at the top of the list. Anyone know a command to remove it?

I found this problem described at https://forums.linuxmint.com/viewtopic.php?t=249154 -repos error, yet they did not say what the technical command in terminal was to remove it.

To disable a software source the easy way, open /etc/apt/sources.list and put a '#' in front of the offending entry. If you don't miss it after a year or two, delete the entry if it makes you feel better. I personally don't think I ever deleted a line in sources.list. Just comment out the ones you don't need or want.

You can safely delete that packages.domain.com entry. It is a dummy entry that is shown as an example of a deb line, rather than being a real one. If there's nothing else in /etc/apt/sources.list.d/additional-repositories.list then you can delete that too.

You can manage your software sources through the Update Manager (Edit->Software sources), by running Software Sources directly (mintsources, software-sources, or through the Mint menu), or by directly manipulating the files themselves.

I learned something about vim and nano editors trying to remove the packages.domain-I had difficulty saving the changes I had x'd out The problem was solved more easily through software sources as suggested, easily, by removing the additional repositories that I had enabled earlier.
thanks again

Just don't be afraid to mess things up. Otherwise, you'll never learn how to fix it.