This bug was fixed in the package systemd - 245.4-4ubuntu3.15
---
systemd (245.4-4ubuntu3.15) focal-security; urgency=medium
* SECURITY UPDATE: systemd-tmpfiles could be made to crash.
- d/p/rm-rf-refactor-rm-rf-children-split-out-body-of-directory.patch:
Backport
This bug was fixed in the package systemd - 247.3-3ubuntu3.7
---
systemd (247.3-3ubuntu3.7) hirsute-security; urgency=medium
* SECURITY UPDATE: systemd-tmpfiles could be made to crash.
- d/p/rm-rf-refactor-rm-rf-children-split-out-body-of-directory.patch:
Backport
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
My system is focal. Can't try Hirsute yet, dont have any systems with
such error appearing.
It doesnt work at all for me, fail to resolve anything
Link 2 (enp3s0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
Sorry for very long delay, many bad events in life. I will give it a try
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about
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
** Merge proposal linked:
https://code.launchpad.net/~slyon/ubuntu/+source/systemd/+git/systemd/+merge/408886
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve
Yes it seems i am still seeing crashes too. They are more rare, but
still appearing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications
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
This bug was fixed in the package systemd - 247.3-3ubuntu3.6
---
systemd (247.3-3ubuntu3.6) hirsute; urgency=medium
* d/p/dell-clamshell-accel-location-base-with-sku.patch:
Revert incorrect patch (LP: #1942899)
systemd (247.3-3ubuntu3.5) hirsute; urgency=medium
[ Yao Wei ]
This bug was fixed in the package systemd - 245.4-4ubuntu3.13
---
systemd (245.4-4ubuntu3.13) focal; urgency=medium
* d/p/dell-clamshell-accel-location-base-with-sku.patch:
Revert incorrect patch (LP: #1942899)
systemd (245.4-4ubuntu3.12) focal; urgency=medium
[ Yao Wei ]
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]
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]
Started testing on my PC.
Ubuntu Hiruste will be a bit difficult to run, but i will try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage
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
Hello Denys, or anyone else affected,
Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.12 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Denys, or anyone else affected,
Accepted systemd into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/systemd/247.3-3ubuntu3.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Focal)
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/1934221
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Hirsute)
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/1934221
I recorded pcap and captured moment just before crash. It doesnt looks
like there was any MDNS at all at this moment, only suspicious is many
weird DNS requests. (spinesystems.solutions is my local domain set on
pc). Not sure what generated them.
Small snap of these:
02:16:36.658522 IP
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
** 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]
** 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
Bugs, which is subscribed to
1. No, my skills are just not enough to spot it.
I noticed warning in valgrind (but it was once only and not crash), but was not
able to trace back reason. Very likely your patch fix that.
2. In my network i have some MDNS devices, and probably some combination of
them and their connectivity
** 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 v248 as can be found in Impish already contains the upstream
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about this
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
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Tags added: fr-1490
** Tags removed: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about this bug go to:
As far as i can see - no crashes anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934221
Title:
systemd-resolve segfault
To manage notifications about this bug go to:
The attachment "Backported bugfix" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
Not sure if i backported patch correctly, some functions is missing in 245.4
Build is OK, testing it, no crashes yet, but will have conclusive results in
~24h.
** Patch added: "Backported bugfix"
Most likely i found patch that fix this problem:
https://github.com/systemd/systemd/commit/97935302283729c9206b84f5e00b1aff0f78ad19
And associated issue have striking similarity
https://github.com/systemd/systemd/issues/18427
Will try to test it today if it fixes my issue as well.
** Bug watch
Here is more meaningful result from valgrind with dbgsym present
** Attachment added: "vagrind output"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5508373/+files/valgrind-bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I run it with valgrind and here is what i got:
(not sure yet how to add debug symbols, will try it too)
root@threadpc:~# valgrind -v /lib/systemd/systemd-resolved
==1798854== Memcheck, a memory error detector
==1798854== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1798854==
Here is backtrace, as i am unable to attach crash report (launchpad gives error)
apport-retrace -g _lib_systemd_systemd-resolved.102.crash
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
36 matches
Mail list logo
