This bug was fixed in the package friendly-recovery -
0.2.41ubuntu0.20.04.1
---
friendly-recovery (0.2.41ubuntu0.20.04.1) focal; urgency=medium
* add resolvconf-pull-resolved.path to script that brings up the
network in order to resolve a conflict between systemd and
resolvc
This bug was fixed in the package friendly-recovery - 0.2.38ubuntu1.2
---
friendly-recovery (0.2.38ubuntu1.2) bionic; urgency=medium
* add resolvconf-pull-resolved.path to script that brings up the
network in order to resolve a conflict between systemd and
resolvconf (LP: #1
This bug was fixed in the package friendly-recovery -
0.2.41ubuntu0.20.10.1
---
friendly-recovery (0.2.41ubuntu0.20.10.1) groovy; urgency=medium
* add resolvconf-pull-resolved.path to script that brings up the
network in order to resolve a conflict between systemd and
resolv
Verification passed for focal.
The attached image verifies the fix in focal. The first half of the
image shows the installed versions of friendly-recovery, systemd, and
resolvconf, the failed result from "dig www.google.com", and the empty
/etc/resolv.conf. The second half of the image shows an up
Hello Brian, or anyone else affected,
Accepted friendly-recovery into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/friendly-
recovery/0.2.41ubuntu0.20.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this n
The attached image verifies the fix in bionic. The first half of the
image shows the installed versions of friendly-recovery, systemd, and
resolvconf, the failed result from "dig www.google.com", and the empty
/etc/resolv.conf. The second half of the image shows an updated
installed version of frie
Verification passed for groovy.
The attached image verifies the fix in groovy. The first half of the
image shows the installed versions of friendly-recovery, systemd, and
resolvconf, the failed result from "dig www.google.com", and the empty
/etc/resolv.conf. The second half of the image shows an
** Changed in: friendly-recovery (Ubuntu)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: friendly-recovery (Ubuntu Bionic)
Assignee: (unassigned) => William Wilson (jawn-smith)
** Changed in: friendly-recovery (Ubuntu Focal)
Assignee: (unassigned) => William W
Hello Brian, or anyone else affected,
Accepted friendly-recovery into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/friendly-
recovery/0.2.41ubuntu0.20.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this
** Changed in: friendly-recovery (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: friendly-recovery (Ubuntu Focal)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
bionic sponsored into unapproved queue
** Changed in: friendly-recovery (Ubuntu Bionic)
Status: New => In Progress
** Changed in: friendly-recovery (Ubuntu Focal)
Status: New => In Progress
** Changed in: friendly-recovery (Ubuntu Groovy)
Status: New => In Progress
--
You
also news to me that resolvconf changes i did got srued that far back!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage no
groovy sponsored into unapproved queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage notifications about this bug go to
focal sponsored into unapproved queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage notifications about this bug go to:
This bug was fixed in the package friendly-recovery - 0.2.42
---
friendly-recovery (0.2.42) unstable; urgency=medium
[ Debian Janitor ]
* Trim trailing whitespace.
* Add missing build dependency on dh addon.
* Bump debhelper from old 10 to 12.
* Set debhelper-compat version
The hirsute debdiff is no longer necessary as 0.2.42 (which has the fix)
is now in -proposed for hirsute.
** Also affects: friendly-recovery (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: friendly-recovery (Ubuntu Focal)
Importance: Undecided
Status: New
-
** Description changed:
I was using friendly-recovery as my Ubuntu desktop session was not
starting after an upgrade to Groovy Gorilla. When I chose to "Enable
networking" in the friendly-recovery menu I noticed that no dns servers
could be reached and come to find out it was because syste
Attached is a patch for hirsute. For hirsute we will begin using quilt
patches for changes.
** Patch removed: "lp1891952_hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457125/+files/lp1891952_hirsute.debdiff
** Patch added: "lp1891952_hi
Attached is a patch to SRU groovy.
** Patch added: "lp1891952_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457123/+files/lp1891952_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Attached is a patch for hirsute. For hirsute we will begin using quilt
patches for changes.
** Patch added: "lp1891952_hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457125/+files/lp1891952_hirsute.debdiff
--
You received this bug notif
Attached is a patch for hirsute. For hirsute we will begin using quilt
patches for changes.
** Patch added: "lp1891952_hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457124/+files/lp1891952_hirsute.debdiff
--
You received this bug notif
Attached is a patch to SRU focal.
** Patch removed: "lp1891952_hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457117/+files/lp1891952_hirsute.debdiff
** Patch removed: "lp1891952_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+sou
Attached is a patch to SRU for bionic.
** Patch added: "lp1891952_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457121/+files/lp1891952_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Attached is a patch to SRU for focal.
** Patch added: "lp1891952_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457120/+files/lp1891952_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached is an patch to SRU for groovy.
** Patch added: "lp1891952_groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457119/+files/lp1891952_groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Attached is a patch for hirsute. In this version we will start using
quilt patches.
** Patch added: "lp1891952_hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5457117/+files/lp1891952_hirsute.debdiff
--
You received this bug notification
** 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/1891952
Title:
systemd-resolved not started when networking enabled
To manage notificati
** Branch linked: lp:~jawn-smith/friendly-recovery/systemd-resolvconf-
conflict
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To
** Branch linked: lp:~jawn-smith/friendly-recovery/systemd-resolvconf-
conflict
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To
The system on which I'd discovered this issue is one which has been
upgraded from an install of Ubuntu 16.04 LTS which had resolvconf in
main.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Tit
The steps in my previous comment result in the same behavior with all of
the following:
Focal
systemd version 245.4-4ubuntu3.4
resolvconf version 1.82
Groovy
systemd version 246.6-1ubuntu1.1
resolvconf version 1.84ubuntu1
Hirsute
systemd version 247.1-4ubuntu1
resolvconf
This appears to be a conflict between systemd-resolved and resolvconf.
I'm able to recreate the issue with the following steps
1) Fresh 20.04 install
2) boot to friendly recovery
a) enable networking, drop to root shell
b) name resolution works as expected
3) reboot to fully booted syst
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage no
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Tags added: groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started whe
** Tags added: fr-209
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage notifications about this bug go to:
https://bugs.la
Latest test results.
** Attachment added: "IMG_20200907_155222.jpg"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/5408674/+files/IMG_20200907_155222.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
This is still an issue with systemd 246.4-1ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage notifications about t
** Tags added: id-5f3e933949c90824f3719caa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-resolved not started when networking enabled
To manage notifications about this bug g
Yes, I still observe the issue with systemd 246.2-1ubuntu1. Simply
restarting systemd-resolved populates /etc/resolv.conf and allows name
resolution to work.
** Attachment added: "IMG_20200831_102917.jpg"
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1891952/+attachment/540
Systemd 246.2-1ubuntu1 may have fixed the DNS issue. Do yo still observe
the problem?
** Changed in: friendly-recovery (Ubuntu Groovy)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Also affects: friendly-recovery (Ubuntu Groovy)
Importance: Undecided
Status: New
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891952
Title:
systemd-
** Changed in: friendly-recovery (Ubuntu Groovy)
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/1891952
Title:
systemd-resolved not started when networking enabled
T
The problem I encountered in the description was from when I had systemd
version 246-2ubuntu1 installed. I've since downgraded to 245.7-1ubuntu1
so I tried friendly-recovery again and there were still issues with name
resolution. However, this time starting systemd-resolved did not fix the
issue an
43 matches
Mail list logo
