** No longer affects: network-manager (Ubuntu)
** No longer affects: thermald (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during
** Tags added: id-5a6f2ec772ac06a254f2247f
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to
** Tags added: xenial
** Branch linked: lp:~woodrow-shen/friendly-recovery/fix-resolvconf-not-
found
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
** Changed in: friendly-recovery (Ubuntu)
Status: Confirmed => Triaged
** Changed in: friendly-recovery (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/resolv.conf
** Changed in: network-manager (Ubuntu)
Status: Opinion => Invalid
** Changed in: thermald (Ubuntu)
Status: Opinion => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Branch linked: lp:~ubuntu-core-dev/friendly-recovery/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network
The attachment "fix-resolvconf-not-found.patch" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
The issue is not NM, but in the friendly-recovery, and I already prepare
the patch to be reviewed.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Opinion
** Changed in: thermald (Ubuntu)
Status: Confirmed => Opinion
** Changed in: friendly-recovery (Ubuntu)
The issue is not NM, but in the friendly-recovery, and I already prepare
the patch to be reviewed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
My understanding is recovery-mode should do a task to update its resolv.conf
when "Enable networking" option was chosen,
just like normal boot will trigger resolvconf service to update resolv.conf (so
/sbin/resolvconf calls /etc/resolvconf/update.d/libc).
What I patch the friendly-recovery is
** Also affects: friendly-recovery (Ubuntu)
Importance: Undecided
Status: New
** Changed in: friendly-recovery (Ubuntu)
Assignee: (unassigned) => Woodrow Shen (woodrow-shen)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The issue is not NM, but in the friendly-recovery, and I already prepare
the patch to be reviewed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
Above should fix the situation as I just found out the resolvconf
service seems not be triggered when recovery mode is applied...
If resolvconf.service can be triggered normally, then it would execute
"/sbin/resolvconf --enable-updates". This creates a symbolic link
/etc/resolv.conf for
Giving the working note what I'm doing currently:
In order to analyze the issue, I tried to remove the /etc/resolv.conf in
the normal mode and traced the syslog if any systemd service restored
the file. What I observed is NM will go through this line of writing
DNS, and reported the warning from
The issue still can be reproduced by 18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to
None of the above worked here! Without the /etc/resolv.conf nothing
works obviously, then the dpkg-reconfigure resolvconf does nothing (i.e.
there is still no file after running it. Adding it manually solved a
part of the problem, but the Unknown group "power" still blocks starting
of the network.
I can confirm "Daniel Pietrucha (texar)"'s experience.
Boot into the recovery console and run
# dpkg-reconfigure resolvconf
...
# apt update # worked immediately afterwards.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
To to establish connection run:
dpkg-reconfigure resolvconf
eth connection is working in my case
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
Booting to recovery mode and trying to enable networking tells me
Unknown group "power" in message bus configuration file.
And networking will not be available running 17.04 ubuntu-gnome.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: thermald (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
So editing NetworkManager.conf didn't help.
I did some digging though and found that in /etc/dbus-1/system.d in element
busconfig in org.freedesktop.thermald.conf:
this is owned by thermald
thermald: 1.5.4-4
** Also affects: thermald
I booted into recovery to see if there the network was working again.
It is a bug of Networkmanager. Probably the username 'power' doesn't
affect the connection.
Solution:
sudo -H gedit /etc/NetworkManager/NetworkManager.conf
At the bottom of this file, copy and paste the following:
[device]
but did you boot into recovery mode in grub? Might be a different bug
if not
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode,
Here the same. I upgraded from 16.10 to 17.04. Network is not active. I
cannot surf in internet.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
26 matches
Mail list logo
