Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W wireplumber
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 86
    • Issues 86
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWire
  • wireplumber
  • Issues
  • #186
Closed
Open
Created Jan 31, 2022 by Oliver Fürniß@oliver.fuerniss

Fedora 35 : wireplumber service does not respond

  • Pipewire version: 0.3.44-1.fc35
  • Wireplumber version: 0.4.7-2.fc35
  • Distribution and distribution version (PRETTY_NAME from /etc/os-release): Fedora Linux 35 (Workstation Edition)
  • Desktop Environment: Gnome 41.3
  • Kernel version (uname -r): 5.15.17-200.fc35.x86_64

Description of Problem

Have done a regular Fedora 35 update this morning (2022-01-31; last one on friday). I've seen that it has been updated pipewire & wireplumber. And since then I have no more audio devices in the Gnome Audio settings and it takes forever on shut down (systemd waits for wireplumber to exit).

Additional Info

> systemctl --user status pipewire pipewire-pulse wireplumber                                                                                                                                                 

● pipewire.service - PipeWire Multimedia Service
     Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/user/pipewire.service.d
             └─00-uresourced.conf
     Active: active (running) since Mon 2022-01-31 16:34:03 CET; 31s ago
TriggeredBy: ● pipewire.socket
   Main PID: 2344 (pipewire)
      Tasks: 2 (limit: 38109)
     Memory: 1.7M
        CPU: 14ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
             └─2344 /usr/bin/pipewire

Jan 31 16:34:03 ofs-skully systemd[1982]: Started PipeWire Multimedia Service.

● pipewire-pulse.service - PipeWire PulseAudio
     Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; vendor preset: disabled)
     Active: active (running) since Mon 2022-01-31 16:34:03 CET; 31s ago
TriggeredBy: ● pipewire-pulse.socket
   Main PID: 2346 (pipewire-pulse)
      Tasks: 2 (limit: 38109)
     Memory: 1.4M
        CPU: 8ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
             └─2346 /usr/bin/pipewire-pulse

Jan 31 16:34:03 ofs-skully systemd[1982]: Started PipeWire PulseAudio.

● wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-01-31 16:34:03 CET; 31s ago
   Main PID: 2345 (wireplumber)
      Tasks: 4 (limit: 38109)
     Memory: 3.6M
        CPU: 29ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─2345 /usr/bin/wireplumber

Jan 31 16:34:03 ofs-skully systemd[1982]: Started Multimedia Service Session Manager.
> pipewire --version                                                                                                                                                                                          
pipewire
Compiled with libpipewire 0.3.44
Linked with libpipewire 0.3.44

But

  • pw-dump > pw-dump.log does not respond
  • wpctl status does not respond
  • systemctl --user stop wireplumber.service does not respond (takes minutes until the shell prompt comes back and then the service is still not stopped)

This is the service status after the shell prompt comes back:

systemctl --user status wireplumber.service                                                                                                                                                         × wireplumber.service - Multimedia Service Session Manager
     Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Mon 2022-01-31 17:04:12 CET; 57s ago
   Main PID: 2345
      Tasks: 1 (limit: 38109)
     Memory: 3.6M
        CPU: 30ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
             └─2345 /usr/bin/wireplumber

Jan 31 16:58:11 ofs-skully systemd[1982]: Stopping Multimedia Service Session Manager...
Jan 31 16:59:41 ofs-skully systemd[1982]: wireplumber.service: State 'stop-sigterm' timed out. Killing.
Jan 31 16:59:41 ofs-skully systemd[1982]: wireplumber.service: Killing process 2345 (wireplumber) with signal SIGKILL.
Jan 31 17:01:11 ofs-skully systemd[1982]: wireplumber.service: Processes still around after SIGKILL. Ignoring.
Jan 31 17:02:42 ofs-skully systemd[1982]: wireplumber.service: State 'final-sigterm' timed out. Killing.
Jan 31 17:02:42 ofs-skully systemd[1982]: wireplumber.service: Killing process 2345 (wireplumber) with signal SIGKILL.
Jan 31 17:04:12 ofs-skully systemd[1982]: wireplumber.service: Processes still around after final SIGKILL. Entering failed mode.
Jan 31 17:04:12 ofs-skully systemd[1982]: wireplumber.service: Failed with result 'timeout'.
Jan 31 17:04:12 ofs-skully systemd[1982]: wireplumber.service: Unit process 2345 (wireplumber) remains running after unit stopped.
Jan 31 17:04:12 ofs-skully systemd[1982]: Stopped Multimedia Service Session Manager.

Anything else I can provide to solve the problem?

Edited Jan 31, 2022 by Oliver Fürniß
Assignee
Assign to
Time tracking