[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2020-07-06 Thread Steve Langasek
** Changed in: resolvconf (Ubuntu) Assignee: md shoeb lincoln (lincolntgl1987) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2020-07-06 Thread md shoeb lincoln
** Changed in: resolvconf (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => md shoeb lincoln (lincolntgl1987) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840

Re: [Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-12-02 Thread Steve Langasek
On Sun, Dec 02, 2018 at 11:59:42AM -, Paul Hewlett wrote: > I recently did an apt update on my laptop running cosmic. DNS was very > slow and I got the degraded to UDP message. Investigation showed that > /etc/resolv.conf symlinked: > lrwxrwxrwx 1 root root 39 Oct 22 2017

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-12-02 Thread Paul Hewlett
I recently did an apt update on my laptop running cosmic. DNS was very slow and I got the degraded to UDP message. Investigation showed that /etc/resolv.conf symlinked: lrwxrwxrwx 1 root root 39 Oct 22 2017 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf I fixed it by removing

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-11-01 Thread Damiön la Bagh
This issue is also happening in Ubuntu 16.04LTS with backports enabled. So I think there is something foobar with systemd-resolved and not resolvconf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu.

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-10-20 Thread Cubic PPA
** Changed in: cubic Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-03-12 Thread aaronfranke
This breaks chroot environments of 17.10 and up in a host of 17.04 and below. ** Also affects: cubic Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu.

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-01-20 Thread Steve Langasek
> Its broken for some VPN cases. Maintainer please note that some VPN > application > updates DNS with resolvconf package and removes those setting on exist. This > is > breaking the DNS resolution in some rare cases. So, in that case I wonder if we shouldn't force removal of resolvconf on

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-01-19 Thread nish
+1 for the issue. Its broken for some VPN cases. Maintainer please note that some VPN application updates DNS with resolvconf package and removes those setting on exist. This is breaking the DNS resolution in some rare cases. -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-01-08 Thread Anupam Datta
In my case it works well with WiFi network, But the Ethernet network is having the issue. In same port other machine works, but not mine. Earlier with 16:04 it used to work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-01-06 Thread Jeffrey Walton
Ping... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 Status in resolvconf

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-12-28 Thread Steve Langasek
This package is not used in new installs of 17.10, by design. If you are seeing wrong behavior of /etc/resolv.conf on a new install, that is not this bug. Please file a separate bug report against the systemd package with a description of what you are seeing so that we can help you. -- You

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-12-28 Thread Antony Jones
Been affected by this since my fresh 17.10 install (not an upgrade, but a clean install). The install was desktop amd64 iso, with no customisations at all, I'm surprised that this package is missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-12-24 Thread frankie
Fix it with the #apt install resolvconf as suggested above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-12-24 Thread frankie
I recently upgraded to 17.1 and have this same issue. Please provide a fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-12-22 Thread atimonin
I have a similar issue on a fresh 17.10 install: global sites are resolving OK, but local corporate sites not resolving firther investigation: # systemctl status systemd-resolved-update-resolvconf.service ● systemd-resolved-update-resolvconf.service Loaded: loaded

Re: [Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-12-11 Thread Steve Langasek
On Sat, Dec 09, 2017 at 05:12:36PM -, Daniel wrote: > Hello, > Was just bitten by this as well. etc/resolv.conf was pointing at > 127.0.1.1. > hydrogen@Bliss:~$ ls -l /etc/resolv.conf > lrwxrwxrwx 1 root root 33 May 24 2016 /etc/resolv.conf -> > ../run/NetworkManager/resolv.conf >

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-12-09 Thread Daniel
Hello, Was just bitten by this as well. etc/resolv.conf was pointing at 127.0.1.1. hydrogen@Bliss:~$ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 33 May 24 2016 /etc/resolv.conf -> ../run/NetworkManager/resolv.conf hydrogen@Bliss:~$ dpkg -S /etc/NetworkManager/ network-manager,

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-11-27 Thread Steve Langasek
Danni, this is useful information and gives the best hope of being able to debug the problem. Was your original resolv.conf a symlink or a real file? Can you attach it to this bug report? Can you also paste the output of 'dpkg -S /etc/NetworkManager' on your system? -- You received this bug

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-11-22 Thread Danni Uptlen
I have this same issue on a clean install of xubuntu 17.10. My biggest issue is that it seems to return after reboot (has reoccurred twice now, i assume after applying updates or something as I have restarted more than twice). I have previously been doing the following to fix: sudo rm

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-11-17 Thread MuppaneniBharath
I do have the same issue after upgrade from 17.4-17.10. So do we have a FIX !!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not

Re: [Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-11-05 Thread Steve Langasek
On Sat, Nov 04, 2017 at 06:55:17AM -, Matteo Dell'Amico wrote: > Same bug for me: /etc/resolv.conf was pointing to > /run/NetworkManager/resolv.conf rather than > ../run/resolvconf/resolv.conf, as fixed by dpkg-reconfigure resolvconf. > Bug also confirmed by a bunch of other people: see >

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-11-04 Thread Matteo Dell'Amico
Same bug for me: /etc/resolv.conf was pointing to /run/NetworkManager/resolv.conf rather than ../run/resolvconf/resolv.conf, as fixed by dpkg-reconfigure resolvconf. Bug also confirmed by a bunch of other people: see https://askubuntu.com/questions/966870/dns-not-working-after-

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-11-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu.

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-10-23 Thread Artur Schmitt
If you need further information, please let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-10-22 Thread Steve Langasek
Thanks. This log shows the correct upgrade, but unfortunately it doesn't show any obvious explanation for why /etc/resolv.conf was replaced. I'll set this back to new, but I guess we aren't going to make forward progress on understanding what happened without some further information. **

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-10-22 Thread Artur Schmitt
Sorry for the mistake. ** Attachment added: "upgrade logs" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+attachment/4984300/+files/dist-upgrade.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-10-21 Thread Steve Langasek
Preparando para desempaquetar .../013-resolvconf_1.79ubuntu4_all.deb ... Desempaquetando resolvconf (1.79ubuntu4) sobre (1.79ubuntu1) ... This shows an upgrade from 16.10 to 17.04, not an upgrade from 17.04 to 17.10. Do you have a later log file available? -- You received this bug notification

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-10-21 Thread Artur Schmitt
** Attachment added: "upgrade logs" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+attachment/4983661/+files/20171019-2226.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu.

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2017-10-21 Thread Steve Langasek
Please attach your upgrade logs from /var/log/dist-upgrade to help us try to see what has happened on your system. Both before and after the upgrade, /etc/resolv.conf should be a symlink to /run/resolvconf/resolv.conf. If something has replaced that with a file, we would need to figure out what