View Single Post
Old 08-11-2018, 07:53 PM   #1
Rellwood
Library Breeder (She/Her)
Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.Rellwood ought to be getting tired of karma fortunes by now.
 
Rellwood's Avatar
 
Posts: 1,279
Karma: 1937891
Join Date: Apr 2015
Location: Fullerton, California
Device: Paperwhite 2015 (2), PW 2024 (12 GEN), PW 2023 (11 GEN), Scribe (1st)
unable to debug "read only database"

I had moved my libraries to Dropbox some time ago, and hadn't come across this problem. Like the title reads, I can't restart in debug mode because the database is read only.

I went into the permissions on all the parent folders and made sure they were ok for everyone (ie. users, other users, system, etc.). Then I went into the folders to the db file as well as the .json file and confirmed they were ok to write on.

So what gives?

We all know that the general folders holding libraries all have the grayed out read only box, but that never was a problem. Even still I made sure to apply the write settings to the entire folder. This didn't last as it immediately reverted back.

Any suggestions?
Rellwood is offline   Reply With Quote