Arch Linux

Rec100

Member

Registered: 2022-03-12

Posts: 29

Struggeling with PipeWire,

I am following the notes on https://wiki.archlinux.org/title/PipeWire trying to get some sound out of my Lenovo ThinkPad X1 Carbon (Gen 9), which runs a fresh Arch installation on a new SSD after a I had a disk failure. From what I read, I do not need EasyEffects to get PipeWire working.

There is only minimum sound coming out of the machine. What I did so far:

sudo pacman -S pipewire pipewire-audio pipewire-jack pipewire-pulse wireplumber sof-firmware

and

cp /usr/share/pipewire/*.conf ~/.config/pipewire/

There is no pulseaudio or pulseaudio-bluetooth on the machine.

I am stuck at https://wiki.archlinux.org/title/PipeWi … io_clients:

The advice is to "systemctl start pipewire-pulse.service" but all I'm getting is a "Failed to start pipewire-pulse.service: Unit pipewire-pulse.service not found." I've logged out and in again, I've rebooted. Still does not work, neither does "systemctl --user enable pipewire-pulse.service" wich shows "Failed to connect to bus: No medium found".

However, pactl works:

$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 101
Tile Size: 65472
User Name: user
Host Name: host
Server Name: PulseAudio (on PipeWire 1.0.5)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink
Default Source: alsa_input.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_6__source
Cookie: f3cd:3f23

How do I proceed to get the sound to 'normal' levels? I guess I need pipewire-pulse.service.

Last edited by Rec100 (2024-04-22 12:23:53)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,831

Re: Struggeling with PipeWire,

Your systemctl command fails because you are acting on the system bus, while all relevant pipewire services are on the user bus. Add --user to your systemctl commands checking pipewire states.

I'd also suggest you remove the "default config copy" from your home dir again, if you're not changing anything you will miss automatic changes you'd get via packages for no gain.

Check what the audio levels of your sink are

pactl list sinks
pactl set-sink-volume $SINKNAME 100% #to set them

I'd strongly suggest you install pavucontrol or so as it will give you an intuitive GUI with information on your audio levels.

If that doesn't solve it, post

sudo fuser -v /dev/snd/*
aplay -lL
amixer -c0 #Or whatever index your actual card is
pactl list cards
pactl list sinks

and post those wrapped in [ code ] [ /code ] tags without the spaces

Last edited by V1del (2024-04-21 17:44:53)

Rec100

Member

Registered: 2022-03-12

Posts: 29

Re: Struggeling with PipeWire,

V1del, thanks for looking into this with me.

* I've installed pavucontrol (it does not connect to anything),
* I've removed ~/.config/pipewire/ as you suggested
* Unfortunately, pactl is not working anymore

pactl info
Connection failure: Timeout

$ pactl list sinks
Connection failure: Timeout

Because I still could not start the pipewire-pulse.service (systemctl --user start pipewire-pulse.service), I re-ran "$ sudo pacman -S pipewire pipewire-audio pipewire-jack pipewire-pulse wireplumber" again, to make sure, everything is installed:

$ sudo pacman -S pipewire pipewire-audio pipewire-jack pipewire-pulse wireplumber
warning: pipewire-1:1.0.5-1 is up to date -- reinstalling
warning: pipewire-audio-1:1.0.5-1 is up to date -- reinstalling
warning: pipewire-pulse-1:1.0.5-1 is up to date -- reinstalling
warning: wireplumber-0.5.1-2 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
:: pipewire-jack-1:1.0.5-1 and jack2-1.9.22-1 are in conflict (jack). Remove jack2? [y/N]

I removed jack2. The installation went well.

$ sudo fuser -v /dev/snd/*
[sudo] password for user: 
                     USER        PID ACCESS COMMAND
/dev/snd/controlC0:  user       2697 F.... pipewire
                     user       2708 F.... wireplumber
/dev/snd/seq:        user       2697 F.... pipewire

Last edited by Rec100 (2024-04-22 12:26:28)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,831

Re: Struggeling with PipeWire,

What does "could not start pipewire-pulse" mean exactly? How are you starting your session? If via startx, make sure you include the necessary includes to properly populate the user session: https://wiki.archlinux.org/title/Xinit#xinitrc -- read the blue note boxes.

Maybe also post the link you get from

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Rec100

Member

Registered: 2022-03-12

Posts: 29

Re: Struggeling with PipeWire,

With "could not start pipewire-pulse service" I meant:

$ systemctl --user start pipewire-pulse.service
Failed to connect to bus: No medium found

The output of journalctl -b can be found here:
https://0x0.st/s/x5Fj6V9enjp4qk_xEBRgSA/Xonb.txt

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,831

Re: Struggeling with PipeWire,

Your user bus is broken for some reason, are you using dbus-launch somewhere? What do you get from

printenv

from a terminal?

Rec100

Member

Registered: 2022-03-12

Posts: 29

Re: Struggeling with PipeWire,

Printenv:

SHELL=/usr/bin/bash
SESSION_MANAGER=local/host:@/tmp/.ICE-unix/2207,unix/host:/tmp/.ICE-unix/2207
COLORTERM=truecolor
XDG_MENU_PREFIX=gnome-
TERM_PROGRAM_VERSION=46.0
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXgVcIK1/agent.8067
MEMORY_PRESSURE_WRITE=c29tZSAyMDAwMDAgMjAwMDAwMAA=
DESKTOP_SESSION=gnome
SSH_AGENT_PID=8068
EDITOR=/usr/bin/vi
PWD=/home/user/Desktop
LOGNAME=user
XDG_SESSION_DESKTOP=gnome
XDG_SESSION_TYPE=wayland
SYSTEMD_EXEC_PID=3775
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.31ALM2
MOTD_SHOWN=pam
GDM_LANG=en_US.UTF-8
HOME=/home/user
USERNAME=user
LANG=en_US.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.7z=01;31:*.ace=01;31:*.alz=01;31:*.apk=01;31:*.arc=01;31:*.arj=01;31:*.bz=01;31:*.bz2=01;31:*.cab=01;31:*.cpio=01;31:*.crate=01;31:*.deb=01;31:*.drpm=01;31:*.dwm=01;31:*.dz=01;31:*.ear=01;31:*.egg=01;31:*.esd=01;31:*.gz=01;31:*.jar=01;31:*.lha=01;31:*.lrz=01;31:*.lz=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.lzo=01;31:*.pyz=01;31:*.rar=01;31:*.rpm=01;31:*.rz=01;31:*.sar=01;31:*.swm=01;31:*.t7z=01;31:*.tar=01;31:*.taz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tgz=01;31:*.tlz=01;31:*.txz=01;31:*.tz=01;31:*.tzo=01;31:*.tzst=01;31:*.udeb=01;31:*.war=01;31:*.whl=01;31:*.wim=01;31:*.xz=01;31:*.z=01;31:*.zip=01;31:*.zoo=01;31:*.zst=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.crdownload=00;90:*.dpkg-dist=00;90:*.dpkg-new=00;90:*.dpkg-old=00;90:*.dpkg-tmp=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:*.swp=00;90:*.tmp=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:
XDG_CURRENT_DESKTOP=GNOME
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/app.slice/app-dbus\x2d:1.2\x2dorg.gnome.Console.slice/dbus-:1.2-org.gnome.Console@0.service/memory.pressure
VTE_VERSION=7601
WAYLAND_DISPLAY=wayland-0
INVOCATION_ID=ad3b8d0e2f9148c9b7773912404bcd86
MANAGERPID=2119
GNOME_SETUP_DISPLAY=:1
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=user
DISPLAY=:0
SHLVL=1
XDG_RUNTIME_DIR=/run/user/1000
PS1=[\u@\h \[\033[32m\]\w\[\033[33m\]$(parse_git_branch)\[\033[00m\]] \n$ 
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
JOURNAL_STREAM=8:19829
XDG_DATA_DIRS=/home/user/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
PATH=/home/user/Bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/sbin/:/usr/sbin/:/home/user/.rvm/bin
GDMSESSION=gnome
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MAIL=/var/spool/mail/user
OLDPWD=/home/user
TERM_PROGRAM=kgx
_=/usr/bin/printenv

I am not aware of anything dbus-launch. Like I said, it's a pretty fresh install. At least I did not manually configure anything with dbus-launch.

I've copied several config files from my backup, but that's more app specific (Firefox, Vim, SSH, etc.).

$ systemctl --user status dbus.service
[sudo] password for user: 
Failed to connect to bus: No medium found

Ouch.

$ systemctl status dbus.service
● dbus-broker.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus-broker.service; disabled; preset: disabled)
     Active: active (running) since Mon 2024-04-22 18:22:04 CEST; 2h 24min ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-broker-launch(1)
   Main PID: 1561 (dbus-broker-lau)
      Tasks: 2 (limit: 38136)
     Memory: 4.8M (peak: 5.6M)
        CPU: 396ms
     CGroup: /system.slice/dbus-broker.service
             ├─1561 /usr/bin/dbus-broker-launch --scope system --audit
             └─1562 dbus-broker --log 4 --controller 9 --machine-id 27ab6d9364bf4647a0f324ae4ca13edb --max-bytes 536870912 --max-fds 4096 --max-matches 131072 --audit

Apr 22 18:22:04 host systemd[1]: Starting D-Bus System Message Bus...
Apr 22 18:22:04 host systemd[1]: Started D-Bus System Message Bus.
Apr 22 18:22:04 host dbus-broker-launch[1561]: Ready
Apr 22 18:22:04 host dbus-broker-launch[1561]: Activation request for 'org.freedesktop.home1' failed: The systemd unit 'dbus-org.freedesktop.home1.service' could not be found.
Apr 22 18:22:04 host dbus-broker-launch[1561]: Activation request for 'org.freedesktop.Avahi' failed: The systemd unit 'dbus-org.freedesktop.Avahi.service' could not be found.
Apr 22 18:22:08 host dbus-broker-launch[1561]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.

Last edited by Rec100 (2024-04-22 18:48:35)