Enabling Network mode in friendly-recovery mode fails
Bug #1436336 reported by
dz0ny
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| friendly-recovery (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
| Vivid |
Fix Released
|
Medium
|
Martin Pitt | ||
Bug Description
dist: latest vivid+systemd
Booting via grub recovery mode and enabling network fails because it expect upstart as services manager.
| affects: | systemd (Ubuntu) → friendly-recovery (Ubuntu) |
| Changed in friendly-recovery (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: vivid |
| summary: |
- Enabling Network mode in grub recover mode fails + Enabling Network mode in friendly-recovery mode fails |
| Changed in friendly-recovery (Ubuntu Vivid): | |
| status: | Triaged → Fix Committed |
| assignee: | nobody → Martin Pitt (pitti) |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in friendly-recovery (Ubuntu Vivid): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package friendly-recovery - 0.2.28
---------------
friendly-recovery (0.2.28) vivid; urgency=medium
* network: Temporarily start D-Bus and NetworkManager manually, instead of
calling the upstart scripts. We run even before local-fs-pre.target and
can't rely on any dependencies or NM to even work, so just do this
opportunist
-- Martin Pitt <email address hidden> Thu, 09 Apr 2015 16:07:48 +0200