Temporary workaround which seems to work most of the time (though,
'timing' - as you are suggesting - sometimes is an issue, requiring a
couple of 'sudo apt update' attempts in Terminal to successfully resolve
all repositories) enter 8.8.8.8 (Google's DNS) into the relevant
'alternate DNS' in IPV4 box. I agree, it is most puzzling how the issue
seems to come and go, despite (eventually) successfully receiving and
deploying all updates to date . I'm still not confident enough to move
from 16.10 to 17.04 on my main machine.
(Sigh...)
David
On 22/04/2017 16:46, Jacek Misiurewicz wrote:
> Regarding my previous post (#24)...
>
> Seems that everything is back to abnormal. After logging out and re-
> logging again bug was back. This time soft disconnecting and
> reconnecting network (from NManager) helped to regain access to network,
> but this was not always the remedy.
>
Temporary workaround which seems to work most of the time (though,
'timing' - as you are suggesting - sometimes is an issue, requiring a
couple of 'sudo apt update' attempts in Terminal to successfully resolve
all repositories) enter 8.8.8.8 (Google's DNS) into the relevant
'alternate DNS' in IPV4 box. I agree, it is most puzzling how the issue
seems to come and go, despite (eventually) successfully receiving and
deploying all updates to date . I'm still not confident enough to move
from 16.10 to 17.04 on my main machine.
(Sigh...)
David
On 22/04/2017 16:46, Jacek Misiurewicz wrote:
> Regarding my previous post (#24)...
>
> Seems that everything is back to abnormal. After logging out and re-
> logging again bug was back. This time soft disconnecting and
> reconnecting network (from NManager) helped to regain access to network,
> but this was not always the remedy.
>