-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom Zotero location, still creating ~/Zotero
on every launch
#77
Comments
@anarcat, this is related to issues #65 and #73 and commit #75. What options do we have? I can think:
Any other? |
I don't know if it is related or it helps, but in my opinion the I don't know anything about flatseal, but I can wait if you plan to fix it sometime. Will just install a cronjob to delete this directory or so. |
@charlydelta , Zotero doesn't follow the XDG spec. If we make adjustments to enforce that ... previous installations would have problems (i tested this here - #74 - and gave up). Your problems could be solved by running: You also can do this using a GUI tool (Flatseal) and removing the configurations for But the question about the better setup for this Flatpak remains ... |
Just if anyone runs into the same problem, I needed to modify the posted command to get this to work
|
I have configured the Zotero data dir to a custom location
~/.zotero_data
, and I allowed it access to it viaflatpak override
. This works all fine, however, on every launch, the folder~/Zotero
gets created (empty) nonetheless... This is really annoying.I don't know whether this is an issue of Zotero or the flatpak, but it is new. Didn't had an issue like that before upgrading today.
The text was updated successfully, but these errors were encountered: