sqlite error "attempt to write a readonly database" when databse is not readonly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Mnemosyne Project |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I run Mnemosyne inside a syncthing container. Initially the setup was working fine, but after a few weeks of use I am getting errors often when I try to save or load the database.
```
Traceback (innermost last):
File "/usr/local/
__import_
File "/usr/lib/
self.
File "/usr/lib/
exec(code, namespace, namespace)
File "/usr/local/
mnemosyne.
File "/usr/local/
self.
File "/usr/local/
scheduled_
File "/usr/local/
scheduled_
File "/usr/local/
self._cursor = self.connection
sqlite3.
```
The database is not readonly, and when I try the operation again it normally works fine.
Is this just an inherent problem with running Mnemosyne inside syncthing or is it something that could be worked around or fixed?
I've not seen this before, so unless you can reproduce it outside of syncthing, I'm afraid there not much I can do about it...