freezes after CTRL period

When prompted to hit CTRL Period the app does not load and sits in loading requiring closing of browser to get it restarted. There has to be better way to fix to stop this annoying issue.


1Password Version: Not Provided
Extension Version: 2.0.4
OS Version: Window 10
Sync Type: Not Provided
Referrer: forum-search:freezes after CTRL period

Comments

  • csprings52
    csprings52
    Community Member

    Help!

  • ag_ana
    ag_ana
    1Password Alumni

    Hi @csprings52!

    Can you please send us some logs so we can take a closer look for you?

    After you have sent the email, please feel free to post the ticket number you received so we can locate your message and connect it with this forum discussion.

    Looking forward to your message!

  • csprings52
    csprings52
    Community Member

    No ticket number has been received that I am aware of.

    I can't seem to attach the diagnostic file as it is not a valid file type for your upload function. Zip file and some other proprietary format inside that.

    Here is the text of the Extension Console

    The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol. bg.html
    Uncaught (in promise) TypeError: tab.sendMessage is not a function
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:134
    bg.js:134:21
    Uncaught (in promise) TypeError: tab.sendMessage is not a function
    onopen moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:53
    bg.js:53:25
    👋 Initializing 1Password background.js:2:1850324
    channel: stable
    version: 2.0.4
    build: 20166 (89.0)
    browser: Firefox (89.0)
    os: Windows (10.0) background.js:2:1850417
    Unknown localization message ca54e249e864e1dcd979e950cda49675 commons.js:32
    Unknown localization message 3880daadd71da4058b0464067d2b021e commons.js:32
    Missing required TabClipper parameters. got: object, object, object, undefined, object 3 commons.js:58
    WASM: Initializing. Log Level: Info 1.js:1:4835
    💫 Looking for desktop app com.1password.1password background.js:2:1785892
    📤 Sending message to native core <4095772026> background.js:2:1787910
    Desktop app port disconnected. Error: None background.js:2:1786342
    💫 Looking for desktop app com.1password.1password7 background.js:2:1785892
    📤 Sending message to native core <214805403> background.js:2:1787910
    Cookie “cookie_prefs” has been rejected because it is already expired. set-plugin
    Unchecked lastError value: DataCloneError: The object could not be cloned. 6 commons.js:32
    Some cookies are misusing the recommended “SameSite“ attribute 6
    Unchecked lastError value: DataCloneError: The object could not be cloned. 2 commons.js:32
    Unchecked lastError value: Error: Frame not found, or missing host permission background.js:2
    Unchecked lastError value: Error: Frame not found, or missing host permission background.js:2
    Unchecked lastError value: DataCloneError: The object could not be cloned. 4 commons.js:32
    Unchecked lastError value: Error: Frame not found, or missing host permission background.js:2
    Unchecked lastError value: Error: Frame not found, or missing host permission background.js:2
    Unchecked lastError value: Error: Frame not found, or missing host permission background.js:2
    Unchecked lastError value: Error: Frame not found, or missing host permission background.js:2
    📥 Received message from native core <214805403> background.js:2:1786791
    👍 Finished initializing 1Password background.js:2:1851216
    📤 Sending message to native core <2203833171> background.js:2:1787910
    Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. background.js:2
    Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 2 background.js:2
    📥 Received message from native core <2203833171> background.js:2:1786791
    We have attempted to add and unlock 0 accounts of the total 0 unlocked accounts from the Desktop app. background.js:2:1793808
    Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. background.js:2
    Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. background.js:2
    Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. background.js:2
    Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. background.js:2
    Unchecked lastError value: Error: Could not establish connection. Receiving end does not exist. 4 background.js:2
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    📤 Sending message to native core <3423130231> background.js:2:1787910
    📥 Received message from native core <3423130231> background.js:2:1786791
    Uncaught (in promise) TypeError: tab.sendMessage is not a function
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:134
    bg.js:134:21
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Use of nsIFile in content process is deprecated. NetUtil.jsm:253:8
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18
    Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    moz-extension://cb3379cd-159e-43ab-be4c-6487217fc25d/bg.js:106
    bg.js:106:18

  • ag_ana
    ag_ana
    1Password Alumni

    @csprings52:

    Indeed, you cannot upload zip files in the forum, you can only send them via email. Have you emailed us from the same email address you use here on the forum? I can look for your message manually in the system :+1:

    In the meantime, for confirmation, what version of the 1Password desktop app do you have installed?

  • csprings52
    csprings52
    Community Member

    Who am I emailing, what address?

  • csprings52
    csprings52
    Community Member

    The windows client is 1080 but I am using the Firefox extension 2.0.4 presumably

  • DenalB
    DenalB
    Community Member

    Who am I emailing, what address?

    Just send your logs to 'support@1password.com' and tell about doing this and link this topic here. :)

  • ag_ana
    ag_ana
    1Password Alumni

    @csprings52:

    Please use the email support+x@1password.com. For future reference, all the instructions are in the link I shared with you in this post :+1:

This discussion has been closed.