.pulse causes no sound (was ... Re: wheezy Audio Works for Root, Dies for User and it's not Perms.)
On Tue, May 15, 2012 at 09:32:09PM -0500, Martin McCormick wrote:
> After purging and restoring pulseaudio and all the
> applications that needed it, I started looking at .pulse in my
> home directory as I didn't put it there to begin with. I
Creating another user would have produced the same result.
> expected to find it empty and there was the cause of all the
> trouble. A listing of that directory is:
>
> 43ec7b6e5a01418f517b363500001654-card-database.tdb
> 43ec7b6e5a01418f517b363500001654-default-sink
> 43ec7b6e5a01418f517b363500001654-default-source
> 43ec7b6e5a01418f517b363500001654-device-volumes.tdb
> 43ec7b6e5a01418f517b363500001654-runtime
> 43ec7b6e5a01418f517b363500001654-stream-volumes.tdb
>
> When all files are present, the trouble happens. If I
> remove them, it works. Pulseaudio soon rebuilds all of them and
> the trouble returns. I have quickly read the man page for
> pulseaudio and for the pulse-daemon.conf file and there is not a
> word about these files and how to manage them but I think that
> pulseaudio is confused about this sound card and is putting the
> wrong tdb file in place.
Good deduction Watson!, but can you prove it? :)
Can you live without pulse?
You could do as Cameleon suggested, and look in that alsa-pulse.conf
file, but I'm guessing it is generated on package install AND/OR is used to
help generate the .pulse files in your home directory.
File a bug with reportbug and attach the faulty alsa-pulse.conf file.
--
"Religion is excellent stuff for keeping common people quiet."
-- Napoleon Bonaparte
Reply to: