only signed add-ons are allowed, unsigned add-ons are no longer allowed; pref has been removed
please feel free to add to the thread as new things become known or in case there are particular trends in reported problems on the forums :-)
Firefox 46 is scheduled to be released on 2016-04-26
release notes: https://www.mozilla.org/en-US/firefox/46.0/releasenotes/
fixed security issues: https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/#firefox46
some changes that seem relevant to sumo are:
* only signed add-ons are allowed, unsigned add-ons are no longer allowed; pref has been removed
please feel free to add to the thread as new things become known or in case there are particular trends in reported problems on the forums :-)
it looks like the support for "xpinstall.signatures.required" won't be dropped in firefox 46 yet, but one version later... and 46 is quite small in any user facing changes as well.
one change that might be worth to highlight is that now adobe's module that is loaded by default for drm purposes will now also be used to playback h.264 media on windows xp and windows n versions, which do not contain the necessary codecs for this out of the box - bug 1210231
it looks like the support for "xpinstall.signatures.required" won't be dropped in firefox 46 yet, but one version later... and 46 is quite small in any user facing changes as well.
one change that might be worth to highlight is that now adobe's module that is loaded by default for drm purposes will now also be used to playback h.264 media on <s>windows xp and</s> windows n versions, which do not contain the necessary codecs for this out of the box - [https://bugzilla.mozilla.org/show_bug.cgi?id=1210231 bug 1210231]
Thanks Philipp.
''philipp [[#post-68862|said]]''
<blockquote>
it looks like the support for "xpinstall.signatures.required" won't be dropped in firefox 46 yet, but one version later...
</blockquote>
If that becomes definite it will make our KB article [[Add-on signing in Firefox]] wrong and the articles that links to
* https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/
** https://wiki.mozilla.org/Addons/Extension_Signing#Timeline
also would seem to be in need of updating.
From a quick look I could not see mention of the change of intent in the mailing list ''mozilla.addons.user-experience'' e.g.
* ''Extension signing blog post'' https://groups.google.com/forum/#!topic/mozilla.addons.user-experience/slaKs943n4c%5B1-25%5D
* ''what is the schedule ''https://groups.google.com/forum/#!topic/mozilla.addons.user-experience/8Ce0EkLCowo
(I have not been following the tracker
* [https://Bugzil.la/1047239 Bug 1047239 - (signed-addons) Add-on signing revamp] )
firefox 47 was the answer i got from release management after i've inquired why the preference wasn't yet deprecated in friefox 46 beta builds...
i've put an updated revision into our kb article about that, but in other web properties not controlled by us it is the responsibility of their owners to keep the information up-to-date.
firefox 47 was the answer i got from release management after i've inquired why the preference wasn't yet deprecated in friefox 46 beta builds...
i've put an updated revision into our kb article about that, but in other web properties not controlled by us it is the responsibility of their owners to keep the information up-to-date.
Hi philipp, unfortunately the bug says the Adobe plugin doesn't support decoding on XP (comment 7).
Bug 1210231 - Decode unencrypted H.264 and AAC using Adobe's CDM on Windows (Vista, and K/N editions) said this in comment 7:
(Quote)Chris Pearce (:cpearce) 2015-11-01 14:13:57 PST
Note: Adobe have not provided an EME plugin that works on Windows XP, so we can't use their plugin for MP4 playback on Windows XP yet.
However, see Bug 1250766 - Re-enable using Adobe GMP for decoding when system H.264/AAC codecs not available (comment 6)
(Quote)Chris Pearce (:cpearce) 2016-03-02 12:34:08 PST
<snip>
This patch enables playback of MP4 videos for Windows XP users using the Adobe Gecko Media Plugin. We had this in 45, but had to turn it off due to bugs in the Adobe GMP. Those have been fixed, so we should get this uplifted so that WinXP users can finally get MP4 playback.
''jscher2000 [[#post-68863|said]]''
<blockquote>
Hi philipp, unfortunately the bug says the Adobe plugin doesn't support decoding on XP (comment 7).
</blockquote>
''[https://bugzilla.mozilla.org/show_bug.cgi?id=1210231 Bug 1210231] - Decode unencrypted H.264 and AAC using Adobe's CDM on Windows (Vista, and K/N editions)'' said this in comment 7:
'''(Quote)'''
''Chris Pearce (:cpearce) '''2015-11-01''' 14:13:57 PST''
''Note: Adobe have not provided an EME plugin that works on Windows XP, so we can't use their plugin for MP4 playback on Windows XP yet.''
----
However, see ''[https://bugzilla.mozilla.org/show_bug.cgi?id=1250766 Bug 1250766] - Re-enable using Adobe GMP for decoding when system H.264/AAC codecs not available'' (comment 6)
'''(Quote)'''
''Chris Pearce (:cpearce) '''2016-03-02''' 12:34:08 PST''
<snip>
''This patch enables playback of MP4 videos for Windows XP users using the Adobe Gecko Media Plugin. We had this in 45, but had to turn it off due to bugs in the Adobe GMP. Those have been fixed, so we should get this uplifted so that WinXP users can finally get MP4 playback.''
firefox 47 was the answer i got from release management after i've inquired why the preference wasn't yet deprecated in friefox 46 beta builds...
i've put an updated revision into our kb article about that, but in other web properties not controlled by us it is the responsibility of their owners to keep the information up-to-date.
philipp, do you have the person from release mgmt's name? Was the answer given in an email, via IRC or another communication? It would be good to document the change before updating the Add-on signing in Firefox KB article. There's a discussion thread that John99 started in the article's kb forum where you can reply.
''philipp [[#post-68867|said]]''
<blockquote>
firefox 47 was the answer i got from release management after i've inquired why the preference wasn't yet deprecated in friefox 46 beta builds...
i've put an updated revision into our kb article about that, but in other web properties not controlled by us it is the responsibility of their owners to keep the information up-to-date.
</blockquote>
philipp, do you have the person from release mgmt's name? Was the answer given in an email, via IRC or another communication? It would be good to document the change before updating the [[Add-on signing in Firefox]] KB article. There's a discussion thread that John99 started in the article's kb forum where you can reply.
tl;dr preference for allowing unsigned add-ons is still in Firefox 46 for desktop will probably be removed in FF47 for desktop (Android is at least 1 release behind)
philipp posted sylvestre's communication in the other thread:
https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox/discuss/6588#post-13523
tl;dr preference for allowing unsigned add-ons is still in Firefox 46 for desktop will probably be removed in FF47 for desktop (Android is at least 1 release behind)
Does this mean the Android Firefox Release and Beta apk installed manually get updates now outside of Google Play?
Found bugs like
Bug 1192279 - Provide an easy-to-use update-method for users without Play store access
Bug 1235591 - Add Android builds to Bouncer
Roland Tanglao, I noticed there has been a https://www.mozilla.org/firefox/android/all/ and https://www.mozilla.org/firefox/android/beta/all/ for a short while now.
Does this mean the Android Firefox Release and Beta apk installed manually get updates now outside of Google Play?
Found bugs like
Bug 1192279 - Provide an easy-to-use update-method for users without Play store access
Bug 1235591 - Add Android builds to Bouncer
"Does this mean the Android Firefox Release and Beta apk installed manually get updates now outside of Google Play? "
hi james!
my understanding is that if you install any FF Android release (nightly, beta and aurora and even release) outside of the google play store you get updated outside of the google play store
cheers!
...Roland
"Does this mean the Android Firefox Release and Beta apk installed manually get updates now outside of Google Play? "
hi james!
my understanding is that if you install any FF Android release (nightly, beta and aurora and even release) outside of the google play store you get updated outside of the google play store
cheers!
...Roland
h264 playback for xp, vista and windows n versions through adobe's drm module got disabled again last minute for causing crashes and will come in a later release: https://bugzilla.mozilla.org/show_bug.cgi?id=1265815#c19
the update to 46.0 is now live (&throttled - only 25%of users will receive it via auto-update atm).
if you see os x users reporting startup crashes directly after updating to 46.0 it might be due to malware on the system - bug 1262787. there would be a manual removal guide at http://www.thesafemac.com/arg-premier-opinion/ or otherwise the free version of malwarebytes antimalware for mac should do its job as well.
the update to 46.0 is now live (&throttled - only 25%of users will receive it via auto-update atm).
if you see os x users reporting startup crashes directly after updating to 46.0 it might be due to malware on the system - [https://bugzilla.mozilla.org/show_bug.cgi?id=1262787 bug 1262787]. there would be a manual removal guide at http://www.thesafemac.com/arg-premier-opinion/ or otherwise the free version of malwarebytes antimalware for mac should do its job as well.
edit: new article in the kb - https://support.mozilla.org/en-US/kb/firefox-46-crashes-startup-os-x
A issue you may find from Linux users is due to the GTK 3.4+ requirement as of Firefox 46.0.
If the user has GTK3.4+ but is using a GTK2 theme due to ability to do so due to say XFCE as desktop then Firefox may look unthemed.
If the user is using a Linux distro still using GTK 2.x then the user will not be able to run Firefox 46.0 and will have to use say the Firefox 45 ESR builds to still be up to date security wise.
A pretty recent Linux distro release still using the older GTK2 for example is Red Hat 6.7 that was released July 22, 2015 (also Centos 6.7) uses GTK 2.24.23. http://distrowatch.com/table.php?distribution=redhat
Though normally Linux distros should have GTK 3.4 or greater for a good while now as 3.4 came out March 26, 2012.
A issue you may find from Linux users is due to the GTK 3.4+ requirement as of Firefox 46.0.
If the user has GTK3.4+ but is using a GTK2 theme due to ability to do so due to say XFCE as desktop then Firefox may look unthemed.
If the user is using a Linux distro still using GTK 2.x then the user will not be able to run Firefox 46.0 and will have to use say the [https://www.mozilla.org/firefox/organizations/all/ Firefox 45 ESR] builds to still be up to date security wise.
A pretty recent Linux distro release still using the older GTK2 for example is Red Hat 6.7 that was released July 22, 2015 (also Centos 6.7) uses GTK 2.24.23. http://distrowatch.com/table.php?distribution=redhat
Though normally Linux distros should have GTK 3.4 or greater for a good while now as 3.4 came out March 26, 2012.
A top crasher with some Ubuntu flavors and MInt and such similar distros is due to using the Oxygen GTK theme. Users changing to a GTK 3.4+ Theme is usually able to use Firefox fine after.
Though Ubuntu 12.04 LTS is old (April 26, 2012) with outdated packages in a new install however if users manage to update from the old GTK 2.24.x version to GTK 3.4+ then they get crashes if they have the Oxygen GTK theme in use when running Firefox 46.0
Edit: the Oxygen-GTK3 seems to be a issue in Ubuntu 12.04 LTS and not the newer trusty 14.04 LTS.
A top crasher with some Ubuntu flavors and MInt and such similar distros is due to using the '''Oxygen GTK theme'''. Users changing to a GTK 3.4+ Theme is usually able to use Firefox fine after.
[https://bugzilla.mozilla.org/show_bug.cgi?id=1268185 Bug 1268185] - startup crash in liboxygen-gtk.so@0x in firefox 46
For reading as Bugzilla tracker is not a discussion forum.
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
________________
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575781
Firefox 46 crashes on Ubuntu 12.04 (precise) with Oxygen-GTK3
Though Ubuntu 12.04 LTS is old (April 26, 2012) with outdated packages in a new install however if users manage to update from the old GTK 2.24.x version to GTK 3.4+ then they get crashes if they have the Oxygen GTK theme in use when running Firefox 46.0
'''Edit''': the Oxygen-GTK3 seems to be a issue in Ubuntu 12.04 LTS and not the newer trusty 14.04 LTS.
____
Not really a crash but a display glitch some Ubuntu users may be experiencing with Firefox 46.0 is
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1576382
This has been a problem since Firefox 43, but only today I've managed to identify it as a (double) bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1203059
https://bugzilla.mozilla.org/show_bug.cgi?id=1101975
Today there will be a patch release version 46.0.1 with the following bug fixes and patches:
Some addon signatures are expiring and this patch is to mitigate the notifications about an 'unrecognized issuer' error Bug 1267318
Some webpages did not finish loading, the patch is to fix any hangs that prevented pages to finish loading and cache the page Bug 1268922
Firefox sync had an issue where a device name was changed on the account every time preferences for sync were opened, even if they were not changed Bug 1262312
And the last and complicated one is, now a service worker can update a itself when it or after a network fails Bug 1267733
Today there will be a patch release version 46.0.1 with the following bug fixes and patches:
# Some addon signatures are expiring and this patch is to mitigate the notifications about an 'unrecognized issuer' error [https://bugzilla.mozilla.org/show_bug.cgi?id=1267318 Bug 1267318]
# Some webpages did not finish loading, the patch is to fix any hangs that prevented pages to finish loading and cache the page [https://bugzilla.mozilla.org/show_bug.cgi?id=1268922 Bug 1268922]
# Firefox sync had an issue where a device name was changed on the account every time preferences for sync were opened, even if they were not changed [https://bugzilla.mozilla.org/show_bug.cgi?id=1262312 Bug 1262312]
# And the last and complicated one is, now a service worker can update a itself when it or after a network fails [https://bugzilla.mozilla.org/show_bug.cgi?id=1267733 Bug 1267733]
https://www.mozilla.org/firefox/46.0.1/releasenotes/
Add-on signing certificate expiration (Bug 1267318)
Service worker update issue (Bug 1267733)
Build issue when jit is disabled (Bug 1266366)
Page loading issue related to antivirus software (Bug 1268922)
Search plugin issue for various locales (Bug 1246494)
Limit Sync registration updates (Bug 1262312)
1267318 of course is referring to Extensions and not all Addons.
https://www.mozilla.org/firefox/46.0.1/releasenotes/
Add-on signing certificate expiration (Bug 1267318)
Service worker update issue (Bug 1267733)
Build issue when jit is disabled (Bug 1266366)
Page loading issue related to antivirus software (Bug 1268922)
Search plugin issue for various locales (Bug 1246494)
Limit Sync registration updates (Bug 1262312)
1267318 of course is referring to Extensions and not all Addons.
updates to 46.0.1 are now generally switched on again for users of prior versions of firefox (so far only a fiifth of users have been on 46), so we might see a new wave of questions like the mac startup crash by users who have freshly updated.
updates to 46.0.1 are now generally switched on again for users of prior versions of firefox (so far only a fiifth of users have been on 46), so we might see a new wave of questions like the mac startup crash by users who have freshly updated.
