My audio suddenly stopped working in Ubuntu 14.04 whilst I was playing something off Youtube. I restarted and purged pulseaudio and alsa, reinstalled both and pulseaudio-equaliser as well (which I have been using successfuly in 14.04 since the beginning).
The error output when trying to initialize pulseaudio is:
I have checked another thread with a similar question however the solution seemed to work for an older version of Ubuntu. I have tried that here as well with no luck. (Trying to remove the pulseaudio config files from /usr/etc/pulseaudio) Note: I have found no .pulse folder in my home directory to purge.
How To Choose A Farmhouse Sink. I’ve been pinning farmhouse (or apron) sinks onto my Kitchen Pinterest board for years now. It was something I knew I wanted to splurge on in our new home, and thankfully my husband agreed with me.
Thanks for any help in Advance.
SmodSmod
3 Answers
For anybody that comes here in the future, there's a much easier solution to this problem as found here. It worked like a charm for me.
You will see a bunch of errors about files in
~/.config/pulse/
not existing which you can ignore when you start pulseaudio. The presets
folder will only exist if you have pulseaudio-equalizer installed (and maybe only if you've already set presets). It just stores your presets so it's not a huge deal either way, but it's nice to copy if you've already put work into your custom presets and want to keep them.Justin WarkentinJustin Warkentin
Problem has been solved.
The location of the configuration file (which is altered by
pulseaudio-equalizer
) in Ubuntu 14.04 is ~/.config/pulse
. After deleting this folder, I followed the following steps.- I removed any traces of pulseaudio and pulseaudio-equalizer
- I physically removed any folders viz.
/etc/pulse
/usr/share/pulseaudio
usr/share/pulseaudio-equalizer
- I performed a reboot
- I reinstalled pulseaudio and pulseaudio-equalizer (the equalizer install is optional!)
- Note at this stage you will notice that your 'Ubuntu System Settings' has disappeared. So you have to reinstall the ubuntu desktop.
- Also, note you can install
ubuntu-desktop
in the first place instead ofpulseaudio
because the removal of the latter removes the former and correctly so, the installation of the desktop covers pulseaudio install as well.
Community♦
SmodSmod
I also had a similar problem, and none of the above solved it. It turned out that in addition to reinstalling ubuntu-desktop, I had to remove my ~/.pulse folder.
It's not usually there, but I had created it while following some instructions online to solve some specific issues, and later I completely forgot about it.
ketilketil
Not the answer you're looking for? Browse other questions tagged sound14.04pulseaudio or ask your own question.
Track tasks and feature requests
Join 36 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprises Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Nov 20, 2018
There are a lot of widgets warning at boot on Yorp, Warning: Tested with: Kernel -cros-sof-v4.14-rebase: bf94547 DSP FW-glk-004-drop-stable: 1f79920 Topology-master: 8cc1dadd |
assigned ranj063Nov 20, 2018
commented Nov 20, 2018
@keqiaozhang these are due to the virtual widgets and routes in topology. @plbossart do we need to suppress these warnings? |
commented Nov 20, 2018
I understand those warnings can be removed with the topology file, which is a better solution that adding ifdefs in common code shared with the SST driver. @keqiaozhang please file this as a topology issue. |
commented Nov 21, 2018
Moved to thesofproject/soft#135 |
referenced this issue Nov 23, 2018
ClosedGLK topology: some unused widgets warning at boot #135
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment