Version-Release number of selected component: systemd-248-2.fc34 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/systemd-resolved.service cmdline: /usr/lib/systemd/systemd-resolved crash_function: sd_event_source_set_enabled executable: /usr/lib/systemd/systemd-resolved journald_cursor: s=9dcd58e0156141d3847d822227c8a4ca;i=ab4973;b=f61ec4731da94d59bd9334881709a730;m=47c64620c;t=5c00c08b7ba7a;x=4d353e7713b22bee kernel: 5.11.13-300.fc34.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 193 Truncated backtrace: Thread no. 1 (10 frames) #0 sd_event_source_set_enabled at ../src/libsystemd/sd-event/sd-event.c:2530 #1 sd_event_source_disable_unref at ../src/libsystemd/sd-event/sd-event.c:426 #2 dns_query_stop at ../src/resolve/resolved-dns-query.c:328 #3 dns_query_complete at ../src/resolve/resolved-dns-query.c:561 #4 on_query_timeout at ../src/resolve/resolved-dns-query.c:572 #5 source_dispatch at ../src/libsystemd/sd-event/sd-event.c:3520 #6 sd_event_dispatch at ../src/libsystemd/sd-event/sd-event.c:4077 #7 sd_event_run at ../src/libsystemd/sd-event/sd-event.c:4138 #8 sd_event_loop at ../src/libsystemd/sd-event/sd-event.c:4159 #9 run at ../src/resolve/resolved.c:92
Created attachment 1772360 [details] File: backtrace
Created attachment 1772361 [details] File: core_backtrace
Created attachment 1772362 [details] File: cpuinfo
Created attachment 1772363 [details] File: dso_list
Created attachment 1772364 [details] File: environ
Created attachment 1772365 [details] File: exploitable
Created attachment 1772366 [details] File: limits
Created attachment 1772367 [details] File: maps
Created attachment 1772368 [details] File: mountinfo
Created attachment 1772369 [details] File: open_fds
Created attachment 1772370 [details] File: proc_pid_status
I hope this is fixed by https://github.com/systemd/systemd/pull/19607. It's hard to say for certain with memory corruptions.
*** Bug 1957572 has been marked as a duplicate of this bug. ***
FEDORA-2021-db78c3c7f1 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-db78c3c7f1
FEDORA-2021-db78c3c7f1 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-db78c3c7f1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-db78c3c7f1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-db78c3c7f1 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
Similar problem has been detected: no idea reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/system.slice/systemd-resolved.service cmdline: /usr/lib/systemd/systemd-resolved crash_function: sd_event_source_set_enabled executable: /usr/lib/systemd/systemd-resolved journald_cursor: s=90e736f9eb4c4edb883eb5698ed54305;i=86f08;b=7b2360833c8c4bfc9f8360dab3ffc3d6;m=16f2ea547d;t=5cd8e7c8a5da6;x=f661fcc6134d7888 kernel: 5.14.9-200.fc34.x86_64 package: systemd-248.7-1.fc34 reason: systemd-resolved killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 193