Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I read about PulseAudio and thought it might be nice to try (especially the way you could individually control the volume of all applications seems nice), so I installed it and it worked fine.
I rebooted, and now it doesn't work again. Before, when I opened pavucontrol and went to the "Output Devices" tab, it showed the actual output sevices I have. Now it only lists one called "dummy output".
So what's the problem? Also, can I start it before X11 (I guess that putting "pulseaudio --start" in ~/.bash_profile should do it)?
The only device shown is "dummy output"
This may be caused by different reasons, one of them being the .asoundrc file in your home taking precedence over the systemwide /etc/asound.conf.
The only device shown is "dummy output"
This may be caused by different reasons, one of them being the .asoundrc file in your home taking precedence over the systemwide /etc/asound.conf.
The user file is modified also by the tool asoundconf or by its graphical variant asoundconf-gtk (the latter is named "Default sound card" in the menu) as soon as you run it. You can prevent the effects of .asoundrc altogether by commenting the last line like this:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.