Your message dated Mon, 9 Feb 2026 09:36:41 +0100
with message-id <[email protected]>
and subject line Re: Bug#1127422: pipewire cannot be started in --system mode
has caused the Debian Bug report #1127422,
regarding pipewire cannot be started in --system mode
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1127422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127422
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pipewire
Version: 1.4.2-1
Severity: important

Dear Maintainer,

On my Debian desktop, various applications are running under a different
user than the logged in user.  Thus, those applications cannot produce
sound if pipewire is started in --user mode.

(In fact, those applications start their own pipewire instance, but since
the desktop is running under the logged in user, those other pipewire
instances have no way to output sound.)

I've experienced this behavior with pulseaudio as well, but it was trivial
to start pulseaudio in --system mode.  However, running

```
systemctl --system start wireplumber pipewire pipewire-pulse
```

yields error messages

```
Failed to start wireplumber.service: Unit wireplumber.service not found.
Failed to start pipewire.service: Unit pipewire.service not found.
Failed to start pipewire-pulse.service: Unit pipewire-pulse.service not found.
```

I agree that --system mode should not be the default, but it should be
at least possible if so desired.

[Error sent manually, since reportbug fails to send emails.]


-- System Information:
Debian Release: 13.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.63+deb13-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pipewire depends on:
ii  adduser                  3.152
ii  init-system-helpers      1.69~deb13u1
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

--- End Message ---
--- Begin Message ---
Version: 1.4.7-2

On 08/02/2026 16:00, Dylan Aïssi wrote:
Hi,

On 08/02/2026 14:24, Ralph Benzinger wrote:
I agree that --system mode should not be the default, but it should be
at least possible if so desired.

Please take a look at the package pipewire-system-services

Best regards,
Dylan

--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to