retorquere / zotero-better-bibtex

Make Zotero effective for us LaTeX holdouts
https://retorque.re/zotero-better-bibtex/
MIT License
5.39k stars 290 forks source link

[BUG] "Better BibTeX startup failed" when zotero 7 restart #2944

Closed opacscdbph44 closed 3 months ago

opacscdbph44 commented 3 months ago

Debug log ID

KDZV86UU-fio-epSj4pov4mGM

What happened?

When I install the plugin, everything is fine. But as soon as I restart zotero, two windows pop up and then the bibtex plugin disappears!

3f1830166c91396aced60199e20da82
github-actions[bot] commented 3 months ago

Hello @opacscdbph44,

@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.

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.

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”.

retorquere commented 3 months ago

I have no access to D<number> logs. Please choose help - debug - restart with debugging enabled, and after restart, follow the instructions above.

opacscdbph44 commented 3 months ago

KDZV86UU-fio-epSj4pov4mGM

is this ok?

if not ok, debug output file are in the attach files. Debug Output.zip

retorquere commented 3 months ago

Yeah that's OK. I will look at it when I have access to my computer.

opacscdbph44 commented 3 months ago

Thanks!

carllx commented 3 months ago

Yeah that's OK. I will look at it when I have access to my computer.

Thanks

retorquere commented 3 months ago

Can you disable the zotero reference plugin, restart, and see if that makes a difference? If not, please disable all non-zotero plugins except better bibtex, reproduce the problem (after "restart with debug logging enabled"), and send a new log.

llity commented 3 months ago

Having the same problem image image By the way, just a quick question, the installation package for BBZ is almost 40Mb, while most plugins are only a few megabytes. Is it possible to reduce the size of the installation package? Thanks

opacscdbph44 commented 3 months ago

Can you disable the zotero reference plugin, restart, and see if that makes a difference? If not, please disable all non-zotero plugins except better bibtex, reproduce the problem (after "restart with debug logging enabled"), and send a new log.

This is the ID of debug information when I disable all non-zotero plugins except better bibtex: L649UIXN-apse/6.7.221-7

However, the bug did not occur when I disable all non-zotero plugins except better bibtex.

It seems like there might be a conflict with this plugin. This is the ID of debug information when I only use (1) better bibtex and (2) Ethereal Style (https://github.com/MuiseDestiny/zotero-style): LUTFH7SH-fio-l6NP5DT6Icgp

opacscdbph44 commented 3 months ago

This bug can be fixed with update Plugin Ethereal Style to 4.7.4. It is also recommended to update zotero to the latest version as well! My problem is fixed already, all friends can try this solution.

github-actions[bot] commented 3 months ago

Thanks for the feedback! Just so you know, GitHub doesn't let me control who can close issues, and @retorquere likes to leave bug reports and enhancements open as a nudge to merge them into the next release.

Quantum-fog commented 3 months ago

The problem was caused by a conflict with Ethereal Style, which has been resolved in Ethereal Style version 4.7.4

young-liuos commented 3 months ago

The problem was caused by a conflict with Ethereal Style, which has been resolved in Ethereal Style version 4.7.4

Currently, there is only 4.7.3, no 4.7.4

opacscdbph44 commented 3 months ago

The problem was caused by a conflict with Ethereal Style, which has been resolved in Ethereal Style version 4.7.4

Currently, there is only 4.7.3, no 4.7.4

try this: https://gitee.com/MuiseDestiny/plugins

or maybe use "check for update" will also work image

retorquere commented 3 months ago

By the way, just a quick question, the installation package for BBZ is almost 40Mb, while most plugins are only a few megabytes. Is it possible to reduce the size of the installation package? Thanks

The bulk of this 40 MB is the optional chinese/japanese transliteration support; it is not in memory unless you enable that.

I will think about a way to bring this in as a separate download, but it's not high priority to me.

llity commented 3 months ago

The bulk of this 40 MB is the optional chinese/japanese transliteration support; it is not in memory unless you enable that. I will think about a way to bring this in as a separate download, but it's not high priority to me.

If it doesn’t impact software performance, it’s not a major concern. However, could we optimize the styling and text hierarchy on the software’s settings page UI? Thanks!

retorquere commented 3 months ago

I'd love for that to look better. It's this way partly because it is an automated translation of the prefs UI I have in Zotero 6, and that has compromises in a lot of places, but also very much because I hate UI work so I don't spend a lot of time on it.