Extension still partially broken on Firefox

[glciampaglia]

Hi all,

This is in reference to #638. First of all, thanks for responding to my original ticket. I have just checked if the problem was solved with the newer version of the extension (I'm running 3.2.2 updated on May 4, 2026). What is happening is that importing from the browser has resumed to work but only when there is no Jabref instance running: in that case the behavior I see is that on click on the extension a new instance of Jabref is started, and then the import dialog appears on Jabref. If instead there is already a Jabref instance running, nothing happens. I am attaching the logs from Firefox's browser console, using the same ArXiv link as in the original ticket (https://arxiv.org/abs/2603.22277).

console-export-2026-6-23_13-40-27.log

[tobiasdiez]

What version of JabRef do you use?

Do you get any errors in the "connection status" section of the extension options (about:addons > jabRef) when jabref is running?

[mj-ramirez]

Same issue. I gave it a break since may 2026 to see if ongoing updates may sort itself out.

• Error message in browser: Searching for bibliographic data... Logs Popup opened, starting translator run
• Connection status reports all good

the console output excerpt:

Translate: Running handler 0 for translators 5 content.js:1:15062
Translate: Mutation observer registered on node content.js:1:12545
Translate: All translator detect calls and RPC calls complete: content.js:3:2898
No suitable translators found content.js:3:3210

any tips ?

[mj-ramirez]

Ah!
it works for https://arxiv.org/abs/2603.22277.

but does not work for any pubmed
https://pubmed.ncbi.nlm.nih.gov/34703827/

must be a rational explanation somewhere

[glciampaglia]

@tobiasdiez apologies for not get back to you sooner. I am using Jabref v5.13, Firefox 154.0, and JabRef extension v3.2.2.

I don't get any error in the extension options: native messaging says communication with Jabref was successful and the local network connection says Jabref was reachable on port 6050.

I tried again a couple arxiv links (the one I shared plus another one) to see if anything had changed and I still observe the same behavior: if Jabref is not running then importing with the browser extension will cause a new instance of Jabref to start and the import dialog opens correctly. If an instance of Jabref is already running, importing from the extension reaches the "Sending to Jabref" stage but nothing happens on Jabref's side.

I also tried running on the pubmed link shared by @mj-ramirez but in that case it remains stuck on "Searching for bibliographic data".

HTH

[mj-ramirez]

macos additional glitch: Apple could not verify “osxkeychain3063888960255661077.so” is free of malware that may harm your Mac or compromise your privacy

Seems to interfere with running the extension. See if I can "de-quarantine" manually...

[mj-ramirez]

update for macos

Fresh re install of Jabref generated error for the jabref browser extension "Direct app connection (Native Messaging) An unexpected error occurred" message.

1. The installed <org.jabref.jabref.json> file content points to incorrect path for <jabrefHost.py>
2. After correcting the path in <org.jabref.jabref.json> to the correct location of the python script, the import to jabref from https://arxiv.org/abs/2603.22277 does import successfully by starting Jabref.
3. The annoying macos “osxkeychain" warnings remain despite manually "allowing" in systems setting
4. Once Jabref is running NO further import possible.
5. Closing Jabref results does not result in any further successful imports to Jabref form https://arxiv.org/abs/2603.22277..
6. Restarting Browser and Jabref returns to scenario number 2.

Need to inspect the <jabrefHost.py> script... ? Maybe some macos specific "package structure/path" variations ? relocating the script as apparently suggested in the comments of the script ?

Not sure what do about the macos “osxkeychain" warnings.

It amazes me how such a seemingly simple task is yet so complex.