# JabRef Extension with 6.0-alpha2

**URL:** <https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609>\
**Category:** Beta Testing\
**Created:** [June 15, 2025, 12:24am UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609 "2025-06-15T00:24:01Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![jrgant](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/jrgant/32/824_2.png) [@jrgant](https://discourse.jabref.org/u/jrgant)\
**Post date:** [June 15, 2025, 12:24am UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/1 "2025-06-15T00:24:01Z")

</div>

I’m using JabRef 6.0-alpha2 on Kubuntu 24.04 and the browser extension on Zen (Firefox-based). The browser extension fails with the error screen:

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/jabref/original/2X/b/bfa31adc34e8f952f36af36f8adf8fd1864ab089.png)

Things I’ve done, based on the browser extension troubleshooting documentation:

1. Checked the installed org.jabref.jabref.json and confirmed that it lists the correct path to jabrefHost.py.
2. Disabled ad blocker

I also tried in Firefox and got the following error screen

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/jabref/original/2X/8/8b5723a2bead9a4d3d68861ea78a15a731c0a3ea.png)

So, if this is an issue with 6.0-alpha2, I’m reporting it here. Otherwise, if anyone has ideas about how to fix, I’m all ears.

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [June 15, 2025, 11:55am UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/2 "2025-06-15T11:55:34Z")

</div>

HI, thanks for the report.  
Can you please test with [https://builds.jabref.org/main/](https://builds.jabref.org/main/) there were some recent fixes regarding this

---

<div class="post-metadata">

**Author:** ![jrgant](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/jrgant/32/824_2.png) [@jrgant](https://discourse.jabref.org/u/jrgant)\
**Post date:** [June 16, 2025, 3:33pm UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/3 "2025-06-16T15:33:29Z")

</div>

Problem persists after installing [https://builds.jabref.org/main/jabref\_6.0.deb](https://builds.jabref.org/main/jabref_6.0.deb) (June 16)

Not quite sure how to help debug, but if there is output I can provide, happy to do so.

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [June 16, 2025, 8:10pm UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/4 "2025-06-16T20:10:35Z")

</div>

If you get an error in the browser extension, try Ctrl + shift + j to show the output  
and in JabRef the log under help view event log

I also noticed some issues with the executable bit not set on the python script for mac and linux

---

<div class="post-metadata">

**Author:** ![jrgant](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/jrgant/32/824_2.png) [@jrgant](https://discourse.jabref.org/u/jrgant)\
**Post date:** [June 17, 2025, 1:50pm UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/5 "2025-06-17T13:50:23Z")

</div>

The first hurdle was indeed an issue with jabrefHost.py not being executable. The console error message confirmed as much.

I made the script executable and now receive the following in the JabRef error message window:

`b'Exception in thread "main" picocli.CommandLine$UnmatchedArgumentException: Unknown option: \'--importBibtex\'\n\tat info.picocli@4.7.7/picocli.CommandLine$Interpreter.validateConstraints(CommandLine.java:13691)\n\tat info.picocli@4.7.7/picocli.CommandLine$Interpreter.parse(CommandLine.java:13643)\n\tat info.picocli@4.7.7/picocli.CommandLine$Interpreter.parse(CommandLine.java:13588)\n\tat info.picocli@4.7.7/picocli.CommandLine$Interpreter.parse(CommandLine.java:13483)\n\tat info.picocli@4.7.7/picocli.CommandLine.parseArgs(CommandLine.java:1552)\n\tat org.jabref/org.jabref.cli.ArgumentProcessor.`

No error is logged to the browser console any longer, though.

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [June 17, 2025, 3:24pm UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/6 "2025-06-17T15:24:19Z")

</div>

Hi, thanks that’s precisely the error I just fixed yesterday evening. Please try again with the newest version [https://builds.jabref.org/main/](https://builds.jabref.org/main/) And the py script is now marked as executable again

The error was about casing of the command.

---

<div class="post-metadata">

**Author:** ![jrgant](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/jrgant/32/824_2.png) [@jrgant](https://discourse.jabref.org/u/jrgant)\
**Post date:** [June 17, 2025, 4:45pm UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/7 "2025-06-17T16:45:18Z")

</div>

Ah, my bad. Will do. I am on x86\_64 and installed jabref\_6.0.deb the other day. I only see arm64 in the current /main. Apologies if I’m missing something.

I’m having trouble building on my end at the moment, but I will give some effort to setting up a development environment so I can be of more help in the future.

---

<div class="post-metadata">

**Author:** ![Siedlerchr](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/siedlerchr/32/216_2.png) [@Siedlerchr](https://discourse.jabref.org/u/Siedlerchr)\
**Post date:** [June 17, 2025, 5:09pm UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/8 "2025-06-17T17:09:26Z")

</div>

Sorry 🤦 Our bad, we tried to remove duplicate arm builds but ended up deleting the original ones in the pipeline. Argh!

Just merged a fix. Should be ready in roughly 20/30 minutes.

> [@jrgant](#):
>
> I’m having trouble building on my end at the moment, but I will give some effort to setting up a development environment so I can be of more help in the future.

Hi, we have a gudie for setting up a workspace. Mabye that helps you. Otherwise please just tell us where you encounter problems:  
[Set up a local workspace | Developer Documentation](https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace/)

---

<div class="post-metadata">

**Author:** ![jrgant](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.jabref.org/jrgant/32/824_2.png) [@jrgant](https://discourse.jabref.org/u/jrgant)\
**Post date:** [June 17, 2025, 5:53pm UTC](https://discourse.jabref.org/t/jabref-extension-with-6-0-alpha2/5609/9 "2025-06-17T17:53:45Z")

</div>

No worries. Just downloaded the new build, and the browser extension is working again! Really appreciate the help.

I’ll take a look at the developer documentation, as you suggest.