@vorlon thank you for your well explaination. My system was upgraded
from 16.04 -> 16.10 -> 17.04 -> 17.10, I'm not sure how it became that
in 17.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs
Actually, since you have already used the method from comment #6 to
point /etc/resolv.conf directly at resolved instead of at resolvconf,
this is also fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https:
@diabloneo
resolvconf doesn't leave a process running on the system; it is only
triggered when there are changes to the network or to the available
local resolvers, and coordinates updates to /etc/resolv.conf.
But if /etc/resolv.conf is not a symlink to /run/resolvconf/resolv.conf,
this has no ef
@vorlon
The resolvconf package is installed. I meaned it's not running when I
check with 'systemctl status' or 'ps -ef'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
T
On 21 October 2017 at 21:51, Steve Langasek
wrote:
> On Sat, Oct 21, 2017 at 08:54:03AM -, diabloneo wrote:
>> No, I wasn't using resolvconf.
>
> Ok, is there any particular reason for that? The resolvconf package is part
> of ubuntu-minimal in Ubuntu 17.04. Removal of ubuntu-minimal leaves
On Sat, Oct 21, 2017 at 08:54:03AM -, diabloneo wrote:
> No, I wasn't using resolvconf.
Ok, is there any particular reason for that? The resolvconf package is part
of ubuntu-minimal in Ubuntu 17.04. Removal of ubuntu-minimal leaves you
with an unsupported configuration.
--
You received thi
No, I wasn't using resolvconf.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Title:
Cannot resolve DNS in artful daily
Status in casper package in Ubuntu:
Confirme
Were you not using resolvconf on this system prior to upgrade?
NetworkManager should only have managed /etc/resolv.conf contents if it
did not detect that another system was managing it (resolvconf or
resolved).
--
You received this bug notification because you are a member of Desktop
Packages, w
@vorlon
It just contained:
# Generated by NetworkManager
nameserver 127.0.1.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Title:
Cannot resolve DNS in artful dail
netcfg is also fixed.
netcfg (1.142ubuntu4) artful; urgency=medium
* Add resolved support. LP: #1714167
-- Dimitri John Ledkov Wed, 20 Sep 2017 09:52:03
+0100
** Changed in: netcfg (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a
network-manager is also fixed:
network-manager (1.8.2-1ubuntu6) artful; urgency=medium
* src/dns/nm-dns-manager.c:
- Fix resolved detection, the symlink target is usually relative to
the root, such that in chroots the file points to a file inside the
chroot. But keep absolute target
livecd-rootfs fixed in version 2.468:
livecd-rootfs (2.468) artful; urgency=medium
[ Dimitri John Ledkov ]
* Drop obsolete fix-ups of resolv.conf, debootstrap should now result in
correct symlink to resolved without any further fixes.
[ Michael Hudson-Doyle ]
* Have subiquity.service
So how was /etc/resolv.conf configured before you removed it? To my
understanding, there should be no problems after upgrade from any of the
default configurations in 17.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
I just upgraded from 17.04 to release version of 17.10, then I encounter
this problem, too. comment #6's method fixed this issue for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net
** Attachment added: "File containing my present journal log, with multiple
on/off toggles."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712283/+attachment/4957729/+files/a
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@prefec2 that sounds like a different bug. This one is not intermittent.
If the workaround in comment #6 does not fix it for you then I suggest
filing a new bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
h
I have the same issue. A couple of month ago we had a similar issue, which
could be fixed by "downgrading" the resolver setup for systemd. However, the
issue returned a couple of days ago.
In general networking works after start up, but stops after a random time
period. When I "turn off" the con
Today, I also ran into this issue. Wifi was working and I could
successfully ping Google's DNS 8.8.8.8.
However, pinging google.com didn't work: "Name or service not known"
The workaround in comment #6 does the trick for me:
sudo rm /etc/resolv.conf
sudo ln -s /run/systemd/resolve/stub-resolv.co
Forgot to mention, I have a fresh install from the daily artful image on
21st of September 2017.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Title:
Cannot resolve D
Started working for me about yesterday, but then dropped again.
I use .domain vpn and no .domain get resolved by the system.
It was ok about a week ago, then not working, working for a day, then again -
none.
--
You received this bug notification because you are a member of Desktop
Packages, whi
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled;
vendor preset: enabled)
Active: active (running) since Tue 2017-08-29 22:12:30 CEST; 36s ago
Docs: man:systemd-resolved.service(8)
https://www.freedeskt
jarod@ubuntu-pc:~$ ll /etc/resolv.conf
-rw-r--r-- 1 root root 78 Aug 28 09:38 /etc/resolv.conf
jarod@ubuntu-pc:~$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 114.114.114.114 # this entry is manually add by me
nameserver 127.0.1.1
jarod@ubuntu-pc:~$ systemctl status systemd-res
On Mon, Aug 28, 2017 at 01:47:23AM -, Jarod wrote:
> update to systemd (234-2ubuntu9) doesn't help, after reboot I still need
> manually add nameserver to /etc/resolve.conf
After your update, is /etc/resolv.conf a symlink to
/run/systemd/resolve/stub-resolv.conf ?
Please show the output of 's
update to systemd (234-2ubuntu9) doesn't help, after reboot I still need
manually add nameserver to /etc/resolve.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Titl
This bug was fixed in the package systemd - 234-2ubuntu9
---
systemd (234-2ubuntu9) artful; urgency=medium
* boot-and-services: skip gdm3 tests when absent, as it is on s390x.
-- Dimitri John Ledkov Wed, 23 Aug 2017 11:58:57
+0100
** Changed in: systemd (Ubuntu)
Status:
I can confirm that for me removing /etc/resolv.conf and replacing it
with a link to stub-resolv.conf using
sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
and rebooting (probably I could just have restarted the appropriate
service) restores DNS functionality.
--
You received t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netcfg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: casper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bu
** Description changed:
in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session
/ installed session - running on virtualbox 5.1.26.
However I cannot ping google.com - "Name or service not known"
Kind of difficult to run ubuntu-bug here without a fully functioning
n
** Changed in: network-manager (Ubuntu)
Importance: Critical => Medium
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu
** Also affects: netcfg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcfg (Ubuntu)
Importance: Undecided => Critical
** Also affects: casper (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad
** Also affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Title:
Cannot resolve DNS in artful
** Branch linked: lp:~xnox/livecd-rootfs/force-resolved-stub-resolver
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Title:
Cannot resolve DNS in artful daily
Status
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1712283
Title:
Cannot resolve DNS in artful daily
St
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Critical
** Changed in: network-manager (Ubuntu)
Assignee: (unassig
36 matches
Mail list logo