Skip to content
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

Closed
charlydelta opened this issue Dec 14, 2020 · 4 comments · Fixed by #86
Closed

Custom Zotero location, still creating ~/Zotero on every launch #77

charlydelta opened this issue Dec 14, 2020 · 4 comments · Fixed by #86

Comments

@charlydelta
Copy link

I have configured the Zotero data dir to a custom location ~/.zotero_data, and I allowed it access to it via flatpak 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.

@felipehw
Copy link
Collaborator

@anarcat, this is related to issues #65 and #73 and commit #75.

What options do we have? I can think:

  1. @charlydelta could just use Flatseal to remove the :create of filesystem accesses for ~/Zotero and ~/.zotero.
  2. we could revert the restriction for Zotero Flatpak access the home dir.

Any other?

@charlydelta
Copy link
Author

I don't know if it is related or it helps, but in my opinion the Zotero folder should be in the documents directory, and the ~/.zotero in an XDG conform directory like ~/.local/share or whatever...

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.

@felipehw
Copy link
Collaborator

felipehw commented Dec 14, 2020

@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: flatpak override --user --filesystem=home --filesystem=~/.zotero:rw --filesystem=~/Zotero:rw org.zotero.Zotero.

You also can do this using a GUI tool (Flatseal) and removing the configurations for ~/.zotero ~/Zotero and giving access to home.

But the question about the better setup for this Flatpak remains ...

@lschmelzeisen
Copy link

Just if anyone runs into the same problem, I needed to modify the posted command to get this to work

flatpak override --user --filesystem /path/where/you/want/Zotero --nofilesystem ~/Zotero org.zotero.Zotero

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants