Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#72539 - [wireplumber,pipewire-pulse] wireplumber.service + pipewire-pulse not working after boot

Attached to Project: Arch Linux
Opened by m1s4k1 (m1s4k1) - Monday, 25 October 2021, 11:11 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 09 February 2022, 15:52 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
wireplumber.service is inactive after boot so if I try to run mpv (pulse) it throws an error:

[ao] Failed to initialize audio driver 'pulse'
Could not open/initialize audio device -> no sound.

After that the service activates itself (dbus activation?) and everything works fine. Service activation can be triggered by any pactl command or by systemctl --user start.
Probably it's intended behavior but I don't have this issue with pipewire-media-session.

Additional info:
* WM: sway

* package version(s):
pipewire 1:0.3.39-1
wireplumber 0.4.4-3

* config and/or log files etc.
Default configuration

Steps to reproduce:
1. Reboot & login
2. Check wireplumber.service:
systemctl --user status pipewire-session-manager.service
○ wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
Active: inactive (dead)
3. Run mpv:
mpv file
...
[ao] Failed to initialize audio driver 'pulse'
Could not open/initialize audio device -> no sound.
Audio: no audio

Exiting... (Errors when loading file)
4. Check the service again:
systemctl --user status wireplumber.service
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-10-25 13:51:40 EEST; 6s ago
Main PID: 733 (wireplumber)
Tasks: 5 (limit: 16647)
Memory: 11.6M
CPU: 137ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─733 /usr/bin/wireplumber
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 09 February 2022, 15:52 GMT
Reason for closing:  Not a bug
Additional comments about closing:  As requested by OP.
Comment by m1s4k1 (m1s4k1) - Monday, 25 October 2021, 11:19 GMT
I've added 'exec systemctl --user start wireplumber.service' to sway config but it'd be nice if PA apps can work automatically.
Comment by David Runge (dvzrv) - Monday, 25 October 2021, 13:45 GMT
@m1s4k1: Thanks for the report.

The wireplumber.service is enabled globally (for all users) by default after installation (so it *should* be running already).
Both pipewire-pulse.service and pipewire.service are socket activated (both pipewire-pulse.socket and pipewire.socket are globally enabled for all users) which might explain the issue you are seeing.

Can you tests whether explicitly enabling both user services pipewire.service and pipewire-pulse.service fixes this issue for you after a reboot?
Comment by m1s4k1 (m1s4k1) - Monday, 25 October 2021, 15:40 GMT
@dvzrv Yes, explicitly enabling these services fixes the issue. Thank you!
Comment by David Runge (dvzrv) - Tuesday, 08 February 2022, 17:41 GMT
@m1s4k1 is this still a problem with current wireplumber and pipewire?
Comment by m1s4k1 (m1s4k1) - Wednesday, 09 February 2022, 04:14 GMT
@dvzrv I still need to keep the services manually enabled but I don't think it's an issue. So let's close this.
Thanks for the help.

Loading...