Maverick Thinkpad T61, Intel GMA X3100, Intel WiFi 4965AG.
cheers u get me the way to go
thanks a lot!!!
Thanks all ...
Helped me fix the thing that was bugging me the whole day .
I don't have a hidden .pulse folder in my Home directory. Sound works, but I have no sound icon in the panel. YES, I have the Indicator Applet attached to the panel and I see the envelope icon, but no sound icon.
I tried uninstalling and reinstalling pulseaudio but that didn't help the situation.
Deleted the .pulse folder and the problem was fixed on re-boot.
I am in Ubuntu 10.10. Today a I did an Update, which included a kernel update. So I had to reboot to complete the update. Since then no sound. Why did I have to update? It worked flawlessly before. I followed all the instructions in this thread. The first time I deleted .pulse from my home directory and rebooted, the sound came back. I was happy. Then the sound did not work in SKYPE. I deleted and reinstalled SKYPE through Synaptic. Then the sound was even gone on the desktop and the little speaker Icon shows no status and when I click on the Sound Preferences I get "Waiting for sound system to respond." Now every time I delete .pulse and reboot, the sound does not come back and I always get this message. Is the .pulse folder suppose to be forever deleted, or by deleting it, it just restores a new copy hopefully with the correct settings? I have gone back to my former kernel in GRUB and still no sound. Its clobbered. Any help please?
None of your tips worked for me.
Deleting .pulse did not do anything at all.
I still have an icon with a speaker, and when I click on the "Sound Preferences..." there is an "Waiting for sound system to respond" message window appearing.
I do have a sound, but I can't do any sound preferences...
Thanks for your help!
Deleted the .pulse directory and the Sound Preferences opened up immediately - no restart necessary. Cool!
i'm having the same problem "waiting for sound system to respond" and deleting the .pulse folder doesn't work.
but i still have sound..
does anyone have a fix yet?