PulseAudio

[Eric Battersby]

I disabled PulseAudio, in Fedora and never looked back.
It would stop working after a few minutes.
Here is one log message:
   cpulimit.c: Received request to terminate due to CPU overload
I am only using ALSA now.

To remove it, I ran this (from some linux page):
         rpm -e pulseaudio pulseaudio-module-x11
 	pulseaudio-module-zeroconf pulsaudio-esound-compat
 	pulseaudio-module-lirc pulseaudio-module-jack
 	pulseaudio-module-gconf paprefs pavucontrol pavumeter
 	paman pulseaudio-module-bluetooth
 	kde-settings-pulseaudio fluxbox-pulseaudio
 	alsa-plugins-pulseaudio
- that seemed to work
- why didn't I do a yum erase?
   - don't know now, but you want to be careful not to remove
     too many dependencies
- my volume control disappeared; I use alsamixer for that


On Thu, 18 Feb 2010, Tyler Aviss wrote:

> Heck no. If it worked with ALSA before, it should work after.
>
> A couple other things to check
>  /etc/modprobe.d entries for ALSA (you might want to remove old
> entries, purge the main ALSA packages, reinstall)
>  try sound from commandline before logging in, so that you're just on
> ALSA without Pulse possibly stealing the device
>
> Some useful commands:
>  aplay -l : lists soundcards that ALSA knows
>  alsamixer : commandline mixer useful for configuring prior to
> getting into gnome/pulse. Use "m" for mute/unmute and arrows for
> volume, tab for navigation
>  aplay /usr/share/sounds/alsa/Front_Center.wav  : test sound (alsa)
>
> On Wed, Feb 17, 2010 at 8:51 AM, Thomas Milne
> <tbrucemilne-TcoXwbchSccMMYnvST3LeUB+6BGkLq7r at public.gmane.org> wrote:
>> I'm waiting for a reply back from work with some more info/command
>> output from dmesg and lspci and so on. I'll get them to also check if
>> pulse is even running, didn't think of that.
>>
>> So you've never had to go the OSS route?
>>
>> On Wed, Feb 17, 2010 at 11:44 AM, Tyler Aviss <tjaviss-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:
>>> I found a couple things when updating to karmic on various machines
>>> that could case this:
>>>  - Gnome/pulse found a different "default" soundcard than what they should have
>>>  - PA set the volume to nothing in the sound panel mixer, or turned on mute
>>>  - Wrong "profile" in the hardware settings of the sound prefs
>>>
>>> If you have a .asoundrc file in your homedir you may need to nuke that too
>>>
>>> Are you seeing your soundcard? Is the pulseaudio daemon loading?
>>>
>>> On Wed, Feb 17, 2010 at 8:23 AM, Thomas Milne
>>> <tbrucemilne-TcoXwbchSccMMYnvST3LeUB+6BGkLq7r at public.gmane.org> wrote:
>>>> Ha! So it finally got to me. So far on my home machine it's been no
>>>> problem, so I've been wondering why everyone hates Pulse so much.
>>>>
>>>> Until now. At work we upgraded all the machines to Karmic Koala and
>>>> now a lot of them have no sound. If you saw how we do our jobs, you
>>>> would understand what a horrifying thing this is ;)
>>>>
>>>> Anyhow, I remember some threads on here a while ago about fixing this
>>>> by using good 'ol OSS, but as these are work computers I thought I
>>>> would ask before I start trying some of the solutions. Is this really
>>>> the tried and true method?
>>>>
>>>> I also found this link. Anyone else solve it like this?
>>>>
>>>> http://swiss.ubuntuforums.org/showthread.php?t=1395089
>>>>
>>>> Thanks!
>>>>
>>>> --
>>>> TBM
>>>> --
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists