Open sxiii opened 8 months ago
Hi,
At this moment the only option for your case is probably to use v.0.43 - then you will able to use the native library for SQLite which has different handling of locked db files.
I will check if it is possible to add option to use alternatively this native library if user needs in v.0.46
same issue with 0.45.2 (build 16609) (Linux)
this version was working fine until, one day, it wasn't
regarding OP's steps to reproduce, that wasn't the case for me - i simply edited some text in an existing post
killed publii and electron processes, deleted the 'db.sqlite.lock' file and it worked again
related: #1393
@atomGit seems that's right, we can just delete or move file in the Publii dir, like this:
/Publii/sites/<yoursitename>/input/db.sqlite.lock
,
and then it works again with the recent version. Thanks for the hint!
Operating system
Garuda Linux Soaring Spizaetus
Publii version
Version: 0.45.2 (build 16609)
Post editor
None
Bug description
SQL3 error is back: "sql3 error database is locked".
I was going to make an important urgent update while that happened :(
Rebooted system (was hoping it would remove the lock), but it didn't helped.
Found other issue like this and tried older version Version: 0.44.4 (build 16557), but it didn't helped at all.
Also tried both AppImage versions (latest two) and repo-installed "aur/publii-bin" versions (Garuda Linux, which is almost Arch) - doesn't work with any of these 3.
Tried to find a DB file to check if it's locked and found out that it's archived inside app.asar file,
fuser /usr/lib/publii/app.asar/
returns nothing, so this file is not locked at least.Ready for any debug steps but would be cool if the data that I changed before commit could be saved (however, I'm even OK to loose it if it helps)
Steps to reproduce
Work in latest Publii version Edit a link to replace it with another link Get into this hanging app state randomly (gnome asks to kill the app) Killed the app (actually, it killed from the 3rd try or smth) Restarted and got this error that DB is occupied
Relevant log output