Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1902819 - systemd (pid 1) segfaults at system shutdown or reboot
Summary: systemd (pid 1) segfaults at system shutdown or reboot
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
Whiteboard: openqa
Depends On:
Blocks: F34BetaBlocker
TreeView+ depends on / blocked
Reported: 2020-11-30 18:57 UTC by Adam Williamson
Modified: 2020-12-01 11:34 UTC (History)
13 users (show)

Fixed In Version: systemd-247.1-1.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-12-01 11:34:47 UTC
Type: Bug

Attachments (Terms of Use)

Description Adam Williamson 2020-11-30 18:57:33 UTC
In current Rawhide, with systemd-247-1.fc34, systemd (pid 1) frequently segfaults on system shutdown or reboot.

openQA is running into this in several tests. Most obviously base_service_manipulation, which involves enabling/disabling services and rebooting several times, e.g. here's one such failure:

but it's also hitting other tests too sometimes. Several tests have to do a clean shutdown so they can upload disk images for other tests to use, and these are frequently hitting this bug too.

damjan says it's likely upstream issue that should be fixed by , but this is such a critical issue I don't really want to backport an unreviewed PR myself.

Proposing as a Beta blocker per "It must be possible to trigger a clean system shutdown using standard console commands" -

Comment 1 Adam Williamson 2020-11-30 20:10:48 UTC
In I believe we hit a segfault on `systemctl isolate`.

Comment 2 Zbigniew Jędrzejewski-Szmek 2020-12-01 11:34:47 UTC
Should be OK now.

Note You need to log in before you can comment on or make changes to this bug.