[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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 recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Triaged 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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 /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in thermald package in Ubuntu: Invalid 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in thermald package in Ubuntu: Invalid 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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 Ubuntu. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in thermald package in Ubuntu: Invalid 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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 not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Invalid Status in thermald package in Ubuntu: Invalid 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Invalid Status in thermald package in Ubuntu: Invalid 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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 failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Invalid Status in thermald package in Ubuntu: Invalid 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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 not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Opinion Status in thermald package in Ubuntu: Opinion 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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) 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. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Opinion Status in thermald package in Ubuntu: Opinion 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Opinion Status in thermald package in Ubuntu: Opinion 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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 just to add one line, see the patch I attached. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+attachment/5041442/+files/patch -- 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 not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Opinion Status in thermald package in Ubuntu: Opinion 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** 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 subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: New Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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 /run/resolvconf/resolv.conf. Basically the step is a implementation of "dpkg-reconfigure resolvconf". -- 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 not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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 calling /etc/resolvconf/update.d/libc: [1516604239.0578] dns-mgr: Writing DNS information to /sbin/resolvconf warning "/etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf" I'm thinking the /etc/resolv.conf will be dynamically recreated, and then NM moved on to finish its service (so NM is able to keep alive). However, under the recovery mode, the NM can't normally start its service and exit due to catch the signal SIGTERM (not sure if it's related to nm_dispatcher). So seems like we have two problems here: 1. why does NM fail to start 2. why does NM not try to call /etc/resolvconf/update.d/libc to restore the file in the recovery mode -- 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 not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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 /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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. How to fix that one? -- 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 not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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 subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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 (Ubuntu) Importance: Undecided Status: New -- 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 not being present Status in network-manager package in Ubuntu: Confirmed Status in thermald package in Ubuntu: New 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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] wifi.scan-rand-mac-address=no Restart the networkmanager sudo service network-manager restart -- 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 not being present Status in network-manager package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
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. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in network-manager package in Ubuntu: Confirmed 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 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 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.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
