I've run into this issue a few times now with a few people that use Mint and more importantly Mint19. Mint 19 is a based on Ubuntu 18.04. There are a few issues that I have come across in my own installations and those of others. Thought I'd share some of the head scratcher moments my colleagues and myself have faced.
Mint 18.x is based of of Ubuntu 16,04
Mint 19 is based off of Ubuntu 18.04
Ubuntu has introduced some new things that can change your experience with Mint. And not necessarily for the better.
1. Ubuntu 18.04 now includes systemd.resolved and it replaces dnsmasq.
The DNS resolver built into systemd has included some extra functionality / changes that are meant to improved security. The completely undocumented feature of not resolving dotless domains. So what does this mean? Well in some environments when you join the network the network will provide a DNS via DHCP. If the network admin decided to declare a domain for the internal network something like. "starbucks". What will happen is your machine will NOT resolve DNS at all if it's on DHCP. If the domain were defined as "starbucks.shop". It would all of a sudden magically resolve DNS. Not ONLY systemd does this. All other resolvers out there do not follow this rule.
This is easily remedied permanently and restores past behaviour.
The file /etc/resolv.conf is actually a link to a systemd file. You can simply change it like so.
Code: Select all
sudo rm /etc/resolv.conf sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
2. Ubuntu 18.04 upgraded libcurl to version 4.
This can be a nasty issue if you do not pay attention to your old /etc/apt/sources.d/* files. If you simply copy over you old 3rdparty source files you will likely break your system a little. Version 4 and version 3 of libcurl can NOT co-exist on a system. You old apt sources were most often based off of xenial or ubuntu 16.04. In that release libcurl was at version 3. Some bright spark decided that they needed to include a pre-release version of libcurl version 4 shared library. So they put libcurl.so.4 into the version 3 lib. This instantly means that there is now a file conflict between the two packages. Now if your old apt sources include xenial in them you might actually also be including a dependency on libcurl version 3.
A classic issue is virtualbox. If you run Virtualbox and you install it from Oracle via the repo you could easily make this mistake. The xenial dist of virtualbox depends on version 3. The bionic release depends on version 4.
Make sure you scan your apt sources to ensure that there are NO xenial references at all. They should all be bionic. But of course this will also depend on the actual source itself. You will have to investigate each one.
Do you have the issue? Performa this command.
Code: Select all
grep -l xenial /etc/apt/sources.list.d/*.list