Re: PulseAudio (Some users get sound, orthers do not)
On 2017-07-09, Marc Shapiro <marcnshap@gmail.com> wrote:
> At some point in the past I was having sound issues which I traced to
> pulseaudio. I uninstalled pulseaudio and everything was fine. Then
> Firefox decided to require pulseaudio and my sound (in Firefox) went away.
>
> I reinstalled pulseaudio and eventually got it working (I thought).
> Well, it was working for me, but not for my wife and daughter,
> apparently. Both of them have recently let me know that they have been
> without sound for an indeterminate period of time.
>
> This morning, I went to my wife's login and ran:
>
> pulseaudio --kill
>
> rm ~/.config/pulse
>
> pulseaudio --start
>
> And that worked. There were some warnings about not being able to find
> the cookie file, which was understandable since I had just rm'd the
> configuration directory. But pulseaudio recreated the directory and
> needed files and seems to be happy. At least I am able to get sound
> from the command line, as well as from Firefox.
>
>
> When I tried to do the same thing under my daughter's login, however, I
> get the warnings about the cookie file and ~/.config/pulse is NOT
> recreated, so still no sound anywhere. I have checked the permissions
> of my daughter's ~/.config/pulse directory and it is 644 with her user
> as owner and group. That matches ~/.config in my home directory and my
> wife's.
>
The wiki suggests (for missing playback devices):
$ rm -r ~/.config/pulse /tmp/pulse-*
$ pulseaudio --kill
$ pulseaudio --start
https://wiki.debian.org/PulseAudio
I suppose you've verified in a mixer program and/or pavucontrol that all
is as should be.
> So why does pulseaudio not create the files it needs, like it did for me
> and my wife? Is there something else that I am missing? Any help will
> be appreciated.
I don't have a ~/.config/pulse/ directory myself; I suppose in my case
pulse gets its config from /etc/pulse.
BTW, as it would appear that ~/.config/pulse/ is a directory and
not a file (unless I'm wrong in which case I'm wrong) I don't see how your
'rm ~/.config/pulse' command worked. But I guess I'm wrong because
certainly you would have noticed "rm: cannot remove 'pulse/': Is a
directory".
Or maybe during the redaction of your post you left out the '-r' flag by
inadvertence.
> Marc
>
>
--
“Yeah yeah.” --Sidney Morgenbesser's retort to a speaker who said that although
there are many cases in which two negatives make a positive, he knew of no case
in which two positives made a negative.
Reply to: