I guess to try to rectify this back on topic...Waterfox sound works as expected without pulse? ^_^  (I'll see myself out the door now.)

Interesting resource here: http://thereisonlyxul.org/

Thank you MiyoLinux.
Sorry MiyoLinux i have nothing against you, I hope you have understood.
Thank you for the answer and solution, but sorry for me is an unacceptable solution.
Because this is another situation where we see a meddling of the same "characters" who created systemd and a short-sighted approach of the Firefox developers. Chrome/Chromium is "made" from Google and I do not want to use it.
So I pinned firefox with /etc/apt/preferences.d/firefox-esr like this:

Package: firefox-esr
Pin: version 52.9.0esr-*
Pin-Priority: 1001

...while it lasts.
Thank you, again MiyoLinux.
Bye.

.mario

I understand!

Each user "should" be free to do what is best for their own personal situation.

In my case, I am a very boring user and my web browsing is very limited; therefore, my "fix" suits me and my situation...it may not be what's best for others. Take care friend!

Edited to add: My reasoning for creating a new desktop file is this...it simply negates the need to edit the original Firefox ESR desktop file when new versions are released. I'm okay with having two "Firefox" listings in my menu, but others may be opposed to that.

siva wrote:
I am curious where you read that iceweasel is something other than a transitional package to firefox-esr.

Here:
https://www.hyperbola.info/
https://www.hyperbola.info/news/iceweas … easel-esr/

and here:
http://thereisonlyxul.org/

EDIT
I see this has been split from the original thread. In that thread, that thread's OP stated he was going back to 52.9 ESR from 60 ESR. That's why I wrote about using an "old," meaning no longer supported, browser.

I really don't understand your post.

My point is that the ESR branch is no less an "old" version of Firefox than any of the listed derivatives: they all use "old" code and are actively maintained, their UIs being clear, visual examples.  The biggest difference is their project's goals.  ESR sacrifices "newness" for overall stability and security updates.  Its forks are separate projects, with their own separate goals, and there are already threads here which profess their pros and cons.

I am curious where you read that iceweasel is something other than a transitional package to firefox-esr.

The very "material" difference is the upstream Firefox ecosystem -- which is creating some of the problems that OP inadvertently discovered.  Without Mozilla's objectives changing over the years, PM would never have had its past; because it is still changing, and significantly, PM may lose an advantage in the future.  On the other hand, the ESR branch will, at least, be "stable enough."  Many people are okay with that.

siva wrote:
Uh...have you looked at the version histories that each one is based on?  And which ones have been unmaintained (for several years)?

Pale Moon is a TRUE fork of Firefox. Where it totally split off from Firefox is immaterial. If an update from FF applies to Pale Moon, PM gets it. It also gets its own updates independent of FF. It just had a new release a few weeks ago. Basilisk had a new release even sooner. Waterfox is also currently maintained. And I read somewhere that Iceweasel is now forked from Basilisk. I really don't understand your post.

Instead of using an old FF version...Pale Moon, Basilisk, Waterfox, or Iceweasel?

Uh...have you looked at the version histories that each one is based on?  And which ones have been unmaintained (for several years)?

On the note of apulse, has anyone tried just adjusting their ~/.asoundrc?
https://codelab.wordpress.com/2017/12/1 … he-rescue/

Package: firefox-esr
Pin: version 52.9.0esr-*
Pin-Priority: 1001

...while it lasts.
Thank you, again MiyoLinux.
Bye.

.mario

@MiyoLinux . . . Thank you!   That is perfect for when the time comes.  Won't go there until there is no other option.

Sorry golinux. I just edited that post, because I remembered something...it's explained in the edit.

Hi all.
Sorry for my poor english and probably for crosspost .
With 60.2.0esr-1~deb9u2 and ALSA i have no sound with Firefox when i browse site like youtube with console error "OpenCubeb() failed to init cubeb". Probably because of this https://gitlab.com/Monsterovich/firefox-fuckpa ?
I installed chromium on my Devuan ASCII and audio of the site with audible content work great.
Excuse me for this rant.
Bye.

.mario

Hi DuaneBarry!

Yes, the latest version of Firefox-ESR requires pulseaudio for sound. However, you can still use it with ALSA.

First, you need to install apulse...

apt install apulse

Now, with that installed, open your terminal (or Run Command), and enter...

apulse firefox-esr

When Firefox opens, go to YouTube and see if sound works. If it does...

I edited this, because it had been so long that I forgot what I actually did. I had to go to another partition to make sure I was correct, because I remembered that my original instructions didn't work for me.

Open your file manager. Make it show hidden files. Navigate to ~/.local/share/applications (if you don't have that folder, create it.)

Create a new file, and name it anything you like, but it has to end with .desktop. I named mine ffesr.desktop

When the file opens, copy and paste the following into it...

[Desktop Entry]
Name=Firefox
Exec=apulse firefox-esr
Terminal=false
Type=Application
Categories=Network;
Icon=firefox

Notice the name is Firefox. That will differentiate it between Firefox-ESR and this one (that you're creating) in the menu.

Save and close the file. It should appear in your menu after that.

.mario