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.
Actually I rather imagine it is Mozilla's thinking "Ah good! Now, with PA, Linux sound is somebody elses problem".
Probably... this goes back to the UNIX philosophy. Do one thing and do it well. This will obviously open up a can of worms, but why not leave the audio problems to someone else when they can focus on the browser and keeping it secure? Yes, I'm aware there's probably thousands of examples where this isn't the case and programs support 30 different sound managers/servers, but there are probably thousands of examples where developers have done the exact same thing as Mozilla.
Like it or not, pulseaudio is the primary sound manager in Linux. Almost all distros use that as their default sound manager, so from Mozilla's standpoint, it makes sense to go to the highest common denominator, not to enable the few obscure situations when someone decides to not use pulseaudio and apply that manpower elsewhere than testing someone's obscure pulseaudio-less system. Does this work for everyone? Obviously not, but for the vast majority of people, it works fine.
At least you're running a distro where the Firefox package is provided enabling alsa and it is relatively easy to build your own if a version you want is not provided by Pat.
Nothing but respect, but this might not be the best argument for Slackers. (as in the other package that goes unnamed)
I wasn't trying to cater to Slackers, but what Mozilla's thought process might be. We've seen this same situation for programs that require systemd, some drop support for non-systemd distros. It may not be desired by people who don't like it, but when you want to focus your resources on other aspects of the program, you might need to cut support for less common systems out there. It sucks, but it's reality.
$ pavucontrol
pavucontrol: error while loading shared libraries: libpulse-mainloop-glib.so.0: cannot open shared object file: No such file or directory
$ pavucontrol
pavucontrol: error while loading shared libraries: libpulse-mainloop-glib.so.0: cannot open shared object file: No such file or directory
This is off topic. Please open a new thread for a new topic.
Which version of Slackware are you using?
The file libpulse-mainloop-glib.so.0 is shipped in the pulseaudio package. Why do you miss it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.