Comment 13 for bug 1785778
Revision history for this message
| R. Oliveira (rodrigobrochado) wrote | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I've faced the same issue, but in a recently installed Ubuntu Desktop 18.04 on a Asus K46CB.
I tried @pujan fix but it didn't work.
Several minutes later I've tried to type: ~$ cat /etc/resolv.conf following tips from here (Brazilian forum):
https:/
This command input in that thread was in fact intended to see the DNS config, but just the execution of the command seems to solve the guy problem.
So I tried to input the same command and after I've (magically) also succeed to update the packages.
There are two possible misconceptions here:
- The kernel was already updating the packages because of the Ubuntu fresh install and apt in some way get confused;
- Or it was a communication/
As I didn't try to directly update the packages after the "several minutes" and type the cat command instead, it's not possible to know if it really was the cat command or the network that got fixed. Also it's kind of weird that the simple fact of checking a config file solve a problem, right? But it is kind of huge coincidence that two different computers in different years (2017 and 2019) got the same fix after that command, isn't it?