Menu

#974 Enigmail does not work with Windows-x64 version of TB 67.0b1

closed
nobody
None
nightly
Minor
67.0.b1
Windows
---
nobody
2019-04-07
2019-04-03
No

Enigmail nighly (build date: 2019-04-03, version: 2.1a1pre, git rev: 8a72aeea05311b0b3c0ed395ec6db1908e7fc256) does not work with TB 67.0b1

Discussion

  • Patrick Brunschwig

    I can't confirm this - it's working OK for me.

    Did you restart Thunderbird after updating Enigmail? If you had an older version of Enigmail before upgrading that didn't work in TB 67 anymore, it's quite likely that after upgrading some things would still fail because Enigmail would then fail to unload itself during the upgrade.

     
  • Helmut Leininger

    I have Windows 10 64-bit
    TB 66.0b3 and a nightly build of enigmail was working ok. After updating TB today to version 67.0b1, enigmail stopped working (disappeared from menu). I uninstalled enigmail, terminated TB, downloaded the new nightly enigmail, started TB, installed enigmail and restarted TB again.

    Status:

    • enigmail dows not show up in the menu nor can it be called for mail decription.
    • if Extras/Add-on Einstellungen/Enigmail is opened, all the settings appear to be empty. File chooser in the general settings menu cannot be opened.
    • ...
     
  • Patrick Brunschwig

    That's strange, as Enigmail is working fine for me (and others I know of). Could it be that the Enigmail version you downloaded came from the browser cache? The best way to install nightly builds of Enigmail is to open the Thunnderbird Add-Ons page, and drag & drop the download link from the browser to the Thunderbird page.

    If that doesn't help, then please provide me with some error message from the Thunderbird Error Console.

     
  • Helmut Leininger

    uninstall, restart TB, install by drag&drop, restart TB. The problem persists.

    from the error console:
    ReferenceError: clearTimeout is not defined
    @chrome://enigmail/content/modules/timer.jsm:48:3
    @chrome://enigmail/content/modules/streams.jsm:19:35
    @chrome://enigmail/content/modules/mime.jsm:19:37
    @chrome://enigmail/content/modules/mimeVerify.jsm:19:34
    @chrome://enigmail/content/modules/mimeDecrypt.jsm:18:36
    @chrome://enigmail/content/modules/pgpmimeHandler.jsm:29:41
    startup@jar:file:///C:/Users/hl/Documents/Thunderbird/hl-Standard/extensions/%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D.xpi!/bootstrap.js:35:21
    startup@resource:///modules/BootstrapLoader.jsm:349:16
    callBootstrapMethod@resource://gre/modules/addons/XPIProvider.jsm:1709:33
    startup@resource://gre/modules/addons/XPIProvider.jsm:1808:32
    startup@resource://gre/modules/addons/XPIProvider.jsm:2275:39
    callProvider@resource://gre/modules/AddonManager.jsm:204:31
    _startProvider@resource://gre/modules/AddonManager.jsm:653:5
    startup@resource://gre/modules/AddonManager.jsm:806:14
    startup@resource://gre/modules/AddonManager.jsm:2799:26
    observe@resource://gre/modules/addonManager.js:65:29

    WebExtensions: Loading packed extension from C:\Users\hl\Documents\Thunderbird\hl-Standard\extensions{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}.xpi ext-legacy.js:73
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:4
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:5
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:6
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:7
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:8
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:9
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:10
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:11
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:14
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:15
    WebExtensions: Loading packed extension from C:\Users\hl\Documents\Thunderbird\hl-Standard\extensions{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi ext-legacy.js:73
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:13
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:14
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:15
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:16
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:17
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:18
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:19
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:20
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:21
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:22
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:23
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:24
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:25
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:26
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:27
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:28
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:29
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:30
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:31
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:32
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:33
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:34
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:35
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:36
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:37
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:38
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:39
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:40
    Ignoring unrecognized chrome manifest directive 'overlay'. chrome.manifest:41
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:46
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:47
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:48
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:49
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:50
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:51
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:52
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:53
    Ignoring unrecognized chrome manifest directive 'style'. chrome.manifest:54
    WebExtensions: Loading add-on preferences from C:\Users\hl\Documents\Thunderbird\hl-Standard\extensions{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}.xpi ext-legacy.js:106
    WebExtensions: Firing profile-after-change listeners for {a62ef8ec-5fdc-40c2-873c-223b8a6925cc} ext-legacy.js:110
    WebExtensions: Loading add-on preferences from C:\Users\hl\Documents\Thunderbird\hl-Standard\extensions{e2fda1a4-762b-4020-b5ad-a41df1933103}.xpi ext-legacy.js:106
    WebExtensions: Firing profile-after-change listeners for {e2fda1a4-762b-4020-b5ad-a41df1933103} ext-legacy.js:110
    Mutations-Ereignisse sollten nicht mehr verwendet werden. Verwenden Sie MutationObserver stattdessen. calendar-widgets.xml:276:38
    Overlays.jsm: Could not resolve 1 references
    Array [ menupopup#options-privacy-menupopup ]
    Overlays.jsm:167
    1554306855825 Telemetry::CoveragePing ERROR no endpoint base set Log.jsm:679

     
  • Patrick Brunschwig

    I'm sorry, but you definitely don't have the latest nightly build of Enigmail. That was one of the last fixes I implemented for TB 67, about a month ago.

     
  • Helmut Leininger

    Sorry, but something must be wrong.
    I definitely installed from the page shown in the screenshot. Both by downloading the extension first or by drag&drop

     
  • Patrick Brunschwig

    The file is every day the same. Here is the SHA-1 sum of todays file:
    bdcc9be70c609b48226e57a702df9cd4f63d627f

     
  • Helmut Leininger

    This is exactly what I have.

     
  • Helmut Leininger

    The problem seems to be with TB 64-bit. works ok in TB 32-bit.
    Note:
    before, it was also ok with TB 64-bit.

     
  • Patrick Brunschwig

    • summary: Enigmail does not work with TB 67.0b1 --> Enigmail does not work with Windows-x64 version of TB 67.0b1
     
  • Patrick Brunschwig

    That's very strange. I'll check the 64-bit Windows version.

     
  • Helmut Leininger

    Now, it gets really, really strange . Is there anyself-healing in it?
    I just re-installed TB 64-bit - and enigmail works !!

     
  • Patrick Brunschwig

    • status: open --> closed
     
  • Patrick Brunschwig

    I can only imagine that the installation did not complete before you switched to 32bit...

     
  • Helmut Leininger

    Just tried to reproduce on anotherPC.

    • TB 66.0b3 (64-bit) updated automatically to 67.0b1 + restart -> provider for Google calendar deactivated
    • installed new google calendar provider and enigmail nightly by drag&drop
    • restart TB --> everything ok

    I am sorry for the irritations. Somethuing must have been wrong with my primary PC.

     
  • Patrick Brunschwig

    I just had a similar case, and I think I found the reason for the strange behavior. Thunderbird contains a startup cache, and it looks like that cache is not deleted properly when installing a new version of an existing extension.

    If ever you come across this problem again, the cache is located in C:\Users\<userid>\AppData\Local\Thunderbird\Profiles\<profile ID>\startupCache.
    Simply delete all files in that directory between stopping and restarting Thunderbird.

     

Log in to post a comment.