Skip to content
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

BBT startup fails, blocking use and synchronization #3101

Open
dmkaplan2000 opened this issue Dec 8, 2024 · 12 comments
Open

BBT startup fails, blocking use and synchronization #3101

dmkaplan2000 opened this issue Dec 8, 2024 · 12 comments

Comments

@dmkaplan2000
Copy link

dmkaplan2000 commented Dec 8, 2024

Debug log ID

Zotero Debug ID = D1498337816

BBT log file.io = 3LT38P7J-fio-EkENJhJvee9i

What happened?

Recently, when I start Zotero, I often (but not always) get a popup with the following message:

TransactionInactiveError: A request was placed against a transaction which is currently not active, or which is finished.

When this happens, BBT does not appear in menus and in the list of add-ins and synchronization of my library with zotero.org stops working. This problem occurs on two different machines connected to the same Zotero account. Unfortunately, I do not see how to make a BBT debug log as when this happens, it is as if BBT was not present, so no option to generate a BBT log. Instead I have restarted with Zotero debugging enabled and that is what I copied in the Debug Log ID field.

I am running zotero-better-bibtex-6.7.263.xpi on Zotero 7.0.11 (64-bit) on Ubuntu 22.04.5 LTS.

This error seems to be linked to the use of a (system-wide) network proxy as it occurs when the proxy asks for a username and password (that I unfortunately do not know how to permanently modify). When I turn off the proxy, then I do not seem to get this error, but I need the proxy for journal access...

Copy link

github-actions bot commented Dec 8, 2024

Hello @dmkaplan2000,

@retorquere is ready to assist you with Better BibTeX. In order to do so efficiently, a debug log is generally required. The information it containst is key to him understanding, replicating, and resolving your issue. If you have shared a D<number> log, those go to the Zotero team, @retorquere cannot access those.

Here’s how you can share your debug log:

  1. If your issue involves specific references, citekey generation, or exports, right-click on the relevant item(s) and select "Better BibTeX -> Submit Better BibTeX debug log" from the menu.
  2. For issues where items do not play a role, follow these steps:
  • Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
  • Reproduce the problem.
  • Choose "Send Better BibTeX debug report..." from the help menu.

After these steps, you will receive debug ID displayed in red. Please share this ID with @retorquere in this issue thread. If your query is about an export, include both the actually exported result and your expected/desired outcome.

Sharing your debug log gives @retorquere a view of your Better BibTeX configuration and the elements contributing to the issue. This helps him address your concerns more efficiently.

If you have submitted a debug log and its ID looks like D<number>, that debug log goes to the Zotero team, not to @retorquere. Please see the points above how to send a BBT debug log.

Thank you.

PS: If the Debug Log menu is not available, or if it fails to send the debug log, you can use the option under “Help” > “Send debug log to file.io”.

@dmkaplan2000
Copy link
Author

After submission, I see that the file.io BBT export option is now in the help menu, so I edited the original submission to indicate both the Zotero log ID and the BBT file.io log ID.

@retorquere
Copy link
Owner

I'll look at the fio log when I'm home, but I have no access to D<number> logs, only the Zotero crew can access those.

@dmkaplan2000
Copy link
Author

OK, thanks. For the Zotero log ID, I just included it because I had already created it. Please just ignore it if it is not of use.

@retorquere
Copy link
Owner

I see no relevant errors in the log, but debug logging was off at time of log submission, so maybe some were missed?

@dmkaplan2000
Copy link
Author

I redid the export of the debugging log. This time it was definitely enabled up until I exported the BBT file.io log. The error only occurs when the system wide proxy is enabled. The debug log ID is 67HLNVN4-fio-LdLzfv9jufYz .

Thanks,
David

@retorquere
Copy link
Owner

How do I set the system wide proxy under linux?

@dmkaplan2000
Copy link
Author

Sorry for the slow response, I have been teaching (about Quarto + Zotero + BBT). To set the system wide proxy, you go to settings => network => network proxy. I use the automatic option with a proxy configuration URL...

@retorquere
Copy link
Owner

Do you know a proxy I can use?

@dmkaplan2000
Copy link
Author

Yeah, that is the problem... You are welcome to use mine to the point of entering the username and password, but I am a little bit less enthusiastic about sending you my password...

In any case, the configuration URL for my proxy is http://proxy-doc.ird.fr/proxy.pac

@retorquere
Copy link
Owner

Don't want it and fortunately don't need it. The problem reproduces. As of yet no idea how to get around it.

@dmkaplan2000
Copy link
Author

That is something of a relief as I was worried that it was perhaps a problem on my end. Let me know if I can provide any more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants