I think this bug is fixed after 16.04.01. I no longer have this problem
on a fresh install of Ubuntu MATE 16.06.1 64-bit, as well as on doing an
upgrade from Ubuntu 14.04 64-bit to Ubuntu 16.06.1 64-bit.
However, my previous installations/upgrades of Ubuntu 16.04 64-bit still
have this problem eve
Turns out what I said before isn't true. The issue still exists.
So, why was I getting a good network connection on the physical machine
I tried 16.04.1 on? Because I was connecting to WiFi via an Access Point
created on a 14.04 installation. The minute I connected directly to the
router, it start
Sorry to spam this bug with comments, but I just found out a workaround
to my problem. I had to disable IPv6 on the network connection (setting
Method to ignore). Not sure why I need to do this in 16.04, but this
isn't needed in 14.04.
After doing this, the internet connection doesn't drop at all
Taking into account the reasoning behind using an old Nautilus version
for Ubuntu 16.04 detailed here
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1541954 , it
makes sense to reconsider the usage of Nemo as the default file manager
for Ubuntu 16.10 and later.
--
You received this bug n
Try to disable IPv6 on your home WLAN and see if you have the same
problems. I set IPv6 to ignore on network manager for my home WLAN and
it was the only way I could get it to work properly on 16.04. On 14.04
that problem doesn't exist.
--
You received this bug notification because you are a memb
Public bug reported:
Is it possible to include a SteamOS session in Xenial repositories?
I can do this manually on Trusty by adding Marc Deslauriers' PPA. He
rebuilt the necessary packages for Ubuntu 14.04.
https://launchpad.net/~mdeslaur/+archive/ubuntu/steamos
It would be interesting to have
Why not using Nemo? As far as I know it has all the functionality of
Nautilus 3.14 and then some.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541954
Title:
Revert to the previous nautilus version
I can confirm this bug still persists on Ubuntu 20.04 64-bit, using an
ASRock 990fx Extreme4 motherboard.
The solution pointed out here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/916677/comments/39
seems to still fix the problem.
--
You received this bug notification because you are a