[opensuse] Firefox 52 and ESR52 require pulseaudio
Such is now default buildconfig. I don't know if alsa is enabled or not in openSUSE rpm builds. https://support.mozilla.org/t5/Videos-sound-pictures-and/Fix-common-audio-an... https://bugzilla.mozilla.org/show_bug.cgi?id=1345661 (comments inhibited) Firefox users whose installations are incompatible with pulseaudio may wish to block updating from 51.x or ESR45.x. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 16.03.2017 um 01:02 schrieb Felix Miata:
Such is now default buildconfig. I don't know if alsa is enabled or not in openSUSE rpm builds.
ALSA is enabled in openSUSE builds for as long as available upstream. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 15 Mar 2017 20:02:25 -0400
Felix Miata
Firefox users whose installations are incompatible with pulseaudio may wish to block updating from 51.x or ESR45.x.
I just went to look as a matter of interest (I'm currently investigating why BBC videos no longer play for me so don't particularly want my version of FF to change.) I was surprised that a change to version 52 was listed as a security upgrade. I don't see changes like 'Send and open a tab from one device to another with Sync' and various others as being security essentials. I thought security upgrades were exactly that? Not wholesale product upgrades. The pulseaudio issue is another example. Why is breaking backwards compatibility advertised as a security upgrade? Full disclosure: I live in the UK and my Youview DVR was recently subject to a forced upgrade that has made the functionality significantly worse in my opinion, so I'm very sensitive about being subject to upgrades that are not what I asked for. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-16 23:29, Dave Howorth wrote:
I was surprised that a change to version 52 was listed as a security upgrade. I don't see changes like 'Send and open a tab from one device to another with Sync' and various others as being security essentials. I thought security upgrades were exactly that? Not wholesale product upgrades.
Because only updating the security problems in the current release needs someone backporting the changes in version 52 back to version 51, say, manually. And doing the same on the next update, and the next, and... It easier to simply go to the next version. Anyway, version 52 crashes completely on my system, doesn't even start. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Am 17.03.2017 um 02:40 schrieb Carlos E. R.:
On 2017-03-16 23:29, Dave Howorth wrote:
I was surprised that a change to version 52 was listed as a security upgrade. I don't see changes like 'Send and open a tab from one device to another with Sync' and various others as being security essentials. I thought security upgrades were exactly that? Not wholesale product upgrades.
Because only updating the security problems in the current release needs someone backporting the changes in version 52 back to version 51, say, manually. And doing the same on the next update, and the next, and...
It easier to simply go to the next version.
Anyway, version 52 crashes completely on my system, doesn't even start.
Is there opened a bug? I have checked your system description and it matches my setup quite well. I'm not experiencing any crash though. I also didn't see similar bugreports in other channels yet. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-03-17 07:24, Wolfgang Rosenauer wrote:
Am 17.03.2017 um 02:40 schrieb Carlos E. R.:
Anyway, version 52 crashes completely on my system, doesn't even start.
Is there opened a bug? I have checked your system description and it matches my setup quite well. I'm not experiencing any crash though.
There is a thread with all the details I could get: "Firefox crashes on start, after last update." Crashes running failsafe, as a new profile and another user, including root. Upstream targz doesn't. I was waiting for comments.
I also didn't see similar bugreports in other channels yet.
Only the automatic reports to upstream. I was considering writing the bugzilla today. Thanks for the interest. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Hi, Am 16.03.2017 um 23:29 schrieb Dave Howorth:
On Wed, 15 Mar 2017 20:02:25 -0400 Felix Miata
wrote: Firefox users whose installations are incompatible with pulseaudio may wish to block updating from 51.x or ESR45.x.
I just went to look as a matter of interest (I'm currently investigating why BBC videos no longer play for me so don't particularly want my version of FF to change.)
I was surprised that a change to version 52 was listed as a security upgrade. I don't see changes like 'Send and open a tab from one device to another with Sync' and various others as being security essentials. I thought security upgrades were exactly that? Not wholesale product upgrades. The pulseaudio issue is another example. Why is breaking backwards compatibility advertised as a security upgrade?
Full disclosure: I live in the UK and my Youview DVR was recently subject to a forced upgrade that has made the functionality significantly worse in my opinion, so I'm very sensitive about being subject to upgrades that are not what I asked for.
it's known for a very long time that it's impossible to keep Firefox on one version for a distribution lifetime. Backporting everything is almost impossible for a distribution without support of upstream. At the same time there are also a lot of people who want or need to have the latest web experience. You get exactly the same with Chrome/Chromium.
From time to time upstream introduces changes which are not nice, unexpected, ugly for one group or the other. There is little we can do about it. For the ALSA case we decided to ease the pain to keep it enabled as long as it works. For Gtk2->Gtk3 we have not even switched yet for Leap while upstream changed quite a while ago.
The only thing we could do is to reassess if we want to ship ESR instead of regular release which would keep the version stable for around a year before a big "leap" would happen. Up to now this was not the favourite and I still think it's not the preferred way for openSUSE. ESR versions are available though via the buildservice if you would like to switch. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R.
-
Dave Howorth
-
Felix Miata
-
Wolfgang Rosenauer