Hi ! HP Victus, Manjaro XFCE, I have a Iiyama secondary screen linked by Hdmi, how to use its speakers rather than the victus ones ?
➜ ~ inxi -A | grep -A5 "Audio"
Audio:
Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel
Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel
Device-3: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: snd_rn_pci_acp3x
Device-4: AMD Family 17h/19h HD Audio driver: snd_hda_intel
API: ALSA v: k6.7.7-1-MANJARO status: kernel-api
Server-1: PipeWire v: 1.0.3 status: active (process)
➜ ~
Check Configuration tab in PulseAudio Volume Control audio mixer:
pavucontrol --tab=5
Profile for 1st device is probably set to Off Digital Stereo Output that shows connection to monitor
If audio playback to monitor is still not working as expected, check the HDMI output is not muted in ALSA
alsamixer -c0
1 Like
Hi, thank you for caring.
➜ ~ systemctl --user status pipewire-pulse.socket pipewire-pulse.service
● pipewire-pulse.socket - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.socket; enabled; preset: enabled)
Active: active (running) since Sat 2024-03-30 07:57:14 CET; 8h ago
Triggers: ● pipewire-pulse.service
Listen: /run/user/1000/pulse/native (Stream)
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/pipewire-pulse.socket
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: enabled)
Active: active (running) since Sat 2024-03-30 07:57:14 CET; 8h ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 2050 (pipewire-pulse)
Tasks: 3 (limit: 18339)
Memory: 29.7M (peak: 30.2M swap: 1.1M swap peak: 1.2M zswap: 217.3K)
CPU: 1.866s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─2050 /usr/bin/pipewire-pulse
➜ ~ pavucontrol
➜ ~ pavucontrol --tab=5
and with alsamixer as well I suppose
for ALSA, use M key to unmute the S/PDIF output [OO]
For pipewire-pulse & pavucontrol I suggest reboot systempavucontrol is still unable to connect to pipewire-pulse , please post more information about audio devices detected in pipewire-pulse
pactl list cards
Ok, I didn’t grasp the alsamixer interface
Why restart ? pavucontrol & pipewire-pulse are installed for months
➜ ~ alsamixer -c0
➜ ~ pactl list cards
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
➜ ~ sudo pactl list cards
[sudo] password for sum:
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
➜ ~
[Edit] Is this normal ?
➜ ~ sudo find / -name pipewire-pulse.conf
/usr/share/pipewire/pipewire-pulse.conf
find: ‘/tmp/.mount_ButterKQeolc’: Permission denied
find: ‘/tmp/.mount_ButterNauECf’: Permission denied
/var/lib/flatpak/runtime/org.freedesktop.Sdk/x86_64/22.08/37618b0f49934fa47c1efb5f3c3e1d9ad50731c0144d4123996ac9db87287f40/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.freedesktop.Sdk/x86_64/23.08/3518892d2bda87abb977abf8b452d5c4400979056e02948617e9c0b9de04ebb9/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.freedesktop.Sdk/x86_64/21.08/6d6d5cb020cefade8c46a53b005d917658945160c0bb6dcc6bad9b4cca36fa4a/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/44/31ef2cbe419c6d091616be29f7384b9f4601901643d9f8fc74c6d12f509af80b/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/42/982438648e909ca4648ef41959440312b25bc1392bec2a7629d6b69824cf535e/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/46/9a6b5e332285a0b9b455a9f3c1589ee85ef2b25ac0f2fa7b63ac90c679ae4756/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/43/72c5f3d0de590e85995322e18b56731a4b7ed8b47d5fba615dae7ca5c6741930/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.gnome.Platform/x86_64/45/e66d066758b2a7b50a1cac032041fc1569c428f7cff988dcba554b3c035a191d/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/22.08/f1b697054c6ad75a09adfad28193a68fcdba6a3791a41aaac121d8f57012ea7f/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/23.08/232eeb0ac8c31b9768099c037e90fdfb96423bdd16d6d80e07628824ef2ed0b1/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.freedesktop.Platform/x86_64/21.08/8745946eed14ab6da3e21a642a467c994fe0f2bea1ad27a933464dca63ceabe4/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.kde.Platform/x86_64/6.5/d59237689cd510428d159691b9d72cb7d37871fe17eded9f3d048648ed694930/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.kde.Platform/x86_64/6.6/d9a07ad16df6b5858f924014ae6bc0803035276bd317da79e4a36bae2f68790b/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.kde.Platform/x86_64/5.15-23.08/4303bde2170527fa3720b9d77075ff6d1bb3895be3269a1760f86a301fb21211/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/runtime/org.kde.Platform/x86_64/5.15-22.08/662497f7f7e1b03c6b40affb3473c8412d703241770f04f8d6af68b8535ddc5a/files/share/pipewire/pipewire-pulse.conf
/var/lib/flatpak/app/sa.sy.bluerecorder/x86_64/stable/911033f5af5d53db423517659099ef0d4bef44788f51eb7886d56592fba45602/files/share/pipewire/pipewire-pulse.conf
find: ‘/run/user/1000/gvfs’: Permission denied
find: ‘/run/user/1000/doc’: Permission denied
find: ‘/proc/125809/task/125809/net’: Invalid argument
find: ‘/proc/125809/net’: Invalid argument
find: ‘/proc/151015’: No such file or directory
➜ ~ ls /etc/pipewire/
client.conf.d client-rt.conf.d jack.conf.d minimal.conf.d pipewire.conf.d pipewire-pulse.conf.d
➜ ~ ls /etc/pipewire/pipewire.conf.d
➜ ~ ls -lR /etc/pipewire/
/etc/pipewire/:
total 24
drwxr-xr-x 2 root root 4096 Feb 19 2022 client.conf.d
drwxr-xr-x 2 root root 4096 Feb 19 2022 client-rt.conf.d
drwxr-xr-x 2 root root 4096 Feb 19 2022 jack.conf.d
drwxr-xr-x 2 root root 4096 Feb 19 2022 minimal.conf.d
drwxr-xr-x 2 root root 4096 Feb 19 2022 pipewire.conf.d
drwxr-xr-x 2 root root 4096 Oct 8 2022 pipewire-pulse.conf.d
/etc/pipewire/client.conf.d:
total 0
/etc/pipewire/client-rt.conf.d:
total 0
/etc/pipewire/jack.conf.d:
total 0
/etc/pipewire/minimal.conf.d:
total 0
/etc/pipewire/pipewire.conf.d:
total 0
/etc/pipewire/pipewire-pulse.conf.d:
total 0
➜ ~
Restarting system is simpler than restarting multiple unknown pipewire/wireplumber servicessystemctl --user list-unit-files | grep wiresystemctl --user status to check sockets and services for errors before restarting
Error response from sudo pactl list cards is expected - PipeWire is usually configured to allow one user account only to access audiosudo is not used
Try using pipewire command
pw-cli info all
Well, something seems wrong there !
➜ ~ systemctl --user list-unit-files | grep wire
pipewire-pulse.service disabled enabled
pipewire-session-manager.service alias -
pipewire.service disabled enabled
wireplumber.service enabled enabled
wireplumber@.service disabled enabled
pipewire-pulse.socket enabled enabled
pipewire.socket enabled enabled
➜ ~ systemctl --user status
● Error404
State: running
Units: 276 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Wed 2024-04-03 08:01:35 CEST; 11h ago
systemd: 255.4-1-manjaro
CGroup: /user.slice/user-1000.slice/user@1000.service
├─app.slice
│ ├─app-dbus\x2d:1.11\x2dorg.a11y.atspi.Registry.slice
│ │ └─dbus-:1.11-org.a11y.atspi.Registry@0.service
│ │ └─1978 /usr/lib/at-spi2-registryd --use-gnome-session
│ ├─app-dbus\x2d:1.2\x2dorg.fedoraproject.Config.Printing.slice
│ │ └─dbus-:1.2-org.fedoraproject.Config.Printing@0.service
│ │ └─117138 /usr/bin/python3 /usr/share/system-config-printer/scp>
│ ├─app-dbus\x2d:1.2\x2dorg.flameshot.Flameshot.slice
│ │ └─dbus-:1.2-org.flameshot.Flameshot@0.service
│ │ └─13658 /usr/bin/flameshot
│ ├─app-dbus\x2d:1.2\x2dorg.gnome.Identity.slice
│ │ └─dbus-:1.2-org.gnome.Identity@0.service
│ │ └─2467 /usr/lib/goa-identity-service
│ ├─app-dbus\x2d:1.2\x2dorg.gnome.OnlineAccounts.slice
│ │ └─dbus-:1.2-org.gnome.OnlineAccounts@0.service
lines 1-23...skipping...
● Error404
State: running
Units: 276 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Wed 2024-04-03 08:01:35 CEST; 11h ago
systemd: 255.4-1-manjaro
CGroup: /user.slice/user-1000.slice/user@1000.service
├─app.slice
│ ├─app-dbus\x2d:1.11\x2dorg.a11y.atspi.Registry.slice
│ │ └─dbus-:1.11-org.a11y.atspi.Registry@0.service
│ │ └─1978 /usr/lib/at-spi2-registryd --use-gnome-session
│ ├─app-dbus\x2d:1.2\x2dorg.fedoraproject.Config.Printing.slice
│ │ └─dbus-:1.2-org.fedoraproject.Config.Printing@0.service
│ │ └─117138 /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py
│ ├─app-dbus\x2d:1.2\x2dorg.flameshot.Flameshot.slice
│ │ └─dbus-:1.2-org.flameshot.Flameshot@0.service
│ │ └─13658 /usr/bin/flameshot
│ ├─app-dbus\x2d:1.2\x2dorg.gnome.Identity.slice
│ │ └─dbus-:1.2-org.gnome.Identity@0.service
│ │ └─2467 /usr/lib/goa-identity-service
│ ├─app-dbus\x2d:1.2\x2dorg.gnome.OnlineAccounts.slice
│ │ └─dbus-:1.2-org.gnome.OnlineAccounts@0.service
│ │ └─2419 /usr/lib/goa-daemon
│ ├─app-dbus\x2d:1.2\x2dorg.xfce.Xfconf.slice
│ │ └─dbus-:1.2-org.xfce.Xfconf@60.service
│ │ └─181023 /usr/lib/xfce4/xfconf/xfconfd
│ ├─app-flatpak-com.slack.Slack-11475.scope
│ │ ├─11475 bwrap --args 41 com.slack.Slack
│ │ ├─11487 bwrap --args 41 xdg-dbus-proxy --args=43
│ │ ├─11488 xdg-dbus-proxy --args=43
│ │ ├─11494 bwrap --args 41 com.slack.Slack
│ │ ├─11495 /bin/bash /app/bin/com.slack.Slack
│ │ ├─11497 "/app/extra/slack -s --enable-features=WebRTCPipeWireCapturer"
│ │ ├─11509 "/app/extra/slack --type=zygote --no-zygote-sandbox"
│ │ ├─11513 cat
│ │ ├─11514 cat
│ │ ├─11551 /app/extra/chrome_crashpad_handler --monitor-self-annotation=ptype=crashpad-handler --no-upload-gzip --database=/home/sum/.var/app/com.slack.Slack/config/Slack/Crashpad "--url=https://s>
│ │ ├─11562 "/app/extra/slack --type=gpu-process --enable-logging --crashpad-handler-pid=41 --enable-crash-reporter=54293575-623b-4ed9-bf04-138c6c3f44b7,no_channel --user-data-dir=/home/sum/.var/ap>
│ │ ├─11569 "/app/extra/slack --type=utility --utility-sub-type=network.mojom.NetworkService --lang=fr --service-sandbox-type=none --enable-logging --crashpad-handler-pid=41 --enable-crash-reporter>
│ │ └─11687 "/app/extra/slack --type=utility --utility-sub-type=audio.mojom.AudioService --lang=fr --service-sandbox-type=none --enable-logging --crashpad-handler-pid=41 --enable-crash-reporter=542>
│ ├─app-flatpak-com.slack.Slack-11515.scope
│ │ ├─11515 bwrap --args 41 /app/bin/zypak-helper child - /app/extra/slack --type=zygote
│ │ ├─11524 bwrap --args 41 /app/bin/zypak-helper child - /app/extra/slack --type=zygote
│ │ ├─11525 "/app/extra/slack --type=zygote"
│ │ └─11602 "/app/extra/slack --type=renderer --crashpad-handler-pid=41 --enable-crash-reporter=54293575-623b-4ed9-bf04-138c6c3f44b7,no_channel --user-data-dir=/home/sum/.var/app/com.slack.Slack/co>
│ ├─appimagelauncherd.service
│ │ └─1902 /usr/bin/appimagelauncherd
│ ├─bamfdaemon.service
│ │ └─2311 /usr/lib/bamf/bamfdaemon
│ ├─dconf.service
│ │ └─2576 /usr/lib/dconf-service
│ ├─evolution-addressbook-factory.service
│ │ └─2498 /usr/lib/evolution-addressbook-factory
│ ├─evolution-calendar-factory.service
│ │ └─2459 /usr/lib/evolution-calendar-factory
│ ├─evolution-source-registry.service
│ │ └─2389 /usr/lib/evolution-source-registry
│ ├─flatpak-portal.service
│ │ └─11502 /usr/lib/flatpak-portal
│ ├─flatpak-session-helper.service
│ │ ├─11479 /usr/lib/flatpak-session-helper
│ │ ├─11484 server --sh -n /run/user/1000/.flatpak-helper/pkcs11-flatpak-11479 --provider p11-kit-trust.so "pkcs11:model=p11-kit-trust?write-protected=yes"
│ │ └─11599 p11-kit-remote --provider p11-kit-trust.so "pkcs11:model=p11-kit-trust?write-protected=yes"
│ ├─gnome-keyring-daemon.service
│ │ └─1906 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
│ ├─gpg-agent.service
│ │ └─1992 /usr/bin/gpg-agent --supervised
│ ├─xdg-desktop-portal-gtk.service
│ │ └─2303 /usr/lib/xdg-desktop-portal-gtk
│ └─xfce4-notifyd.service
│ └─2101 /usr/lib/xfce4/notifyd/xfce4-notifyd
├─init.scope
│ ├─1882 /usr/lib/systemd/systemd --user
│ └─1884 "(sd-pam)"
└─session.slice
├─at-spi-dbus-bus.service
│ ├─1965 /usr/lib/at-spi-bus-launcher
│ ├─1970 /usr/bin/dbus-broker-launch --config-file=/usr/share/defaults/at-spi2/accessibility.conf --scope user
│ └─1971 dbus-broker --log 4 --controller 9 --machine-id 866a42a3b558486baf84e7cf0ebd4270 --max-bytes 100000000000000 --max-fds 6400000 --max-matches 5000000000
├─dbus-broker.service
│ ├─1913 /usr/bin/dbus-broker-launch --scope user
│ └─1914 dbus-broker --log 4 --controller 10 --machine-id 866a42a3b558486baf84e7cf0ebd4270 --max-bytes 100000000000000 --max-fds 25000000000000 --max-matches 5000000000
├─gvfs-afc-volume-monitor.service
│ └─2566 /usr/lib/gvfs-afc-volume-monitor
├─gvfs-daemon.service
│ ├─ 1949 /usr/lib/gvfsd
│ ├─ 1955 /usr/lib/gvfsd-fuse /run/user/1000/gvfs -f
│ ├─ 2644 /usr/lib/gvfsd-trash --spawner :1.7 /org/gtk/gvfs/exec_spaw/0
│ ├─ 10304 /usr/lib/gvfsd-http --spawner :1.7 /org/gtk/gvfs/exec_spaw/1
│ ├─118689 /usr/lib/gvfsd-network --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
│ └─118764 /usr/lib/gvfsd-dnssd --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
├─gvfs-gphoto2-volume-monitor.service
│ └─2589 /usr/lib/gvfs-gphoto2-volume-monitor
├─gvfs-metadata.service
│ └─2661 /usr/lib/gvfsd-metadata
├─gvfs-mtp-volume-monitor.service
│ └─2595 /usr/lib/gvfs-mtp-volume-monitor
├─gvfs-udisks2-volume-monitor.service
│ └─2301 /usr/lib/gvfs-udisks2-volume-monitor
├─pipewire-pulse.service
│ └─2015 /usr/bin/pipewire-pulse
├─pipewire.service
│ └─2013 /usr/bin/pipewire
├─wireplumber.service
│ └─2014 /usr/bin/wireplumber
├─xdg-desktop-portal.service
│ └─2227 /usr/lib/xdg-desktop-portal
├─xdg-document-portal.service
│ ├─2267 /usr/lib/xdg-document-portal
│ └─2279 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc
├─xdg-permission-store.service
│ └─2121 /usr/lib/xdg-permission-store
├─zeitgeist-fts.service
│ └─2244 /usr/lib/zeitgeist/zeitgeist-fts
└─zeitgeist.service
└─2207 /usr/bin/zeitgeist-daemon
➜ ~ pw-cli info all
Error: "failed to connect: Host is down"
➜ ~
Services are up and host is down (I have no idea of which host )
pw-cli response is similar to responses from PulseAudio tools
PipeWire Wiki - Troubleshooting - PipeWire Not Loading
PipeWire and Wireplumber have three main directories where its files are stored /usr/share/pipewire and /usr/share/wireplumber. It is recommended if you would like to make configuration changes that you copy them from /usr to the corresponding directories in /etc or your ~/.config folder.
The third directory is ~/.local/state/wireplumber which contains four filesdefault-nodes, default-profile, default-routes, and restore-stream.
Make sure your systemd services and sockets are enabled and started (as --user) this includes pipewire.service, pipewire.socket, pipewire-pulse.service, pipewire-pulse.socket and wireplumber.service.
Well, thank you for caring, you helped me reinvestigate.
1 Like
system
17 April 2024 02:48
10
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.
