SlackwareThis Forum is for the discussion of Slackware Linux.
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 think this effectively solves the divide on pulseaudio and allows everyone to satisfy their use case. I think the main issue left is for someone to investigate bluez-alsa to workaround the bluez pulseaudio caveat. I have no bluetooth hardware and would be unable to test this in the foreseeable future otherwise I'd be trying to build it now.
Does Firefox require PulseAudio to be installed? I haven't had any issues with PulseAudio that I couldn't resolve, but I would like to go back to an ALSA only system if there are no audio issues with Firefox (I don't use any bluetooth devices).
Now, I'd propose a vote here: to have ALSA or PulseAudio as default, and the other one to sit in extra.
I don't mind Pat deciding this himself, by giving me the option to painlessly go PulseAudio-free in 15.0, he has already saved me a lot of dead brain cells. Frankly, I thought for a few minutes and couldn't remember which previous ChangeLog entry before this made me as excited. Many thanks to orbea for his contribution, this earned him a well deserved place in the Slackware Hall of Fame.
Does Firefox require PulseAudio to be installed? I haven't had any issues with PulseAudio that I couldn't resolve, but I would like to go back to an ALSA only system if there are no audio issues with Firefox (I don't use any bluetooth devices).
Mozilla doesn't formally support ALSA backend anymore because of claimed maintenance efforts involved (which afaik makes Firefox work as intended only on certain GNU/Linux setups...) https://bugzilla.mozilla.org/show_bug.cgi?id=1247056
Does Firefox require PulseAudio to be installed? I haven't had any issues with PulseAudio that I couldn't resolve, but I would like to go back to an ALSA only system if there are no audio issues with Firefox (I don't use any bluetooth devices).
It worked fine for me after removing PulseAudio. (Actually, the only remaining issue that I had with PulseAudio was that current version of Firefox was not working properly, as described here, and now with ALSA only it works well.)
I don't mind Pat deciding this himself, by giving me the option to painlessly go PulseAudio-free in 15.0, he has already saved me a lot of dead brain cells.
I did not said that voting should have any effect on decision what goes as default (and, knowing how Slackware development works, it certainly will not). I just thought that it would be interesting to see is majority of people content with PulseAudio, or would still prefer to have it as an option instead.
Does Firefox require PulseAudio to be installed? I haven't had any issues with PulseAudio that I couldn't resolve, but I would like to go back to an ALSA only system if there are no audio issues with Firefox (I don't use any bluetooth devices).
It is my understanding that some versions do require pulseaudio at least for the time being while others, like the Long Term versions do not require Pulse. SeaMonky and Palemonn do not require Pulse and --- FireFox-FuckPA --- a build from Nightly on GitHub obviously does not use nor require Pulse.
You do realize Pulseaudfio will not work without ALSA, right?
Of course I do. The alternatives I had on my mind are PulseAudio setup, just like the default is at the moment, and ALSA only setup, where ALSA only versions of packages that are now in extra/pure-alsa-system would be default, while PulseAudio versions of these, togheter with pulseaudio, pamixer, pavucontrol and xfce4-pulseaudio-plugin packages would sit in extra/pulseaudio.
Hearty "Thank You!" to all who are involved in this modification of defaults. I really did try to utilize and even enjoy Pulseaudio but for me, and I do realize my audio system is far from average, everything used to work perfectly and though now somewhat manageable (thanks to Didier, Bassmadrigal and a few others) Pulse has been such a headache I hate it more than that other intrusive "modification" created by Lord Voldemort, AKA "He who shall not be named". On distros I've tried that have it as default at least that one stays out of my way for the most part. It's still an odd tradeoff for me to give up basic text conf files and a learning curve for nomenclature and syntax for inits that are thankfully still human and rather obvious in Slackware and for what? faster boot times? Puhleaze!.... but still less hassle than Pulse.
Very cool. PulseAudio broke audio in Firejail for me, which is really annoying since I firejail anything that connects to the Internet. Thanks Pat and team!
The way this is implemented just seems so elegant in its simplicity. Many thanks for this.
I'm only using pure ALSA on one old netbook and I'm not going to spend time on bluez-alsa. I've played with it in the past though. If anyone is inclined to work on that, you might save yourself some time by looking at the configuration options and dependencies in the Gentoo ebuilds.
I guess that instructions in extra/pure-alsa-system/README should be complemented with adding following list to /etc/slackpkg/blacklist? As otherwise, it seems that "slackpkg upgrade-all" would want to revert to PulseAudio versions of these packages?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.