[Solved]Zotero on Arch Linux: Segfault & Corrupted Stack Trace Immediately When Sync

edited yesterday at 5:01am
I'm experiencing a persistent crashing issue with Zotero on Arch Linux, and I'm hoping someone can shed some light based on the diagnostic information I've gathered.

The Problem:

Zotero works perfectly fine after a fresh installation. However, as soon as I log in and it starts to sync with my library, it crashes during the process. The sync never successfully completes.

System Information:

Operating System: Arch Linux (fully up-to-date with sudo pacman -Syu)

Zotero Installation: Installed from the AUR using the zotero-bin package. I have tried reinstalling it after the system update.

Diagnostics and Logs:

Terminal Output: When I run zotero from the terminal, it crashes with the following message:

/usr/bin/zotero: line 20: 34092 Segmentation fault (core dumped) "$CALLDIR/zotero-bin" -app "$CALLDIR/app/application.ini" "$@"
GDB Backtrace: I used coredumpctl to analyze the crash, and it provided a corrupted stack trace. This seems to be the most critical piece of information.

(gdb) bt
#0 0x00007f85be5af74c in ?? ()
#1 0x0000000000000000 in ?? ()
I understand that ?? () and the null address indicate stack corruption, which often points to a deep library incompatibility rather than a simple bug.

I found the ~/Zotero/storage folder is empty, which I believe is a result of the crash happening before attachments can be downloaded.

How can I solve this problem?
Thanks in advance for any help or guidance you can provide!
  • Sorry, we can only help with the official tarball (even if the AUR package is just a wrapper). You should test with that.

    You can also try the Zotero beta.

    https://www.zotero.org/support/installation#linux
  • Thanks for the quick reply.

    I've just tested this again to be certain. I downloaded the official tarball from the Zotero website (Zotero-7.0.22_linux-x86_64.tar.bz2), extracted it, and ran the zotero executable directly.

    The result is exactly the same: it crashes during the first sync, and the core dump still shows a corrupted stack trace. This confirms that the issue is not specific to the AUR package.
  • Try the beta. There's unlikely to be any fix here other than something that comes with an update of the Firefox base. (If the current beta doesn't fix it, there'll be a new one soon on an even newer Firefox base.)
  • Thanks, the latest beta version works well!
Sign In or Register to comment.