Package: pipewire
Version: 1.4.2-1
Severity: normal

Dear Maintainer,

I was experimenting no sound and errors starting pipewire.socket:

pipewire.socket: Failed to queue service startup job: Unit dbus.service not found.
pipewire.socket: Failed with result 'resources'.

Since 1.4.2, user service requires dbus user service.

Installing dbus-user-session solved the problem.

Maybe you should recommend or suggest dbus-user-session.

Thanks,

Alex

-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.25-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pipewire depends on:
ii adduser 3.150
ii init-system-helpers 1.68
ii libpipewire-0.3-modules 1.4.2-1
ii pipewire-bin 1.4.2-1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Alexandre,

On 4/29/25 07:04, Alexandre Rossi wrote:

I was experimenting no sound and errors starting pipewire.socket:

pipewire.socket: Failed to queue service startup job: Unit dbus.service not found.
pipewire.socket: Failed with result 'resources'.

Since 1.4.2, user service requires dbus user service.

Installing dbus-user-session solved the problem.

Maybe you should recommend or suggest dbus-user-session.

Thanks for your bug report.

pipewire.{socket,service} are provided by the package "pipewire" which
depends on "pipewire-bin". And "pipewire-bin" already recommends "dbus-user-session".

So, adding a new recommend will probably not help. Now the question is:
what is your configuration for not having dbus-user-session despite it
being listed in recommends?

Best regards,
Dylan

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

I was experimenting no sound and errors starting pipewire.socket:

pipewire.socket: Failed to queue service startup job: Unit dbus.service not found.
pipewire.socket: Failed with result 'resources'.

Since 1.4.2, user service requires dbus user service.

Installing dbus-user-session solved the problem.

Maybe you should recommend or suggest dbus-user-session.

Thanks for your bug report.

pipewire.{socket,service} are provided by the package "pipewire" which depends on "pipewire-bin". And "pipewire-bin" already recommends "dbus-user-session".

So, adding a new recommend will probably not help. Now the question is:
what is your configuration for not having dbus-user-session despite it
being listed in recommends?

I guess this is because of me using APT::Get::Install-Recommends "false".
If the recommends is indirect, this may be fine and this can be closed. I
do not know the pipewire dep tree enough to have a strong opinion on this.

Thanks for looking into this,

Alex

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)