-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error connecting to JabRef" but reference is sent fine to Jabref #493
Comments
I am having a similiar error - when running your command, this is my output:
I do have also a problem with my surface and its network driver, so I am trying to fix this at the same time. The error form the jabref extension is:
|
Thanks! Sadly the error message doesn't contain anything helpful, except for that the Jabref script didn't respond in the way Chrome was expecting it, see https://developer.chrome.com/docs/apps/nativeMessaging/#native-messaging-debugging. So we have to dig deeper, if you have a bit of time. Can you please locate the powershell script (its in the same folder as the jabref exe) If you do this and then import something from the browser extension, there should be a small popup printing exactly the same output as the command above. If there is no popup at all, please use the debug statement in the powershell script also in the If that doesn't point to anything meaningful, I have to investigate if the last point in https://developer.chrome.com/docs/apps/nativeMessaging/#native-messaging-debugging is helpful:
|
Okay so, before I run any scripts just a little update. Now I will just finish a bit of work that way and try your comment :) Thank you for your time |
This may be the same issue: JabRef/jabref#9196 |
Thanks!
I think this is the culprit. The absence of this message means that JabRef cannot find the already opened instance, which leads then to the issues you observe. There are already similar issues reported at the main repo JabRef/jabref#9196. These should be fixed with the next release of JabRef and hopefully your issue disappears then as well. Sorry for the inconvenience! |
The "Error connecting to JabRef" issue remains under newest version 5.8 Brave [Version 1.46.144 Chromium: 108.0.5359.128 (Official Build) (64-bit)] |
@DvP17 sorry for the late reply. Could you please follow the debug steps outlined at #493 (comment). That hopefully allows me to find the origin of the issue. |
@tobiasdiez Thank you for your answer. I followed your instructions and it simply prints out a pop-up window with the BibTeX citation (attached). It also imports successfully, but there is still the new tab showing up in the browser with the error message: "Error when communicating with the native messaging host. at chrome-extension://bifehkofibaamoeaopjglfkddgkijdlh/browser-polyfill.min.js:1:6365" |
Okay, so this means that the correct message is passed to JabRef. That's already a good start. Could you also try to replace the "return ..." line that follows by |
Sorry @DvP17 for the late response. Thanks for testing it further. Yes, the response looks fine. So I'm lost. Just to make sure that I properly understand the issue: The reference is correctly added in JabRef, but you still get an error message in your browser, right? |
No worries. Thank you for your reply!
Yes, that is correct. |
That's strange, and I've no idea how to fix this properly. What I can offer is to add a preference option that silences all error messages. Then you don't get these false-positives, but also no notifications something "real" is broken. Would that be a solution, or do you have any other ideas how to address this issue? |
Since I'm not familiar with the code, I'm not sure what might cause the error message. What triggers the error message, where is it coming from? Is the powershell script opening the respective html connection? Yes, suppressing error messages might be helpful. |
I fix this by modify the code in JabRefHost.ps1 line 39 and 40 into this:
Drop all output make it works. This issue seems to caused by the unexpected output polluting the This will make the Hope this will fix yours too. |
* Fix the error with the solution based on JabRef/JabRef-Browser-Extension#493 (comment) * Maintain stdout from jabref * Update CHANGELOG.md
Hi,
I just started using Jabref a couple of days ago and I'm seeing this issue when importing sources via the browser extension.
If I go to a website like Wikipedia or Arxiv and click on the Jabref extension, the data is sent to Jabref as I would expect and I can import it without issues, but I still get the "Error connecting to Jabref" error tab on the browser. An interesting detail is that this only happens if Jabref is already running, otherwise the extension seems to open Jabref and import the references without any issue.
Both Jabref and the extension where downloaded from the official page links, I'm not running any development version or similar.
I have tried adding the jabref-firefox.json path to the register as mentioned in the manual, but no changes.
I'm using the following versions if it helps:
The text was updated successfully, but these errors were encountered: