X
Tap here to go to the mobile version of the site.

Support Forum

New addon not compatible now FF66

Posted

So today on my work computer ( i am still having issues with my personal computer(s) 10.6... ( see/read the previous ticket which is been closed not that it solved anything) because lastpass addon signature signing is not valid according to Firefox and nor can I download an older version that is compatible ). I went to do something on my work Firefox profile which I just recently created less than a week ago. I immediately noticed that tree style tabs was not open for some reason so I went to toggle it back on because sometimes it gets popped off, I couldn't find the icon so I went over to add-ons where I immediately notice that I had "no"? add-ons I'm sorry they're called extensions now in the new button that said unsupported. And guess what was in the unsupported category lastpass and tree style taps with a big message about not being verified and that I should click for more info which tells me to contact the developer and blah blah blahat signing is required in Firefox 57 and above.... and now all of a sudden Now I have a big yellow bar "one or more add-ons cannot be verifiedd and has been disabled". So I went back and looked at the version of last passed since I apparently have an outdated version!!! 4.27.2.10 last updated May 2nd 2019 okay so what's the next course of action? I can either remove the addon or find a replacement, find a replacement doesn't find lastpass. However a search does, and guess what version it is............ it is the same version! If it weren't for auto fill on IOS and android I would go back to a text document because this is getting ridiculous, because it is not on all of my devices and it spontaneously disappears.

I know this is a Firefox problem but this will require going to Mozilla to get this thing fixed.

That's all I can think of for now other than frustration frustration frustration frustration frustration and I probably need to reopen my old ticket, which said wait for an update that we'll never come because the addon system changed.


So I just went to my personal profile, same issue. Both profiles have been open ) simultaneously with no issues( since yesterday with the only thing changing that the computer has been put to sleep and woken back up. Here's a screen shot of all my add-ons on there..... Oddly enough the only thing that survived is "multi pass" which I haven't gotten around to touching yet.



So I just closed out of everything, unchecked reopen windows on login, did a full restart. And my work Firefox profile has my 2 extensions back but my personal profile does not. And Firefox things "these extensions do not meet current standards so they have been deactivated". My work computer is brand-new and I received it in October .... so? My personal Firefox profile was created in October or November 2018, and work profiles was created within the last two weeks (i moved from Safari too many tabs and i needed side tabs...). All should have current add-ons using "current standards" but Firefox doesn't think so?

I know this is a Firefox problem but this will require going to Mozilla to get this thing fixed, so well unlikely I will be CCing to firefox/Mozilla.

So today on my work computer ( i am still having issues with my personal computer(s) 10.6... ( see/read the previous ticket which is been closed not that it solved anything) because lastpass addon signature signing is not valid according to Firefox and nor can I download an older version that is compatible ). I went to do something on my work Firefox profile which I just recently created less than a week ago. I immediately noticed that tree style tabs was not open for some reason so I went to toggle it back on because sometimes it gets popped off, I couldn't find the icon so I went over to add-ons where I immediately notice that I had "no"? add-ons I'm sorry they're called extensions now in the new button that said unsupported. And guess what was in the unsupported category lastpass and tree style taps with a big message about not being verified and that I should click for more info which tells me to contact the developer and blah blah blahat signing is required in Firefox 57 and above.... and now all of a sudden Now I have a big yellow bar "one or more add-ons cannot be verifiedd and has been disabled". So I went back and looked at the version of last passed since I apparently have an outdated version!!! 4.27.2.10 last updated May 2nd 2019 okay so what's the next course of action? I can either remove the addon or find a replacement, find a replacement doesn't find lastpass. However a search does, and guess what version it is............ it is the same version! If it weren't for auto fill on IOS and android I would go back to a text document because this is getting ridiculous, because it is not on all of my devices and it spontaneously disappears. I know this is a Firefox problem but this will require going to Mozilla to get this thing fixed. That's all I can think of for now other than frustration frustration frustration frustration frustration and I probably need to reopen my old ticket, which said wait for an update that we'll never come because the addon system changed. So I just went to my personal profile, same issue. Both profiles have been open ) simultaneously with no issues( since yesterday with the only thing changing that the computer has been put to sleep and woken back up. Here's a screen shot of all my add-ons on there..... Oddly enough the only thing that survived is "multi pass" which I haven't gotten around to touching yet. So I just closed out of everything, unchecked reopen windows on login, did a full restart. And my work Firefox profile has my 2 extensions back but my personal profile does not. And Firefox things "these extensions do not meet current standards so they have been deactivated". My work computer is brand-new and I received it in October .... so? My personal Firefox profile was created in October or November 2018, and work profiles was created within the last two weeks (i moved from Safari too many tabs and i needed side tabs...). All should have current add-ons using "current standards" but Firefox doesn't think so? I know this is a Firefox problem but this will require going to Mozilla to get this thing fixed, so well unlikely I will be CCing to firefox/Mozilla.
Attached screenshots
Quote

Additional System Details

Installed Plug-ins

  • Shockwave Flash 32.0 r0

Application

  • Firefox 66.0.3
  • User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:66.0) Gecko/20100101 Firefox/66.0
  • Support URL: https://support.mozilla.org/1/firefox/66.0.3/Darwin/en-US/

Extensions

  • hotfix-update-xpi-intermediate 1.0.2 (hotfix-update-xpi-intermediate@mozilla.com)
  • LastPass: Free Password Manager 4.27.2.10 (support@lastpass.com)
  • Tree Style Tab 3.0.10 (treestyletab@piro.sakura.ne.jp)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription:
  • adapterDeviceID: 0x5926
  • adapterDrivers:
  • adapterRAM:
  • adapterVendorID: 0x8086
  • contentUsesTiling: True
  • crashGuards: []
  • driverDate:
  • driverVersion:
  • featureLog: {u'fallbacks': [], u'features': [{u'status': u'available', u'description': u'Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'HW_COMPOSITING'}, {u'status': u'available', u'description': u'OpenGL Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'OPENGL_COMPOSITING'}, {u'status': u'opt-in', u'description': u'WebRender', u'log': [{u'status': u'opt-in', u'message': u'WebRender is an opt-in feature', u'type': u'default'}], u'name': u'WEBRENDER'}, {u'status': u'blocked', u'description': u'WebRender qualified', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blocked', u'message': u'No qualified hardware', u'type': u'env'}], u'name': u'WEBRENDER_QUALIFIED'}, {u'status': u'available', u'description': u'Off Main Thread Painting', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'OMTP'}]}
  • info: {u'TileHeight': 1024, u'ApzWheelInput': 1, u'ApzDragInput': 1, u'ApzKeyboardInput': 1, u'ApzAutoscrollInput': 1, u'AzureFallbackCanvasBackend': u'none', u'TileWidth': 1024, u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'skia', u'AzureContentBackend': u'skia'}
  • lowEndMachine: False
  • numAcceleratedWindows: 1
  • numTotalWindows: 1
  • offMainThreadPaintEnabled: True
  • offMainThreadPaintWorkerCount: 3
  • targetFrameRate: 60
  • usesTiling: True
  • webgl1DriverExtensions: GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader5 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_attrib_64bit GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_sRGB_decode GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_ATI_texture_mirror_once GL_NV_texture_barrier
  • webgl1Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_texture_compression_rgtc EXT_frag_depth EXT_sRGB EXT_shader_texture_lod EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context
  • webgl1Renderer: Intel Inc. -- Intel(R) Iris(TM) Plus Graphics 640
  • webgl1Version: 4.1 INTEL-12.4.7
  • webgl1WSIInfo: CGL
  • webgl2DriverExtensions: GL_ARB_blend_func_extended GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader5 GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_occlusion_query2 GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_subroutine GL_ARB_shading_language_include GL_ARB_tessellation_shader GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_vertex_attrib_64bit GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_EXT_texture_sRGB_decode GL_APPLE_client_storage GL_APPLE_container_object_shareable GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_texture_range GL_ATI_texture_mirror_once GL_NV_texture_barrier
  • webgl2Extensions: EXT_color_buffer_float EXT_texture_compression_rgtc EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_texture_float_linear WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_lose_context
  • webgl2Renderer: Intel Inc. -- Intel(R) Iris(TM) Plus Graphics 640
  • webgl2Version: 4.1 INTEL-12.4.7
  • webgl2WSIInfo: CGL
  • windowLayerManagerRemote: True
  • windowLayerManagerType: OpenGL
  • windowUsingAdvancedLayers: False

Modified Preferences

Misc

  • User JS: No
  • Accessibility: Yes
Seburo
  • Top 25 Contributor
  • Moderator
645 solutions 4727 answers

Late on Friday May 3rd, we became aware of an issue with Firefox that prevented existing and new add-ons from running or being installed. We are very sorry for the inconvenience caused to people who use Firefox.

We rolled-out a fix for release, beta and nightly users on Desktop. The fix will be automatically applied in the background within the next few hours, you don’t need to take active steps.

In order to be able to provide this fix on short notice, we are using the Studies system. You can check if you have studies enabled as follows:

  1. Click the menu Fx57Menu button at the top right of the Firefox window.
  2. Click on Options (Windows) or Preferences (Mac and Linux).
  3. Select the Privacy & Security panel and scroll down to the Firefox Data Collection and Use section.
  4. The box next to Allow Firefox to install and run studies should be checked.
    • If the box is not checked, click it to check mark the setting.
      Fx61DataCollection-Studies

You can disable studies again, if you wish, after your add-ons have been re-enabled. See About Studies for more information.

Please do not delete your add-ons as an attempt to fix. You will lose any data related to the add-on. Disabled add-ons will not lose any data.

There are a number of work-arounds being discussed in the community. These are not recommended as they may conflict with fixes we are deploying. We’ll let you know when further updates are available that we recommend, and appreciate your patience.

There is no fix available for Android at this time. The team is working on it.

Late on Friday May 3rd, we became aware of an issue with Firefox that prevented existing and new add-ons from running or being installed. We are very sorry for the inconvenience caused to people who use Firefox. We rolled-out a fix for release, beta and nightly users on Desktop. The fix will be automatically applied in the background within the next few hours, you don’t need to take active steps. In order to be able to provide this fix on short notice, we are using the Studies system. You can check if you have studies enabled as follows: # Click the menu [[Image:Fx57Menu]] button at the top right of the Firefox window. # Click on Options (Windows) or Preferences (Mac and Linux). # Select the '''Privacy & Security''' panel and scroll down to the ''Firefox Data Collection and Use'' section. # The box next to ''Allow Firefox to install and run studies'' should be checked. #*If the box is not checked, click it to check mark the setting.<br>[[Image:Fx61DataCollection-Studies|width=500]] You can disable studies again, if you wish, after your add-ons have been re-enabled. See [[About Studies]] for more information. Please do not delete your add-ons as an attempt to fix. You will lose any data related to the add-on. Disabled add-ons will not lose any data. There are a number of work-arounds being discussed in the community. These are not recommended as they may conflict with fixes we are deploying. We’ll let you know when further updates are available that we recommend, and appreciate your patience. There is no fix available for Android at this time. The team is working on it.
Was this helpful to you? 1
Quote

Question owner

Original context is lastpass support and I am also by "ticket" referencing a previous P2018P ticket that was created with lastpass on Mac OS X 10.6 which is on all of my personal computers. The gist of that ticket is that all of a sudden my add-ons ( in retrospect lastpass and a couple others ) we're self uninstalling with no notification and no longer downloadable because they weren't the new version and old versions were scrubbed and my archived copies were {)"'"corrupt"'"(} now?. And if I could get it to load it said they weren't verified and would not install.

And pardon the spelling errors above mostly incorrect words and spots I thought I fix them but they apparently didn't get fixed.

I find it very interesting that this P2019P has almost duplicated my previous P2018P experience, however with a brand-new profile and brand-new Firefox as of October 2018.

If you are referencing the current P2019P problem please say so if you can, if you're referencing my P2018P problem please clearly state that as obviously I have two problems mentioned in my posts.

In the meantime I won't hold my breath and i will go back to working so I can repair my car, get to work and hopefully at some point save up for a new Computer of my own ( unfortunately I want my next one to last 10 years like my last one and now that nothing is upgradable on apples anymore so it's really expensive just to start with creating a larger barrier of entry. (Video editing)). although it's not like I'm going to abandon my old devices has they all start to find niche uses (FireWire) so it would be at least nice to sync some data across automatically not by sneakernet ( Dropbox*, FF**, Lastpass**, googledrive**, box*, out of sync copies are hell to deal with manually. *dead on 10.6, ** semi still functional for now? ).

Be glad that I self censor because unnecessarily discontinued ewaste is a hot topic. //part sarcasm// Because of security everybody should buy a new computer every six months to keep up with Moore's Law no matter if they can afford it. Well we make things abnormally higher cost with built-in ram, built-in storage, built-in batteries, which then get recalled and then the manufacturer has to deal with exploding decommissioning warehouses because they can't get the batteries out fast enough.

At least we're moving away from the kitchen sink of add-ons to fix things era (status forever, Setting sanity, closed tab button addons)

update Suddenly my extensions have options to enable and disable them in the unsupported extension tab and after a reload of the Extensions page they are in the extension tab again ????? Is this resolved? For how long?

Original context is lastpass support and I am also by "ticket" referencing a previous P2018P ticket that was created with lastpass on Mac OS X 10.6 which is on all of my personal computers. The gist of that ticket is that all of a sudden my add-ons ( in retrospect lastpass and a couple others ) we're self uninstalling with no notification and no longer downloadable because they weren't the new version and old versions were scrubbed and my archived copies were {)"'"corrupt"'"(} now?. And if I could get it to load it said they weren't verified and would not install. And pardon the spelling errors above mostly incorrect words and spots I thought I fix them but they apparently didn't get fixed. ''I find it very interesting that this P2019P has almost duplicated my previous P2018P experience, however with a brand-new profile and brand-new Firefox as of October 2018.'' If you are referencing the current P2019P problem please say so if you can, if you're referencing my P2018P problem please clearly state that as obviously I have two problems mentioned in my posts. In the meantime I won't hold my breath and i will go back to working so I can repair my car, get to work and hopefully at some point save up for a new Computer of my own ( unfortunately I want my next one to last 10 years like my last one and now that nothing is upgradable on apples anymore so it's really expensive just to start with creating a larger barrier of entry. (Video editing)). although it's not like I'm going to abandon my old devices has they all start to find niche uses (FireWire) so it would be at least nice to sync some data across automatically not by sneakernet ( Dropbox*, FF**, Lastpass**, googledrive**, box*, out of sync copies are hell to deal with manually. *dead on 10.6, ** semi still functional for now? ). Be glad that I self censor because unnecessarily discontinued ewaste is a hot topic. //part sarcasm// Because of security everybody should buy a new computer every six months to keep up with Moore's Law no matter if they can afford it. Well we make things abnormally higher cost with built-in ram, built-in storage, built-in batteries, which then get recalled and then the manufacturer has to deal with exploding decommissioning warehouses because they can't get the batteries out fast enough. At least we're moving away from the kitchen sink of add-ons to fix things era (status forever, Setting sanity, closed tab button addons) update Suddenly my extensions have options to enable and disable them in the unsupported extension tab and after a reload of the Extensions page they are in the extension tab again ????? Is this resolved? For how long?

Modified by iMark7777777

Was this helpful to you?
Quote

Question owner

just saw the reply: Seburo: thanks. looks like that was already enabled. FYI this happened today somewhere between 12PM when I close the computer after using it since 8am and when I got home and opened it backup and was very unpleasantly surprised at about 2PM.

Unfortunately I learned about deleting extension Data the hard way last year when lastpass suddenly uninstalled itself with no warning with the very briefest of opportunities to click "don't uninstall" only if you were opening Firefox with the extension page open previously. That happened on 3 out of 3+ Firefox profiles/computers before on the last working one I made a backup/ and i have not opened since out of paranoia the one remaining working profile.

I would move to chrome if it wasn't a resource hog, and spontaneously decided to close/not reopen tabs and IE/edge is definitely not an option do to cross platforms, and opera has always been funky with the settings. There's a lot of frustration and wasted time around Firefox in the last two years for me.

just saw the reply: Seburo: thanks. looks like that was already enabled. FYI this happened today somewhere between 12PM when I close the computer after using it since 8am and when I got home and opened it backup and was very unpleasantly surprised at about 2PM. Unfortunately I learned about deleting extension Data the hard way last year when lastpass suddenly uninstalled itself with no warning with the very briefest of opportunities to click "don't uninstall" only if you were opening Firefox with the extension page open previously. That happened on 3 out of 3+ Firefox profiles/computers before on the last working one I made a backup/ and i have not opened since out of paranoia the one remaining working profile. I would move to chrome if it wasn't a resource hog, and spontaneously decided to close/not reopen tabs and IE/edge is definitely not an option do to cross platforms, and opera has always been funky with the settings. There's a lot of frustration and wasted time around Firefox in the last two years for me.

Modified by iMark7777777

Was this helpful to you?
Quote
XKalifornian 0 solutions 1 answers

Just found out about this update and problem. Verified that Allow Firefox to install and run studies was checked. Somewhere I read to go to add-ons and try to update/re-install the extension. There, I get "Download failed. Please check your connection". My connection is fine and I've been working on stuff all morning. Why is FF extension the only link that has a problem? I got the email about it being fixed in a few hours, that seems to have started a few days ago. When will this be resolved Mozilla?

Just found out about this update and problem. Verified that ''Allow Firefox to install and run studies'' was checked. Somewhere I read to go to add-ons and try to update/re-install the extension. There, I get "Download failed. Please check your connection". My connection is fine and I've been working on stuff all morning. Why is FF extension the only link that has a problem? I got the email about it being fixed in a few hours, that seems to have started a few days ago. When will this be resolved Mozilla?
Was this helpful to you?
Quote
jscher2000
  • Top 10 Contributor
8427 solutions 68757 answers

Helpful Reply

Hi XKalifornian, has the study not shown up under about:studies, either in the Active or Completed list on the about:studies page?

If the study appears on the about:studies page:

The study downloads and runs a hotfix extension, and that installs a new certificate and then does an immediate re-verification of extensions. The certificate should show up here:

  • Windows: "3-bar" menu button (or Tools menu) > Options
  • Mac: "3-bar" menu button (or Firefox menu) > Preferences
  • Linux: "3-bar" menu button (or Edit menu) > Preferences
  • Any system: type or paste about:preferences into the address bar and press Enter/Return to load it

In the search box at the top of the page, type cert and Firefox should filter to the Certificates section. Then click the "View Certificates" button. Check the "Authorities" tab to see whether Mozilla is listed with the new certificate. You can compare the attached screenshot.

If the certificate is missing:

Unfortunately, the hotfix was not successful and we will need to provide further steps to install the certificate, or await further updates from the Add-ons team.

If the certificate was installed but installed extensions still show as unverified and/or new extensions can't be installed because they are corrupted:

It sounds as though the hotfix didn't successfully trigger immediate re-verification. To trigger a re-verification sooner than the usual "every 24 hours," you can use this method to clear the time stamp for the last time Firefox last re-verified.

(A) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(B) In the search box above the list, type or paste xpi- and pause while the list is filtered

(C) Right-click the app.update.lastUpdateTime.xpi-signature-verification preference and click Reset on the context menu -- the numeric value will disappear and the preference will say it is now a "string".

The next time you exit and restart Firefox, the re-verification should be performed within about a minute.

Success?

Hi XKalifornian, has the study not shown up under about:studies, either in the Active or Completed list on the '''about:studies''' page? ''If the study appears on the'' about:studies ''page:'' The study downloads and runs a hotfix extension, and that installs a new certificate and then does an immediate re-verification of extensions. The certificate should show up here: * Windows: "3-bar" menu button (or Tools menu) > Options * Mac: "3-bar" menu button (or Firefox menu) > Preferences * Linux: "3-bar" menu button (or Edit menu) > Preferences * Any system: type or paste '''about:preferences''' into the address bar and press Enter/Return to load it In the search box at the top of the page, type ''cert'' and Firefox should filter to the '''Certificates''' section. Then click the "View Certificates" button. Check the "Authorities" tab to see whether Mozilla is listed with the new certificate. You can compare the attached screenshot. ''If the certificate is missing:'' Unfortunately, the hotfix was not successful and we will need to provide further steps to install the certificate, or await further updates from the Add-ons team. ''If the certificate was installed but installed extensions still show as unverified and/or new extensions can't be installed because they are corrupted:'' It sounds as though the hotfix didn't successfully trigger immediate re-verification. To trigger a re-verification sooner than the usual "every 24 hours," you can use this method to clear the time stamp for the last time Firefox last re-verified. (A) In a new tab, type or paste '''about:config''' in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk. (B) In the search box above the list, type or paste '''xpi-''' and pause while the list is filtered (C) Right-click the '''app.update.lastUpdateTime.xpi-signature-verification''' preference and click Reset on the context menu -- the numeric value will disappear and the preference will say it is now a "string". The next time you exit and restart Firefox, the re-verification should be performed within about a minute. Success?
Was this helpful to you? 1
Quote

Question owner

so this problem is affecting me in more ways than one, when I got back to my life outside of work I was greeted by this on Firefox 48 on 10.8. Do I dare open up my main profile on my main computer running Firefox 48? mac 10.6 and a lot more extensions. or all the other profile(s).

and "about:studies" is not a valid address. I exported and imported the certificate as it was not there, I will try to attach incase anybody else needs it. this was scraped from a clean Firefox installation then hashed and uploaded, please verify the certificate as it says to do on install. https://drive.google.com/open?id=1Cm6womKdWCiSW5i3Igelk7MR07fZYzR-

....... and.... restart.... NOP? no wait maybe that worked? unfortunately all of them are now incompatible. Screen Shot 2019-05-06 at 11.12.02 AM.png

so this problem is affecting me in more ways than one, when I got back to my life outside of work I was greeted by this on Firefox 48 on 10.8. Do I dare open up my main profile on my main computer running Firefox 48? mac 10.6 and a lot more extensions. or all the other profile(s). and "about:studies" is not a valid address. I exported and imported the certificate as it was not there, I will try to attach incase anybody else needs it. this was scraped from a clean Firefox installation then hashed and uploaded, please verify the certificate as it says to do on install. https://drive.google.com/open?id=1Cm6womKdWCiSW5i3Igelk7MR07fZYzR- ....... and.... restart.... NOP? no wait maybe that worked? unfortunately all of them are now incompatible. Screen Shot 2019-05-06 at 11.12.02 AM.png

Modified by iMark7777777

Was this helpful to you?
Quote
jscher2000
  • Top 10 Contributor
8427 solutions 68757 answers

Hi iMark7777777, older Firefox versions did not support either studies OR the necessary WebExtensions APIs to run the hotfix extension.

Mozilla might issue a different kind of hotfix for those versions, but we do not have any official announcement on that.

If you need to re-enable extensions in Firefox 48 sooner, you might need to use an unsupported unofficial workaround to get the new certificate, such as the ones in this thread: https://support.mozilla.org/questions/1258165#answer-1218833

Hi iMark7777777, older Firefox versions did not support either studies OR the necessary WebExtensions APIs to run the hotfix extension. Mozilla might issue a different kind of hotfix for those versions, but we do not have any official announcement on that. If you need to re-enable extensions in Firefox 48 sooner, you might need to use an unsupported unofficial workaround to get the new certificate, such as the ones in this thread: https://support.mozilla.org/questions/1258165#answer-1218833

Modified by jscher2000

Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.