XPCOMGlueLoad error when starting Zotero 5.0.81
Hi all,
After updating Zotero from 5.0.77 to 5.0.81 on Ubuntu 19.04, I'm getting the following error when starting Zotero:
XPCOMGlueLoad error for file /usr/lib/zotero/libxul.so:
/usr/lib/zotero/libxul.so: undefined symbol: _ZN7mozilla11SandboxInfo14ThreadingCheckEv
Couldn't load XPCOM.
Any thoughts ?
Thanks in advance !
After updating Zotero from 5.0.77 to 5.0.81 on Ubuntu 19.04, I'm getting the following error when starting Zotero:
XPCOMGlueLoad error for file /usr/lib/zotero/libxul.so:
/usr/lib/zotero/libxul.so: undefined symbol: _ZN7mozilla11SandboxInfo14ThreadingCheckEv
Couldn't load XPCOM.
Any thoughts ?
Thanks in advance !
FWIW, I'm using @emilianoeheyns ' package, and already have reported downstream here: https://github.com/retorquere/zotero-deb/issues/21
Emiliano thought that the problem was unrelated to his packaging, so here I am.
> the extracted directory, does the same thing happen?
No, it doesn't: the program from the tarball starts just fine !
sudo apt remove zotero
sudo apt install zotero
I'd be surprised if the uninstalling was incomplete. I might want to ask Emiliano on Github.
It could also be a permissions issue. I'll see if I can replicate it.
`apt remove` already removes the whole /usr/lib/zotero directory, but in order to be sure, I 1) installed Emiliano's package again ; 2) did `apt purge` ; 3) tried to start Zotero. I got the same error.
And yes, it does prevent Zotero from starting at all.
I'm on x86_64. /proc/cpuinfo gives twice:
model name : Intel(R) Pentium(R) CPU G2030 @ 3.00GHz
@emilianoeheyns, don't hesitate to ask for anything else that could help
Can you start Zotero with
/usr/lib/zotero/zotero -ZoteroDebugText > ~/zotero.log 2>&1 &
and see if there's anything informative in zotero.log besides the XPCOMGlueLoad error? From what I can gather, XPCOMGlueLoad error just means "I did an oopsie" but is in itself unspecific on what went wrong; on _ZN7mozilla11SandboxInfo14ThreadingCheckEv I can't find anything at all.
diff -qr Zotero_linux-x86_64 /usr/lib/zotero
For me it yields
Only in /usr/lib/zotero/defaults: pref
Only in /usr/lib/zotero: mozilla.cfg
Only in Zotero_linux-x86_64: zotero.desktop
sudo chown -R root:root Zotero_linux-x86_64
, does Zotero still start from that unpacked tarball?Now that we know it starts well on a fresh ubuntu 19.04, I gave it another try on my laptop, which also happens to be running Ubuntu 19.04. I had no problem starting Zotero on that machine.
So the problem seems to be somewhat related to the state of my system, although I have no idea how exactly, neither do I recall altering it in any particular way.
On the `problematic` machine, `LANG=C diff -qr Zotero_linux-x86_64 /usr/lib/zotero` gives
Only in /usr/lib/zotero/defaults: pref
Only in Zotero_linux-x86_64/fonts: .uuid
Files Zotero_linux-x86_64/libxul.so and /usr/lib/zotero/libxul.so differ
Only in /usr/lib/zotero: mozilla.cfg
Only in Zotero_linux-x86_64: zotero.desktop
Files Zotero_linux-x86_64/zotero.jar and /usr/lib/zotero/zotero.jar differ
Finally: after `sudo chown -R root:root Zotero_linux-x86_64`, Zotero still starts from the unpacked tarball.
This is strange
These are very strange and this should absolutely not be possible.
Here's what I have: (I removed & reinstalled both zotero)
ls -lt |head
-rw-rw-r-- 1 ngirard ngirard 60167808 janv. 20 09:50 Zotero-5.0.81_linux-x86_64.tar.bz2
tar xjf Zotero-5.0.81_linux-x86_64.tar.bz2
dpkg -l | grep zotero
ii unity-scope-zotero 0.1+13.10.20130723-0ubuntu1 all Zotero scope for Unity
ii zotero 5.0.81 amd64 Zotero is a free, easy-to-use tool to help you collect, organize, cite, and share research
LANG=C diff -qr Zotero_linux-x86_64 /usr/lib/zotero
Only in /usr/lib/zotero/defaults: pref
Files Zotero_linux-x86_64/libxul.so and /usr/lib/zotero/libxul.so differ
Only in /usr/lib/zotero: mozilla.cfg
Only in Zotero_linux-x86_64: zotero.desktop
Files Zotero_linux-x86_64/zotero.jar and /usr/lib/zotero/zotero.jar differ
You have the "global menu" version! Uninstall Zotero, remove
/etc/apt/sources.list.d/zotero.list
, and reinstall.I can see you also posted on Github, I'll keep the discussion going on Github from now on ; but that won't be until tonight, unfortunately.
Dan, Emiliano: thanks to both of you for your time & assistance on this problem !