Arch Linux

evilch3n

Member

Registered: 2020-04-12

Posts: 15

[Solved] No sound until source is toggled after each start

I searched 40 minutes on the forum to find a similiar issue but coulnd't find any, dont know if newbie corner or kernel/hardware would be the right board - if its wrong please move the thread

The Problem:

No sound works until i toggle the source in the gnome settings menu, it does not matter if i toggle from analog to analog or from analog to digital or vice versa. After a toggle or just even opening the source drop down the sound works.

If i dont toggle that no youtube video will play, no game would start nor teamspeak would launch

Iam using:
- Kernel: 6.5.8
- used pipewire but it crashed often so i installed pulseaudio
- usb headset JBL Quantum 350

Things i tried sofar (nothing worked):
- alsamixer -c 0 sset "Auto-Mute Mode" Disabled --> "mixer: Unable to find simple control 'Auto-Mute Mode',0" seems like i dont have this option?
- sudo tee /etc/modprobe.d/snd-hda-intel.conf <<< "options snd_hda_intel power_save=0" --> to try if powersaving was interfering
- systemctl --user enable pulseaudio ---> thought maybe pulseaudio does not start or wasn't enabled
- added pulseaudio -k to my .profile hoped a restart on login would help
- put the USB-dongle from front to a blue-slot (3.0) in the back
- added load-module module-switch-on-connect to /etc/pulse/default.pa (pulling the dongle and plugin it back in also fixes the problem)

Outputs and other info:

pactl list short sinks

0 alsa_output.pci-0000_2d_00.1.hdmi-stereo module-alsa-card.c s16le 2ch 44100Hz SUSPENDED
3 alsa_output.usb-JBL_JBL_Quantum350_Wireless-00.iec958-stereo module-alsa-card.c s16le 2ch 48000Hz RUNNING

systemctl --user status pulseaudio

● pulseaudio.service - Sound Service
Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; preset: enabled)
Active: active (running) since Tue 2023-10-24 16:57:16 CEST; 5min ago
TriggeredBy: ● pulseaudio.socket
Main PID: 1391 (pulseaudio)
Tasks: 9 (limit: 38392)
Memory: 20.4M
CPU: 2.869s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pulseaudio.service
├─1391 /usr/bin/pulseaudio --daemonize=no --log-target=journal
└─1532 /usr/lib/pulse/gsettings-helper

Okt 24 16:57:15 speed systemd[771]: Starting Sound Service...
Okt 24 16:57:16 speed pulseaudio[1391]: stat('/etc/pulse/default.pa.d'): Datei oder Verzeichnis nicht gefunden
Okt 24 16:57:16 speed systemd[771]: Started Sound Service.
Okt 24 16:57:16 speed pulseaudio[1391]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.

Last edited by evilch3n (2023-10-24 20:19:56)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,234

Re: [Solved] No sound until source is toggled after each start

If you switched to pulseaudio you'll want to install pipewire-media-session and remove pipewire-audio and dependants. Otherwise you will always have a logical conflict with wireplumber and pulseaudio

evilch3n

Member

Registered: 2020-04-12

Posts: 15

Re: [Solved] No sound until source is toggled after each start

install pipewire-media-session even tho its called pipewire? ok will try didnt think of that because of the naming

edit: you are the MVP - the naming wasnt intuitive for me but this did the trick! marking as solved (god damn i spent hours to find a workaround for this)

Last edited by evilch3n (2023-10-24 20:19:39)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,234

Re: [Solved] No sound until source is toggled after each start

The logical correlation of things is that you won't be able to completely rid yourself of pipewire, because before it was an audio server it's main purpose was to be a secure screen sharing utility that allowed wayland clients to grab authenticated screen grabs correctly. So all of the things that want to provide screen sharing on wayland will hard depend on at least the pipewire video part of the equation. so you need to have something that still fulfills that contract, while not having audio handled by it. AFAIK you can actually configure wireplumber to leave audio alone by now, but the "canonical" way of doing is to simply use pipewire-media-session instead. While it will likely get phased out at some point, hopefully wireplumber is easier to disable the audio integration or whatever bugs you're facing currently having been fixed within pipewire.

Last edited by V1del (2023-10-24 21:57:59)