vimium icon indicating copy to clipboard operation
vimium copied to clipboard

Vimium not working in Firefox/Tor browser after 2.0 upgrade

Open S0AndS0 opened this issue 8 months ago • 7 comments

Describe the bug

  • press G to scroll to bottom of page ⇔ No action
  • press gg to scroll to top of page ⇔ No action
  • press d to scroll to down page ⇔ No action
  • press f for open link in current tab ⇔ No action
  • press F for open link in new tab ⇔ No action
  • press / for search ⇔ No action

Note; was totally/fully functional a few hours ago, so some auto-update seems to have broken things.

I've also tried closing, and reopening, the web-browser; no joy.

I've also tried disabling, and re-enabling, extension; no joy.

I've also tried uninstalling, and re-installing; no joy.

To Reproduce

Steps to reproduce the behavior:

  1. Install Tor browser
  2. Install extension through Mozilla dot Org site
  3. Go to URL 'https://duckduckgo.com/', or 'https://google.com', or really anywhere

Include a screenshot if applicable.

Not applicable

Browser and Vimium version

  • Vimium version: 2.0.4
  • Firefox version: 115.4.0esr

S0AndS0 avatar Oct 26 '23 18:10 S0AndS0

Update rolling back to version 1.67.7 via Mozilla's version history page resulted in joy!!!

I'll be turning off auto-updates until I read back from ya

S0AndS0 avatar Oct 26 '23 18:10 S0AndS0

Hey @S0AndS0, is the issue for you that Vimium wasn't enabled for all sites? See #4348 for background.

philc avatar Oct 27 '23 05:10 philc

Thanks for getting back to me so swiftly!

I re-checked/re-installed version 2.0.4 today and tragically must report toggling the "Access your data for all websites" setting off, and back on again, didn't result in any joy.


Steps taken so far

  • Navigate to Vimium-FF version history
  • Install version 2.0.4
  • Navigate to about:addons
  • Click "Vimium"
  • Click "Permissions"
  • Toggle "Access your data for all websites" to false
  • Toggle "Access your data for all websites" to true
  • Check behavior in different tab and find no joy
  • Navigate to about:addons
  • Click "Vimium"
  • Click "Permissions"
  • Toggle "Access your data for all websites" to false
  • Toggle enable/disable Vimium extension to false
  • Toggle enable/disable Vimium extension to true
  • Toggle "Access your data for all websites" to true
  • Check behavior in different tab and find no joy
  • Navigate to Vimium-FF version history
  • Install version 1.67.7
  • Check behavior in different tab and find joy

On the off chance such things help, here are the details, and permissions, tabs for each version tested so far

Details 1.67.7

  • Allow automatic updates → "Off"
  • Run in Private Windows → "Allow"
  • Version → 1.67.7
  • Last Updated → "October 26, 2023"

Permissions

  • [X] Access your data for all websites
  • [X] Read and modify bookmarks
  • [X] Get data from the clipboard
  • [X] Input data from the clipboard
  • [X] Access browsing history
  • [X] Display notifications to you
  • [X] Access recently closed tabs
  • [X] Access browser tabs
  • [X] Access browser activity during navigation

Details 2.0.4

  • Allow automatic updates → "Off"
  • Run in Private Windows → "Allow"
  • Version → 2.0.4
  • Last Updated → "October 29, 2023"

Permissions

Required permissions for core functionality:

  • [X] Read and modify bookmarks
  • [X] Get data from the clipboard
  • [X] Input data from the clipboard
  • [X] Access browsing history
  • [X] Display notifications to you
  • [X] Access recently closed tabs
  • [X] Access browser tabs
  • [X] Access browser activity during navigation

Optional permissions for added functionality:

  • [X] Access your data for all websites → true

S0AndS0 avatar Oct 29 '23 18:10 S0AndS0

Thanks for the extensive diagnostic info.

Without a logging statement, I have no further ideas.

The last idea I have is perhaps your Vimium settings have somehow become corrupt as part of the upgrade. I believe the synced settings in Firefox will persist even through a reinstall of the extension.

If this were the case, you should see an error in the Console somewhere -- either on the background page or the web page you're browsing. However, If you'd like to rule this out, you can try clearing the settings by going to the Vimium options page, and typing this into Firefox's javascript developer console: chrome.storage.sync.clear(). This will clear all synced state associated with Vimium (but not other extensions).

philc avatar Oct 30 '23 05:10 philc

I ran chrome.storage.sync.clear() as described in the previous post and it gave me the following error message:

Uncaught (in promise) Error: Please set webextensions.storage.sync.enabled to true in about:config undefined
    apply self-hosted:2366
    applySafeWithoutClone resource://gre/modules/ExtensionCommon.sys.mjs:635
    wrapPromise resource://gre/modules/ExtensionCommon.sys.mjs:963

So I set webextensions.storage.sync.enabled to true and this did result in joy, as @S0AndS0 put it.

jxir avatar Oct 31 '23 02:10 jxir

I get the following two errors when loading a page with Vimium enabled:

TypeError: obj is undefined
    utils.js:338:11
TypeError: items is undefined
    mode_normal.js:17:37

In both cases chrome.storage.session.get(key, (obj) => {}) is called and obj is undefined. So it appears to be related to chrome.storage. But running chrome.storage.sync.clear() doesn't seem to change anything.

I checked my Firefox settings and webextensions.storage.sync.enabled was already set to true. No joy so far.

Browser and Vimium version

  • Vimium version: 2.0.6
  • Firefox version: 120.0.1

jsteendam avatar Dec 02 '23 14:12 jsteendam

@philc

... "The last idea I have is perhaps your Vimium settings have somehow become corrupt as part of the upgrade"...

Near as I can tell ya totally be correct to point the finger of blame at corruption, of one sort or another, because not long after opening this issue my drive started failing 🤦

Unless others are reporting similar symptoms, without also experiencing file-system wide corruption, feel free to close this issue with whatever label is appropriate as a "not your problem" status ;-D

S0AndS0 avatar Mar 12 '24 23:03 S0AndS0