1 |
Duncan posted on Sun, 26 Mar 2017 14:53:04 +0000 as excerpted: |
2 |
|
3 |
> When I enable firefox electrolysis (aka e10s) browser-internal pages |
4 |
> such as about:config, about:support, and about:addons, load, but nothing |
5 |
> actually on the web will load -- the progress bar goes all the way |
6 |
> across and just as the page appears to be parsing, TAB-CRASH, with the |
7 |
> offer to (try to) reload the page (which fails the same way). |
8 |
> |
9 |
> This is regardless of whether I'm running with all extensions (which |
10 |
> I've spent quite some time on weeding out and replacing the non-e10s- |
11 |
> compatible ones, they're all reported compatible with multiprocess now) |
12 |
> enabled, all disabled, in safe mode, even after a fir |
13 |
|
14 |
Seems the problem /may/ have been due to firefox only officially |
15 |
supporting pulseaudio now -- no more alsa support. |
16 |
|
17 |
I was using the apulse library package to work around that issue so I |
18 |
could get audio from the upstream firefox install, without having to |
19 |
install pulseaudio, and it seems apulse breaks if e10s (multi-process |
20 |
firefox) is enabled, thus breaking firefox. |
21 |
|
22 |
FWIW, Mozilla upstream is leaving the alsa build-time feature available, |
23 |
at least for now, but telling distros mozilla no longer tests alsa or |
24 |
cares if it breaks, so it's up to any distros that care to keep working. |
25 |
|
26 |
We'll see how that goes, but meanwhile, at least for now gentoo's firefox |
27 |
ebuild still allows alsa (or jack) instead of pulseaudio, and apparently |
28 |
enables alsa by default if USE="-jack -pulseaudio" (IOW, no separate |
29 |
USE=alsa flag to set). |
30 |
|
31 |
And once I worked thru a couple bugs (and the loonnnggg now effectively |
32 |
required rust dependency build) and got the firefox ebuild actually |
33 |
building again, with alsa, I could enable multi-process/e10s and |
34 |
everything still worked. |
35 |
|
36 |
Testing the mozilla-built package again, e10s was still broken as long as |
37 |
apulse was installed -- and worked but of course without sound with apulse |
38 |
not installed. Switching back to the ebuild-built firefox, with alsa not |
39 |
pulseaudio support, I had both e10s AND audio. =:^) |
40 |
|
41 |
So it would seem apulse breaks firefox multi-process/e10s -- but since |
42 |
the upstream build only supports pulseaudio now, I have four choices, |
43 |
either upstream-build with audio using apulse but no multi-process/e10s, |
44 |
upstream-build without audio but with multi-process/e10s, upstream build |
45 |
but finally give in and install pulseaudio proper, to get both e10s and |
46 |
audio, or do the full gentoo build. |
47 |
|
48 |
For now I'm back to doing the full gentoo build. Unfortunately, the |
49 |
reason I had quit doing that in the first place is because gentoo often |
50 |
takes days, sometimes weeks, to make a current build available after |
51 |
upstream has updated. Which is fine for most things, but when the new |
52 |
build fixes many security vulns as it normally does, and that's my |
53 |
primary way of interacting with the not entirely trusted web, those extra |
54 |
few days after upstream release and vuln publishing before gentoo gets an |
55 |
ebuild ready could mean the difference between me getting compromised, |
56 |
and not. |
57 |
|
58 |
So I had decided to go with the upstream build in ordered to actually be |
59 |
able to upgrade the day a new firefox version, along with all the vulns |
60 |
it fixed, was announced. |
61 |
|
62 |
Now I don't know /what/ I'll do in that regard, as it appears the mozilla |
63 |
folks have put those of us who have chosen not to drink the pulseaudio |
64 |
koolaid between a rock and a hard place. |
65 |
|
66 |
Maybe I'll have to try chromium one of these days... That seems to be |
67 |
where mozilla's headed in any case... |
68 |
|
69 |
-- |
70 |
Duncan - List replies preferred. No HTML msgs. |
71 |
"Every nonfree program has a lord, a master -- |
72 |
and if you use the program, he is your master." Richard Stallman |