I've had this problem many years. Still happens in 20.04... but it's
not like there's an attempt to be like a real Unix (rather than 'real'
GUI 'OS') so I guess I can't expect much (but the users do.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
This bug was fixed in the package friendly-recovery - 0.2.31ubuntu2
---
friendly-recovery (0.2.31ubuntu2) xenial; urgency=medium
[ Dimitri John Ledkov ]
* Actually use a friendly-recovery.target which systemd boots to
using a generator for default.target symlink. This ensures
** Changed in: friendly-recovery (Ubuntu Xenial)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to
** Patch removed: "fix-resolvconf-not-found.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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Unsubscribing sponsors as there seems to be nothing else to sponsor.
Artful is also EOL.
** Changed in: friendly-recovery (Ubuntu Artful)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Changed in: friendly-recovery (Ubuntu Xenial)
Assignee: Eric Desrochers (slashd) => (unassigned)
** Changed in: friendly-recovery (Ubuntu Artful)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I filed a new bug LP: #1766872 .
If someone experience the same problem, please provide some feedbacks in
the new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery m
Additionally,
When doing a systemd-analyze blame:
"Bootup is not yet finished. Please try again later"
systemctl list-jobs is showing a 100 jobs in 'waiting' state
Seems like systemd is not fully initialise in 'Recovery Mode'
--
You received this bug notification because you are a member of U
I did the same exercise on my reproducer and got the following pstree
output:
When is switch to vtty with systemd.debug-shell=1, here what I got :
# pstree
systemd-+-bash---pstree
|-recovery-menu---network---systemctl---systemd-tty-ask
|-systemd-journal
# ps
root 486
I did the same exercise on my reproducer and got the following pstree
output:
When is switch to vtty with systemd.debug-shell=1, here what I got :
# pstree
systemd-+-bash---pstree
|-recovery-menu---network---systemctl---(sd-askpwagent)
|-systemd-journal
# ps
root 486
I did the same exercise on my reproducer and got the following pstree
output:
When is switch to vtty with systemd.debug-shell=1, here what I got :
# pstree
systemd-+-bash---pstree
|-recovery-menu---network---systemctl---(sd-askpwagent)
|-systemd-journal
# ps
root 486
Here's a screenshot of what it looks like when block. [bionic-recovery-
mode.png]
** Attachment added: "bionic-recovery-mode.png"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+attachment/5127019/+files/Screenshot_bionic-recovery_2018-04-25_10_58_23.png
--
You rece
Here's a screenshot of what it looks like when block. [bionic-recovery-
mode.png]
** Attachment added: "bionic-recovery-mode.png"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+attachment/5127018/+files/Screenshot_bionic-recovery_2018-04-25_10_58_23.png
--
You rece
pstree command seems to shorten the processes name. So in fact 'systemd
'tty-ask' is 'systemd-tty-ask-password-agent'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mod
@xnox,
I have notice a block in Bionic when choosing 'Enable Network' option in
recovery mode on different bionic vanilla system and I can reproduce all
the time.
I also asked colleagues to give it a try (for a second pair of eye on
this) and they have the same result as me.
Basically, when choo
** Also affects: friendly-recovery (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: friendly-recovery (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: friendly-recovery (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: friendl
This bug was fixed in the package friendly-recovery - 0.2.38
---
friendly-recovery (0.2.38) unstable; urgency=medium
* Make friendly-recovery block the systemd emergency / rescue shell
modes. LP: #1662137
* Bump debhelper and starndards version, drop dh-systemd build-dep.
*
** Changed in: friendly-recovery (Ubuntu Bionic)
Assignee: Woodrow Shen (woodrow-shen) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable
** Tags added: id-5ab94ce5cbdbbc3e7f60d704
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/resolv.conf
not being present
To ma
** Also affects: friendly-recovery (Ubuntu Bionic)
Importance: High
Assignee: Woodrow Shen (woodrow-shen)
Status: Triaged
** Tags removed: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** No longer affects: network-manager (Ubuntu)
** No longer affects: thermald (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due t
** Tags added: id-5a6f2ec772ac06a254f2247f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/resolv.conf
not being present
To ma
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable networ
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/resolv.conf
not being present
To manage notific
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Titl
** Branch linked: lp:~ubuntu-core-dev/friendly-recovery/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/resolv.conf
not
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" t
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)
Sta
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 ju
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network f
** 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
Bugs, which is subscribed to Ubunt
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network f
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/resol
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 c
The issue still can be reproduced by 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/resolv.conf
not being present
To m
None of the above worked here! Without the /etc/resolv.conf nothing
works obviously, then the dpkg-reconfigure resolvconf does nothing (i.e.
there is still no file after running it. Adding it manually solved a
part of the problem, but the Unknown group "power" still blocks starting
of the network.
I can confirm "Daniel Pietrucha (texar)"'s experience.
Boot into the recovery console and run
# dpkg-reconfigure resolvconf
...
# apt update # worked immediately afterwards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network f
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
Bugs, which is subscribed to Ubuntu
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
d
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
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]
w
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to /etc/res
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network fai
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Tit
46 matches
Mail list logo
