At this point, i fully expect for the systemd team to not lift a finger
as usual and i'm going to run into this major bug again in a couple of
years when upgrading to 26.04... :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Running into this in server triage as well, Just checking in to see if
someone is working on this bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2078555
Title:
Upgrad
** Changed in: dnsmasq (Ubuntu)
Status: Confirmed => Triaged
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: dnsmasq (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided => Medium
** Change
I reproduced this issue by:
1. Starting a Jammy LXD container
2. Stop+disable systemd-resolved, install dnsmasq
3. Verify that dnsmasq is healthy
4. Upgraded to Noble
5. systemd-resolved is running again, dnsmasq is broken
I started looking into this bug because it has a dnsmasq task (so it's
par
"but this may be the right behavior, to install systemd-resolved"
In my case, systemd-resolved was installed before the upgrade, but it
was disables via command line. On updates and upgrades, i expect the
package manager to respect the configuration choices that have been made
previously.
do-rele
I'm running a different DNS solution, but i'm running into the same
problem with systemd-resolved
See bug 2078852
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2078555
Tit
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/20
That command results in
"No pending crash reports. Try --help for more information."
What additional information would you like?
systemd-resolved would have been version 255.4-1ubuntu8.4.
dnsmasq is version 2.90-2build2
While systemd-resolved may be the new expected default, at least a
warning
Tagging for discussion, but this may be the right behavior, to install
systemd-resolved.
Please run
ubuntu-bug 2078555
to attach relevant information
** Tags added: rls-nn-incoming
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug n
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2078555
Title:
Upgrading from
12 matches
Mail list logo