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

Watch folder lost every (Qiqqa) restart, v80 #416

Open
SimonDedman opened this issue Jun 1, 2023 · 2 comments
Open

Watch folder lost every (Qiqqa) restart, v80 #416

SimonDedman opened this issue Jun 1, 2023 · 2 comments

Comments

@SimonDedman
Copy link

Hi Ger,

Just logging this for the sake of it kinda, but also means I can keep a log of version numbers and their issues for reference.
v80s: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again.
I'm running Qiqqa in a virtualmachine Windows10 which seems to work fine, with the library location on my linux (host) drive which is made available to the VM as a mapped network drive, always in the same place (Y:/). The mapped drive location seems to be available immediately on startup, but just in case I disabled running Qiqqa at startup but that changed nothing.

Versions and key issues
v83: crashes all the time with object error. does textify & OCR properly (quite well? not perfectly? never finishes?) though.
v82: white pages. textify & OCR issues.
v80s: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again. textify & OCR work perfectly. Everything else works.

Cheers, hope you're well!

@SimonDedman SimonDedman changed the title Watch folder lost ever (Qiqqa) restart, v80 Watch folder lost every (Qiqqa) restart, v80 Jun 1, 2023
@SimonDedman
Copy link
Author

Edit: thought: it says I have read-only access to the library which AFAIK isn't an issue since the database is separate? Notwithstanding I should have write access to the library since I can make write edits on things in that mapped drive within windows explorer etc.

@SimonDedman
Copy link
Author

sorry, already brought this up in this megathread, though my setup has changed since the original nightmares, and I'm now running win10 in a virtualmachine, with the watch folder being in a permanently mapped drive (Y:/Galway/Papers). Do you think the inability to save watch folders has anything to do with my only having read-only access to the library?

I suppose this could be a solved problem, but I'm using v80 due to worse issues with v82 & 83:

v83: crashes all the time with object error. does textify & OCR properly though.
v82: white pages. textify & OCR takes forever/fails.
v80: Loses Watch folder on restarts, even if not launched on boot, added, run, closed, reopened, watch folder gone again

(essentially a note to self!)
Cheers!

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

No branches or pull requests

1 participant