Bug 2443620 - Rawhide with systemd-260~rc1-5.fc45.x86_64 no longer reports tmp.mount as dependency
Summary: Rawhide with systemd-260~rc1-5.fc45.x86_64 no longer reports tmp.mount as dep...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-03-01 08:21 UTC by Jan Pazdziora
Modified: 2026-03-03 17:51 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-03-02 18:23:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 40915 0 None None None 2026-03-02 17:15:02 UTC

Description Jan Pazdziora 2026-03-01 08:21:17 UTC
Running 

systemctl list-dependencies dbus-broker.service

used to report

● ├─dbus.socket
● ├─system.slice
● └─tmp.mount

in a Fedora container. In rawhide it now reports

dbus-broker.service
● ├─dbus.socket
● └─system.slice


Reproducible: Always

Steps to Reproduce:

1. Have Dockerfile

FROM registry.fedoraproject.org/fedora
RUN dnf install -y systemd
ENTRYPOINT [ "/usr/sbin/init" ]

2. podman build --from registry.fedoraproject.org/fedora:rawhide -t localhost/systemd .
3. podman run --rm -t --name systemd localhost/systemd
4. In another terminal

podman exec systemd systemctl list-dependencies dbus-broker.service

2.
3.
Actual Results:

dbus-broker.service
● ├─dbus.socket
● └─system.slice



Expected Results:

Up until Fedora 43 the output is

dbus-broker.service
● ├─dbus.socket
● ├─system.slice
● └─tmp.mount


Additional Information:

This is with

$ podman exec systemd rpm -q systemd
systemd-260~rc1-5.fc45.x86_64

The service definition is exactly the same as it is in a Fedora 43 container:

$ podman exec systemd systemctl status dbus-broker.service
● dbus-broker.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sun 2026-03-01 08:14:57 UTC; 29s ago
 Invocation: 055ed01049bf4faa9b2ea970485e2ea8
TriggeredBy: ● dbus.socket
       Docs: man:dbus-broker-launch(1)
   Main PID: 75 (dbus-broker-lau)
      Tasks: 2 (limit: 307)
     Memory: 1.4M (peak: 2.2M)
        CPU: 23ms
     CGroup: /system.slice/dbus-broker.service
             ├─75 /usr/bin/dbus-broker-launch --scope system --audit
             └─78 dbus-broker --log 10 --controller 9 --machine-id 8f7f9bf5ff244f99b8a004a5c6b5b5dc --max-bytes 536870912 --max-fds 4096 --max-matches 16384 --audit

Mar 01 08:14:57 61e5394c83de systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus...
Mar 01 08:14:57 61e5394c83de systemd[1]: Started dbus-broker.service - D-Bus System Message Bus.
Mar 01 08:14:57 61e5394c83de dbus-broker-launch[75]: Ready

$ podman exec systemd cat /usr/lib/systemd/system/dbus-broker.service
[Unit]
Description=D-Bus System Message Bus
Documentation=man:dbus-broker-launch(1)
DefaultDependencies=false
After=dbus.socket
Before=basic.target shutdown.target
Requires=dbus.socket
Conflicts=shutdown.target

[Service]
Type=notify-reload
Sockets=dbus.socket
OOMScoreAdjust=-900
LimitNOFILE=16384
ProtectSystem=full
PrivateTmp=true
PrivateDevices=true
ExecStart=/usr/bin/dbus-broker-launch --scope system --audit

[Install]
Alias=dbus.service

The tmp.mount is still listed as mounted:

$ podman exec systemd systemctl status tmp.mount
● tmp.mount - Temporary Directory /tmp
     Loaded: loaded (/proc/self/mountinfo; static)
     Active: active (mounted) since Sun 2026-03-01 08:14:57 UTC; 2min 50s ago
 Invocation: 6986e2c84cac45ed8e33a85cc5c90134
      Where: /tmp
       What: tmpfs
       Docs: https://systemd.io/TEMPORARY_DIRECTORIES
             man:file-hierarchy(7)
             https://systemd.io/API_FILE_SYSTEMS

Notice: journal has been rotated since unit was started, output may be incomplete.

Comment 1 Lukáš Nykrýn 2026-03-02 13:23:21 UTC
What is the actual problem here?

Comment 2 Jan Pazdziora 2026-03-02 13:32:11 UTC
Change of behaviour that I did not find documented or acknowledge anywhere in changelogs, so I suspect it may be a bug.

Comment 3 Yu Watanabe 2026-03-02 16:59:55 UTC
This may be 'caused' by https://github.com/systemd/systemd/pull/39790 .
Should be expected behavior change.
Maybe NEWS file should be improved.

Comment 4 Jan Pazdziora 2026-03-02 18:23:23 UTC
Perfect, thanks for the pointer. I guess with the upstream issue, this Fedora bugzilla can be closed.

Comment 5 Zbigniew Jędrzejewski-Szmek 2026-03-03 17:51:36 UTC
Pushed https://github.com/systemd/systemd/commit/6e0f0510d2 now.


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