** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
Yes.. LXD's system containers and systemd/udev have a special kind of
relationship and we should strive to resolve that situation properly
long-term. I already talked to stgraber about that, but I guess we
should lay out a proper path forward as continuously patching more and
more components of sys
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Medium
Status: New
** Also affects: systemd (Ubuntu Hirsute)
I
released in 249.5-2ubuntu1
** Changed in: systemd (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1950511
Title:
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1950787
Title:
systemd-sysusers cannot mount /d
** Tags added: fr-1896
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952733
Title:
Add Dell Privacy Mic Mute Key mapping for another Dell machine
Status in OEM Priority
** Tags added: fr-1897
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952735
Title:
Add Microphone mute key mapping for Dell machine
Status in OEM Priority Project:
Co
** Tags added: fr-1895
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1943561
Title:
Add ACCEL_LOCATION=base property for 6 Dell clamshell models
Status in OEM Priority P
Yes, indeed. NetworkManager tries to control all interfaces that are
available by default and netplan implemented some quirks in the past to
avoid this. But we should review those quirks and rather implement a
per-interface/netdef deny- or accept-list.
** Tags added: fr-1888
** Changed in: netpla
** Tags added: fr-1886
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1952599
Title:
virt: Support detection for ARM64 Hyper-V guests (fixed upstream)
Status in systemd p
** Also affects: systemd (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Hirsute)
This is already included in v249.5 stable, that is to be uploaded soon.
(https://git.launchpad.net/~slyon/ubuntu/+source/systemd/log/?h=ubuntu-
jammy-249)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
http
** Tags added: fr-1885
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1650688
Title:
timedatectl set-timezone fails on UC16
Status in Snappy:
Triaged
Status in systemd
** Tags added: fr-1884
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1951214
Title:
ubuntu-bug isn't opening firefox (snap) on jammy, instead gedit gets
data
Status in
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1950794
Title:
DHCPv4 (IAID+DUID) networking broken in L
I'm still suspecting dbus to be at fault here. We might need to bisect
dbus in order to find out more about this, but that is hard without a
reliable reproducer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice
Thanks ddstreet, I agree 918e6f1c0151429f5095355f4f3f74f16e79724a could
be related as well, but unfortunately that commit produced quite some
fall-out.
Nevertheless, I've prepared a new systemd build in my PPA and the
"core18_2028_amd64.snap" at https://people.ubuntu.com/~slyon/uc18/
cherry-pi
Reverting this upstream commit seems to fix the problem:
https://github.com/systemd/systemd/commit/0299deab53d2a087727a5d04c1500c322c48b63e
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launch
Turns out dropping "debian/patches/units-Don-t-start-systemd-udev-
trigger.service-in-a-conta.patch" (that we want to drop anyway) makes a
difference here, i.e. removing the "ConditionVirtualization=!container"
line from /usr/lib/systemd/service/systemd-udev-trigger.service.
# apt install systemd
Thank you, having a reliable reproducer is very helpful! I can confirm
this reproduces locally for me on QEMU.
I prepared a new systemd package [0], containing backports from the
above mentioned PR that indeed sounds very related (I wonder why the
issue didn't happen before, tho, as this is unrela
I've implemented the workaround in systemd's debian/test/tests-in-lxd.
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launch
Public bug reported:
DHCPv4 networking does not work in the default IAID+DUID
(ClientIdentifier=duid) mode in LXC containers, using systemd-networkd
v249.5-2ubuntu1. Static configuration and DHCPv6 work without problem.
Reproducer:
$ lxc launch ubuntu-daily:jammy jj
$ lxc exec jj bash
# add-apt-r
This commit seems to be related:
https://github.com/lxc/distrobuilder/commit/33a4302ca5a62ed9eb9009dcc5059aecfb55ba41
But why does it not work in privileged containers?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
** Attachment added: "debug.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950787/+attachment/5540415/+files/debug.log
** Description changed:
systemd-sysusers.service/systemd.exec fails to start in privileged
containers, due to being unable to properly mount /dev for passing
Public bug reported:
systemd-sysusers.service/systemd.exec fails to start in privileged containers,
due to being unable to properly mount /dev for passing credentials, caused by
the following config in the .service unit:
```
# Optionally, pick up a root password and shell for the root user from
** No longer affects: systemd (Ubuntu Jammy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in Ubuntu Core 18
That's certainly possible. In the first attempt (that failed according
to mvo's tests) I only backported
https://github.com/systemd/systemd-stable/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0
and
https://github.com/systemd/systemd-stable/commit/cc6271f17d3c5c200e8a391f10d0afb71403fc28
(as a de
Thank you for testing the revert!
Do we know if the same issue happens in Focal/UC20 as well? Or can we somehow
falsify that? The regressing patches had been introduced to
Hirsute/Focal/Bionic to fix LP: #1934147
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Merge proposal linked:
https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/411528
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Titl
Sounds like we cannot have an easy fix by simply applying
04eb582acc203eab0bc5c2cc5e13986f16e09df0 (and its dependencies).
So let's first try to pinpoint if f0831ed2a03fcef582660be1c3b1a9f3e267e656
really introduced the regression. I've built a new core18 snap with my previous
work and the inclu
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails t
Thank you Alfonso, I staged this patch for the next Focal SRU:
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
focal&id=fe0cb0bd66baea89d8bbe47cb47d88540f46d470
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu Focal)
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1948476
Title:
[SRU] Allow target units
Sure, I put that custom core18 snap into
https://people.ubuntu.com/~slyon/uc18/ as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fai
Not having a reliable reproducer is always a tricky situation to be
in...
Indeed that other commit might be related. I've backported the following
patches and created a custom systemd build in
https://launchpad.net/~slyon/+archive/ubuntu/lp1949089
https://github.com/systemd/systemd-stable/commit/
** Changed in: libunity (Ubuntu Impish)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1945969
Title:
Update Vala to 0.52.6 in Imp
** Also affects: util-linux (Ubuntu Jammy)
Importance: Low
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1944741
Title:
HiFive Unmatched partitio
No need for 0-day SRU. This has been sponsored into Debian unstable and
will be synced to Ubuntu. Thanks @seb128!
https://tracker.debian.org/news/1266939/accepted-
libunity-714190420190319-6-source-into-unstable/
** Summary changed:
- FTBFS with valac 0.52.6 in impish
+ Update to 0.52.6 in impis
** Summary changed:
- Update to 0.52.6 in impish
+ FTBFS with valac 0.52.6 in impish
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1945969
Title:
FTBFS with valac 0.52.
** Also affects: vala (Ubuntu Impish)
Importance: High
Assignee: Rico Tzschichholz (ricotz)
Status: Fix Released
** Also affects: libunity (Ubuntu Impish)
Importance: High
Assignee: Lukas Märdian (slyon)
Status: Fix Committed
--
You received this bug notification
This is a FTBFS fix for libunity that could become an impish 0-day SRU.
PPA pre-testing has been done here:
https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing-
archive-extra
** Description changed:
+ [Impact]
+
+ * libunity FTBFS using valac 0.52.6, which makes i
Thank you! You changes LGTM.
The first patch resembles the upstream commit, the 2nd patch (that touches the
translation files) is not yet merged upstream, but makes sense.
With all builds passing in a PPA and a successful autopkgtest run, I'll
stage this to be a 0-day SRU, as discussed with the r
** Also affects: util-linux (Ubuntu Impish)
Importance: Low
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1944741
Title:
HiFive Unmatched partiti
** Also affects: libunity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libunity (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity
There is some documentation around how to implement this with netplan
here: https://netplan.io/faq/#use-pre-up%2C-post-up%2C-etc.-hook-scripts
But its basically using the underlying renderer's (NM or networkd-
dispatcher) hooks, as netplan itself is not a networking daemon and
cannot easily listen
Thank you for testing. The Focal backport might need some more work, as
that version of systemd is even older and the patches did not apply
cleanly.
For Hirsute it was a straightforward cherry-pick of patches from
systemd-stable v247 (MergeProposal attached to this bug report). So I
wonder if we c
** Changed in: systemd (Ubuntu Impish)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1938259
Title:
Add ACCEL_LOCATION=base prope
Closing, as agreed upon with the SRU team:
https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/408816/comments/1079349
** Changed in: systemd (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received t
** Changed in: binutils (Ubuntu)
Status: Invalid => Confirmed
** Changed in: binutils (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.
In more recent kernels (i.e. linux-meta-aws/azure 5.13) I can see
messages like this: " watchdog: BUG: soft lockup - CPU#3 stuck for
238s!" that seems to indicate the kernel is not giving back control to
the userspace/systemd.
Also a message about a missing autofs4 module, that might be related:
"
** Changed in: binutils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1940505
Title:
monero FTBFS on riscv64
Status in binutils:
Thanks for confirming Denys, that's unfortunate...
Would you mind giving the version from this PPA a try
https://launchpad.net/~slyon/+archive/ubuntu/lp1934221 (for Hirsute)?
And maybe also for Focal once the build is ready?
--
You received this bug notification because you are a member of Ubun
** Merge proposal linked:
https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/408816
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1943982
Titl
Unfortunately, this patch does not seem to be sufficient.
It produces very similar segfaults in on_query_timeout
(https://errors.ubuntu.com/problem/c4e5be3f1c7af9483993c7e6007b9325ab5b78cd)
that the segfault we could observe before
(https://errors.ubuntu.com/problem/bb0ce4ff8e6ef86041cfb5647b79282
Public bug reported:
[impact]
The initial patch for LP: #1934221 was not sufficient to fix the root
cause of the segfault, but rather moved it to a slightly different
location in the code (still inside the on_query_timeout handler).
[test case]
this bug is only to revert the previous patch
For
Some more findings after testing with systemd-run:
FAIL: lxc-tests: lxc-test-autostart (360s)
FAIL: lxc-tests: lxc-test-no-new-privs (361s)
This two tests fail during the (local) autopkgtest run. But after logging into
the local autopkgtest VM via its debug shell (--shell-fail|-s parameter) and
From a side-channel discussion:
all the fully unprivileged tests need to be disabled on
cgroup v2. You can't run fully unprivileged containers on pure cgroup2
layouts. The delegation model doesn't allow it. Not without systemd
making a fully empty delegated cgroup hierarchy available.
I think I
Addressed in FR-1460
** Tags removed: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus timeout-ed during an upgrade, taking serv
** Changed in: snapd
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1850667
Title:
Switch to "unified" cgroup hierarchy (cgroupv2
** Attachment added: "lxc-vs-old-systemd.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1943704/+attachment/5525407/+files/lxc-vs-old-systemd.log
** Description changed:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified hierarch
Public bug reported:
lxc fails 4 autopkgtests if ran on a cgroups v2 enabled systemd
(248.3-1ubuntu7) using a pure unified hierarchy (in favor of the hybrid
hierarchy used before).
https://autopkgtest.ubuntu.com/packages/lxc
FAIL: lxc-tests: lxc-test-apparmor-mount (0s)
FAIL: lxc-tests: lxc-test
snapd landed the support in upstream git as of yesterday
(https://github.com/snapcore/snapd) and it is expected to be shipped
with snapd v2.53
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.lau
I've tested systemd 245.4-4ubuntu3.13 from focal-proposed in a VM and
can verify it is working as expected.
I used the configuration provided and kept the VM running for several days
without any crash:
```
root@ff-vm:~# cat /etc/systemd/resolved.conf
[Resolve]
DNS=46.182.19.48#dns2.digitalcourage
Merged upstream and staged in: https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/log/?h=ubuntu-impish
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I've tested systemd 247.3-3ubuntu3.6 from hirsute-proposed in a VM and
can verify it is working as expected.
I used the configuration provided and kept the VM running for several days
without any crash:
```
root@hh-vm:~# cat /etc/systemd/resolved.conf
[Resolve]
DNS=46.182.19.48#dns2.digitalcoura
We do now have an upstream patch/PR:
https://github.com/systemd/systemd/pull/20705
It's not much different from what was already landed in the systemd
package (skipping the test in this scenario). So we should probably only
stage it for the next systemd upload, after it was merged upstream.
--
Y
** Also affects: glibc via
https://github.com/systemd/systemd/issues/20593
Importance: Unknown
Status: Unknown
** Project changed: glibc => systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
Unfortunately, it doesn't seem to be the same bug, but might be similar.
I can still reporduce the issue with the upstream daily-build.
I can reproduce it on an Ubuntu Impish host (kernel 5.11.0-31-generic, systemd
248.3-1ubuntu3), running an Ubuntu Impish container (kernel 5.11.0-31-generic,
s
** Changed in: glibc (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1940635
Title:
systemd-networkd failing to acquire a DHCP6
** Description changed:
basic.target waits for dbus.socket (via sockets.target) AND dbus.socket
waits for basic.target, too, delaying dbus-daemon startup. At some point
a timeout happens, dbus is started and all queued services try to start
registering to the bus at the same time.
All
Hi Denys,
could you please help with testing this new systemd release in focal-
proposed (and hirsute-proposed) and confirm that it is working in your
context without crashes?
https://wiki.ubuntu.com/Testing/EnableProposed
IIRC you're running a Focal machine, which should make testing the
versio
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1940635
Title:
systemd-networkd failing to acqui
** Summary changed:
- systemd-networkd failing to acquire a DCHP6 lease from dnsmasq on armhf
+ systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
** Attachment added: "lxd-armhf-debug.log"
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1940635/+attachment/5519352/+files/lxd-armhf-debug.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The systemd-networkd debug log (inside armhf container) reveals an
interesting error message: "NDISC: Unexpected error while reading from
ICMPv6, ignoring: Exchange full"
Aug 20 09:40:22 autopkgtest-lxd-ytcddy systemd-networkd[5450]: NDISC: Started
IPv6 Router Solicitation client
Aug 20 09:40:22
** Attachment added: "lxd-amd64.log"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+attachment/5519348/+files/lxd-amd64.log
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status:
Some context:
https://github.com/riscv/riscv-gnu-toolchain/issues/738
https://sourceware.org/bugzilla/show_bug.cgi?id=25181
According to the latter, this should already be fixed in upstream
binutils since several years... why does it still happen?
--
You received this bug notification because yo
Public bug reported:
monero FTBFS on riscv64 due to toolchain issues:
[ 64%] Linking CXX executable signature_fuzz_tests
cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E
cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1
/usr/bin/c++ -g -O2 -ffile-prefix-map
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1850667
Title:
Switch to "unified" cgroup hierarchy (cgroupv2)
Status in lxc:
Fix Released
S
** Information type changed from Private to Public
** Changed in: systemd (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1929184
Thank you for providing & integrating the patches. LGTM!
$ dput ubuntu ../e2fsprogs_1.46.3-1ubuntu2_source.changes
Checking signature on .changes
gpg: ../e2fsprogs_1.46.3-1ubuntu2_source.changes: Valid signature from
5889C17AB1C8D890
Checking signature on .dsc
gpg: ../e2fsprogs_1.46.3-1ubuntu2.ds
** Changed in: e2fsprogs (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1939409
Title:
merge e2fsprogs 1.46.3-1 from Debian: s
Denys, what kind of MDNS traffic is flowing in your network? I'm not
really able to reproduce the problem locally. Maybe I'm missing this
special network packets?
Have you already been able to find out what triggers the issue for you?
--
You received this bug notification because you are a membe
** Description changed:
- systemd-resolve keep crashing and it is very annoying as sometimes it
- severely interrupt normal dns resolving.
+ [Impact]
+
+ * systemd-resolved stops replying to clients on the local LAN.
+ * logging segfault crashes in dmesg:
+ [836786.046514] systemd-resolve[87200
** Patch added: "Hirsute"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512243/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1936948
Title:
Dependency loop via sockets.target
Status in dbus package in Ubuntu:
New
Bug
Public bug reported:
basic.target waits for dbus.socket (via sockets.target) AND dbus.socket
waits for basic.target, too, delaying dbus-daemon startup. At some point
a timeout happens, dbus is started and all queued services try to start
registering to the bus at the same time.
All services regis
Thank you for providing a patch! That patch looks straight forward and
(almost) resembles the upstream change, obviously missing the parts that
do not yet exist in systemd v245.
The only other thing I found missing is an upstream change in
src/resolve/resolved-dns-transaction.c:
```
static void
systemd v248 as can be found in Impish already contains the upstream
fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
Status in
** Patch added: "Focal"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5512235/+files/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch
** Also affects: systemd (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: systemd
After enabling the unified cgroups hierarchy in systemd and running some
tests, I can confirm that most things are working as expected, except
for snapd.
https://bileto.ubuntu.com/excuses/4602/impish.html
The Bileto autopkgtests show (ignoring two unrelated/flaky failures in
universe packages: su
After reading a bit more about this issue, I can see where the conflict
happens:
1/ systemd requires any container manager to mount /sys read-only,
according to https://systemd.io/CONTAINER_INTERFACE/ in order to make
udevd behave properly.
2/ NetworkManager checks for /sys to be read-only in ord
This should have been fixed upstream by:
https://github.com/systemd/systemd/pull/18559
Or https://github.com/systemd/systemd/pull/18684 and
https://github.com/systemd/systemd/pull/18717 respectively. I wonder why
this fix isn't working for network-manager, while it seems to be good
for LXD?
--
Y
Related to: LP: #1914062
Two patches exist, both were dropped from their corresponding packages:
https://git.launchpad.net/network-manager/commit/?id=4c4f7172
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/systemd/commit/?h=ubuntu-
impish&id=efebddfe37efff6a259ef7fd59212d65ad1b848b
Public bug reported:
The nm-online util does not return successfully as of 1.32.2-0ubuntu1
(currently in impish-proposed).
systemd VS network-manager autopkgtests (in LXD) fail, because the
autopkgtest-virt-lxd runner tries to wait for "network ready" before it
is reconnecting after a reboot. Thi
Thanks, I've sponsored the HH & FF uploads.
** Changed in: shadow (Ubuntu Focal)
Status: Fix Committed => In Progress
** Changed in: shadow (Ubuntu Hirsute)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Thanks William, this LGTM now!
I've modified your debian/changelog and the XML/man pages a bit, to
account for the removed handling of floating point numbers. And uploaded
the package.
$ dput ubuntu ../shadow_4.8.1-1ubuntu9_source.changes
D: Setting host argument.
Checking signature on .changes
g
Thank you! This one is looking pretty solid overall.
But I think the "hex detection" has some flaws, as it only checks for capital
letters and there is a discrepancy between accepting float hex numbers (which
is unexpected IMO) but rejecting float octal numbers.
Could you please test for some mo
** Changed in: lxd (Ubuntu Impish)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1931088
Title:
boot-and-services tests fails
401 - 500 of 562 matches
Mail list logo
