during recovery mode, enable network failed due to /etc/resolv.conf not being present
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
friendly-recovery (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned | ||
Artful |
Won't Fix
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
High
|
Unassigned |
Bug Description
Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc.
and selected "Enable Networking":
the result was:
grep: /etc/resolv.conf: No such File or directory.
Unknown group "power" in message bus configuration file.
(Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier)
Ubuntu: zesty 17.04
Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
network-manager: 1.4.4-1ubuntu3
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
ProcVersionSign
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Apr 13 16:40:19 2017
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2014-07-09 (1009 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
IpRoute:
default via 192.168.250.1 dev wlan1 proto static metric 600
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown
192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600
NetworkManager.
[main]
plugins=
[ifupdown]
managed=false
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
lxcbr0 bridge connected /org/freedeskto
wlan1 wifi connected /org/freedeskto
eth1 ethernet unavailable /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.4.4 connected started full enabled enabled enabled enabled disabled
Related branches
- Dimitri John Ledkov: Pending requested
-
Diff: 27 lines (+9/-0)2 files modifieddebian/changelog (+8/-0)
lib/recovery-mode/options/network (+1/-0)
Changed in friendly-recovery (Ubuntu): | |
assignee: | nobody → Woodrow Shen (woodrow-shen) |
Changed in network-manager (Ubuntu): | |
status: | Opinion → Invalid |
Changed in thermald (Ubuntu): | |
status: | Opinion → Invalid |
tags: | added: rls-bb-incoming |
Changed in friendly-recovery (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
tags: | added: xenial |
tags: | added: id-5a6f2ec772ac06a254f2247f |
no longer affects: | network-manager (Ubuntu) |
no longer affects: | thermald (Ubuntu) |
tags: | removed: rls-bb-incoming |
tags: | added: id-5ab94ce5cbdbbc3e7f60d704 |
Changed in friendly-recovery (Ubuntu Bionic): | |
assignee: | Woodrow Shen (woodrow-shen) → nobody |
Changed in friendly-recovery (Ubuntu Artful): | |
importance: | Undecided → Medium |
Changed in friendly-recovery (Ubuntu Xenial): | |
importance: | Undecided → Medium |
assignee: | nobody → Eric Desrochers (slashd) |
Changed in friendly-recovery (Ubuntu Artful): | |
assignee: | nobody → Eric Desrochers (slashd) |
status: | New → In Progress |
Changed in friendly-recovery (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in friendly-recovery (Ubuntu Xenial): | |
assignee: | Eric Desrochers (slashd) → nobody |
Changed in friendly-recovery (Ubuntu Artful): | |
assignee: | Eric Desrochers (slashd) → nobody |
Changed in friendly-recovery (Ubuntu Xenial): | |
status: | In Progress → Triaged |
Status changed to 'Confirmed' because the bug affects multiple users.