Locally installed services can't add dbus configuration

Bug #1811152 reported by Mario Limonciello on 2019-01-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
High
Unassigned

Bug Description

A report was received in upstream fwupd about how the daemon wasn't able to start after the following commands:

# meson build
# ninja -C build
# ninja -C build install

This placed everything in /usr/local by default.
It also created an /usr/local/etc/dbus-1/system.d/org.freedesktop.conf

The daemon can (attempt to) be started by:
/usr/local/libexec/fwupd/fwupd -v

It fails to acquire org.freedesktop.fwupd on dbus system bus however.

This is because by default dbus on Ubuntu does not examine files in /usr/local/etc/dbus-1/system.d.

This issue can be fixed if the following is added to /usr/share/dbus-1/system.conf:

    <includedir>/usr/local/etc/dbus-1/system.d</includedir>

Sebastien Bacher (seb128) wrote :

Did you check if the issue is specific to Ubuntu? https://gitlab.freedesktop.org/dbus/dbus/blob/dbus-1.12/bus/system.conf.in doesn't seem to include it either upstream?

Mario Limonciello (superm1) wrote :

I did not check upstream yet no, thanks for checking. I'll report it upsteam as well.

Mario Limonciello (superm1) wrote :

I filed the issue upstream as well.
https://gitlab.freedesktop.org/dbus/dbus/issues/253

Sebastien Bacher (seb128) wrote :

Thanks

Changed in dbus (Ubuntu):
importance: Undecided → High
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers