Help with creation, editing, or playback of sounds, images, or video. Amarok, audacious, mplayer, grip, cdparanoia and anything else that makes a sound or plays a video.
I did an upgrade of the system lately and on the way I recognized an update to some files in /etc/pulse during an etc-update run. As I did not edit something in these files I let it update them. After next login, pulseaudio stopped working.
In the meantime I found out that pulseaudio cannot connect to sound card device at startup and uses a dummy device instead. When I use fuser /dev/snd/* or lsof /dev/snd/* I see nothing is using the sound devices. At least not after the XFCE Desktop is started. But it worked till that update tp pulseaudio-0.9.19. I already tried upgrading to pulseaudio-0.9.21-r50 with no changes. Also with both versions I tried starting pulseaudio newly after making sure nothing is using the sound devices.
All the documentation I found ends at this point. Is there something I can try/read into that I have missed?
I hope someone can help me with this,
fangorn
Edit:
I also tried changing back to pure alsa, but did not hear anything.
I removed ~/.asoundrc and replaced it with a standard config (pure and dmix) and killed pulseaudio startup. I also reconfigured the playing apps to explicitely use the alsa output. Any hints on how to cleanly go back?
Last edited by fangorn on Tue Jan 12, 2010 6:45 pm, edited 1 time in total.
In the meantime I gave up on pulseaudio, went back to my good old FVWM config, switched to alsa-driver-1.0.22.1 to get vlc from git working with alsa again and now I have audio again.
tell you anything?
Of course you'd need to kill any process holding the audiodev (another pulseaudio instance, for instance) first.
Another thing that might help is to remove /var/lib/pulse/* (not while pulseaudio is running, of course).
Ah, so that was the cause of my own mysterious pulseaudio problem. Thanks for clearing that up VoidMage.
So let me rephrase that:
If you upgraded gdbm you may need to force pulseaudio to recreate its databases (by weeding through /var/lib/pulse and/or ~/.pulse/) .
That seems to have helped. A device is detected again. I did not have the time to test functionality yet though. Will report back when I have tested it.