[Expired for friendly-recovery (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: friendly-recovery (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested the command with both xenial & yakkety 64 bits:
xenial:
- after validating the command, i got dropped back to a frozen recovery menu
- ctrl+alt+del to exit after a while
- check nautilus , and cant find a network.debug output
yakkety:
- the command immediatly abort with: 'read only
I tested this on current xenial, and my ethernet interface does get
configured via DHCP, through the "ifup -a", it's not yet getting to the
NetworkManager fallback. I then commented out the "ifup -a" from /lib
/recovery-mode/options/network and re-ran it, and NM gets brought up.
So I cannot
** Package changed: systemd (Ubuntu) => friendly-recovery (Ubuntu)
** No longer affects: network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580591
Title:
"activate networking"
Does not have that issue with Wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580591
Title:
"activate networking" : broken from recovery mode
To manage notifications about this bug go to:
This has also been met by other users, like:
http://ubuntuforums.org/showthread.php?t=2253852=13172673#post13172673
Looks like systemd is concerned here.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- I have found that activation
Also affect xenial
cat /etc/fstab
#
#
# / was on /dev/sdc1 during installation
UUID=---- / ext4
errors=remount-ro 0 1
# /home was on /dev/sdc3 during installation
UUID=---- /home
** Summary changed:
- "activate network" broken from recovery mode
+ "activate networking" : broken from recovery mode
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580591