No pulseaudio daemon running12/31/2022 This is what I used to have in my config file, in order to prevent the computer from trying to output sound through HDMI connections. Now, if you also must fix the issue that pulseaudio at startup always directs sound to the wrong device, then you can configure your ~/.config/pulse/default.pa to hardcode the default output device with statements such as set-card-profile 0 output:analog-stereo Thanks to Jim Carter for pointing me in the right direction. If you now see lots of lines scroll by, more specifically statements of modules loaded, then you know that you have solved the original issue.īecause this is hard to track down, especially if you are forgetful (like me), or because you got convinced by one of the many web pages dealing with pulseaudio issues that you should have a default.pa in the first place, there's already a launchpad bug filed against the behaviour that a user specific default.pa replaces the system wide default.pa. For example with opening a terminal, then typing mv. If yes, try to move it to a backup location, and then restart pulseaudio. In other words: If you get the error message main.c: Daemon startup without any loaded modules, refusing to work.Ĭheck if you intentionally or accidentally have a file at. If you don't want to type as much every time you are going to use the remote pulseaudio, you can add this to your ~/.For those who come here at this time or later, especially if you have never messed with the system wide default in /etc/pulse/default.pa, do note that if you have a ~/.config/pulse/default.pa it completely replaces the system wide default. Note that with this solution you won't see a second audio-output-device in pulseaudio-tools like padevchooser, so you can't move To actually stream sound over the network open a terminal and typeĪny pulseaudio application started from that same terminal will automatically stream its sound over the network. Option -N let's ssh know that we don't want the shell to run any programs, since forwarding a port is all we want to do.Įnter your root password and the port should be forwarded. Ssh -f -N -L4000:localhost: 4000 root -f puts the ssh session the background, because we don't need to actively work with the session anyways. In this example we've decided to use port 4000. The first step is to forward a tcp port to the router using ssh. Pulseaudio should now be running after reboot. Udevd -daemon chmod 0777 /dev /snd /* mkdir -p /var /lib /pulse You can put all of these commands in a script: You have to keep this running to keep the connection going. Socat TCP-LISTEN: 4000,fork UNIX-CONNECT: /tmp /run /pulse /native & Now run socat to listen on the port that will be forwarded to the router and let it redirect to the native Unix socket that pulseaudio is using on the router: It will complain that pulseaudio shouldn't be run in system mode, but on many routers this is the only mode that will actually work. Pulseaudio -system -disallow-module-loading -disallow-exit -no-cpu-limit & Pulseaudio also likes to complain that /var/lib/pulse is missing, so we create it: If you still have problems, you can also try: Install the udev package, if you run into problems with pulseaudio. Sometimes it helps to start udevd before pulseaudio to avoid problems. The module will already be in system.pa by default, just make sure that the auth-anonymous=1 option is given, to avoid an access denied error, when you later try to stream sound. Load-module module-native-protocol-unix auth-anonymous= 1 For sound from the network, something like this is needed:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |