Zotero 5 and rpm (RedHat) based distributions
I recently downloaded Zotero 5 for use on CentOS 7. It did not successfully run. What are the prerequisites for Zotero 5 in terms of other programs and libraries?
In addition, having Zotero 5 in rpm format and hosted on a repo for CentOS and Fedora would be VERY nice.
Has anyone else had success with Zotero 5.x working on either Fedora or CentOS or any other Linux distribution other than Ubuntu?
In addition, having Zotero 5 in rpm format and hosted on a repo for CentOS and Fedora would be VERY nice.
Has anyone else had success with Zotero 5.x working on either Fedora or CentOS or any other Linux distribution other than Ubuntu?
I don't remember reports from Zotero 5, but Zotero 4 definitely ran on Fedora and ArchLinux and the requirements shouldn't have changed.
Zotero is unlikely to package for specific distros (they don't produce a .deb either) so that'd have to come from someone else.
When running from terminal as regular user in CentOS 7
./zotero
I receive, get ready for it... and so on. Two black windows open, but nothing else. Yet when I run as super user it works. I do have SELinux enforcing. Do I need to add an exception?
Although, we running as super user, i.e.
sudo ./zotero
I still get an error as follows, but the program runs. Suggestions?sudo setenforce 0
I still get errors as in the fist pre-formatted test box in the previous reply../zotero --jsconsole
gives me the following: And then hangs.Also, some time afterwords, the following was spit out... Ideally though, an RPM and distro specific packaging would be very nice :)
bash zotero
./zotero -v
Zotero Zotero 5.0.27, Copyright (c) 2006-2017 Contributors
_initDB<@chrome://zotero/content/xpcom/zotero.js:894:9
Current java version 1.8.0_144-b01 64bit
1.8.0_151-b12
Any movement on this @adamsmith and @dstillman
It works again with elevated user rights.
Try to submit a Debug ID for a startup that fails:
https://www.zotero.org/support/reporting_problems#reporting_startup_errors
Or if that doesn't work, use -jsconsole, not --jsconsole, to view the Error Console. The messages in the terminal are unlikely to matter.