View Single Post
Old 02-14-2018, 06:39 PM   #7
CRussel
(he/him/his)
CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.CRussel ought to be getting tired of karma fortunes by now.
 
CRussel's Avatar
 
Posts: 12,298
Karma: 80074820
Join Date: Jul 2010
Location: Sunshine Coast, BC
Device: Oasis (Gen3),Paperwhite (Gen10), Voyage, Paperwhite(orig), iPad Air M3
In a windows environment, one can end up with this issue on a clean install with the Calibre folder attached at the root of a drive. (ie, d:\calibre as the database) This is because, by default, Windows makes non-adminstrators have read-only access to the root of the drive, and calibre runs (as it _should_) without elevating privilege.

I ran into this recently when I virtualized the server that was hosting my calibre database, and forgot to reset the permissions. Duh.

Result? A complaint about a corrupted database. Sigh. Once I changed the permissions to give 'users' write permission, all was well.
CRussel is offline   Reply With Quote