The next time you hit this issue, please provide the output of these
commands,

$ journalctl --user -u pipewire -u pipewire-pulse -u wireplumber -b
$ pactl list sinks
$ wpctl status
$ pw-cli list-objects Node
$ pw-dump

Since you said you're trying to restart *pulseaudio*, I'm concerned you
might have conflicting sound servers running (although your package list
suggest not), but to be sure,

$ ps aux | grep -E 'pulseaudio|jackd'

Shouldn't report anything (other than grep).

If that doesn't help provide any further clues, debug logging from
Pipewire and friends will be required. For the pipewire daemon in
particular,

$ export DEBUGINFOD_URLS="https://debuginfod.elfutils.org/ $DEBUGINFOD_URLS"
$ timeout 5 strace -f -tt -T -p `pidof pipewire` > pipewire_strace.out
$ timeout 5 perf record --debuginfod -g -p `pidof pipewire`
$ perf report > pipewire_perf.out

If you have custom configuration configuration of Pipewire share that
too. There are reports against your version of Pipewire of the CPU
getting locked when resuming from suspend,

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3984, and
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4025

You might try seeing if this can consistently reproduce the issue,

PIPEWIRE_LOG_SYSTEMD=false PIPEWIRE_DEBUG=3 pw-cli -m load-module
libpipewire-module-combine-stream




** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #3984
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3984

** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #4025
   https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4025

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2111972

Title:
  Pipewire uses 100% of a CPU core. Can not connect to pulseaudio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2111972/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to