Zotero 10 crashes on MacOS
Latest version MacOS 26.6.2. Crashes on opening on a Macbook Neo.
Launching from a terminal gives the possibly relevant message:
Missing chrome or resource URL: chrome://zotero/skin/16/white/loading.svg
Further output:
UNSUPPORTED (log once): POSSIBLE ISSUE: unit 1 GLD_TEXTURE_INDEX_2D is unloadable and bound to sampler type (Float) - using zero texture because texture unloadable
zsh: segmentation fault /Applications/Zotero.app/Contents/MacOS/zotero
Runs fine on linux (Ubuntu 24.04)
Launching from a terminal gives the possibly relevant message:
Missing chrome or resource URL: chrome://zotero/skin/16/white/loading.svg
Further output:
UNSUPPORTED (log once): POSSIBLE ISSUE: unit 1 GLD_TEXTURE_INDEX_2D is unloadable and bound to sampler type (Float) - using zero texture because texture unloadable
zsh: segmentation fault /Applications/Zotero.app/Contents/MacOS/zotero
Runs fine on linux (Ubuntu 24.04)
Upgrade Storage
When launched with -safe a whole bunch of messages starting with
xattr: [Errno 1] Operation not permitted: '/Applications/Zotero.app/Contents/_CodeSignature/CodeResources'
xattr: [Errno 1] Operation not permitted: '/Applications/Zotero.app/Contents/_CodeSignature'
xattr: [Errno 1] Operation not permitted: '/Applications/Zotero.app/Contents/MacOS/libfreebl3.dylib'
xattr: [Errno 1] Operation not permitted: '/Applications/Zotero.app/Contents/MacOS/liblgpllibs.dylib'
xattr: [Errno 1] Operation not permitted: '/Applications/Zotero.app/Contents/MacOS/plugin-container.app/Contents/_CodeSignature/CodeResources'
occurred. Many others similar to this occurred. App crashes without troubleshooting mode.
How about with
/Applications/Zotero.app/Contents/MacOS/zotero -purgecaches?-safe? Output in the terminal doesn't matter if it's starting up properly.If you're able to start it in Troubleshooting Mode, you should disable all plugins manually and try starting normally.
Where do I access the Console? No windows are launching... Is there a subdirectory where the crash reports is found? Nevermind I found it
Will email the report to the address you mention tomorrow.
I sent the console crash report to the support email address with a link to this thread.