Thread: Glo [Glo HD] Strange files (parsed extention) in kobo-images directory
View Single Post
Old 10-01-2015, 08:57 PM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Nick_1964 View Post
The files are left behind, but I really don't know if the books are deleted by hand or by calibre but most of them are from June the days that I bought both readers.. They are left behind, the books are not on the reader,
And was June the last time you synced the device and received recommendations from Kobo? If so, the cover images are probably for those books
Quote:
but I only sideloaded by calibre and I only delete by the reader, so I don't add or delete books by using a filemanager, also the database is compressed almost 1.5 megabytes for just 6 books.. The plugin doesn't delete the files, some directory's are empty..
The firmware doesn't delete the empty directories when books or cover images are removed. Doing this from calibre will remove empty directories. And yes, a "clean device" function would be handy in the utilities plugin to remove empty directories and and run the image cleanup and annotations file removal in one go.
Quote:
It looks like calibre or the plug-in handles the recent books correctly, but leaves the old ones untouched...
The image cleaning scans the .kobo-images directory and removes all cover images that do not have a reference in the database. So, unless there is a bug in how that is done, "the old ones" are still being referred to. The question is how. The only other reason I can think of for them not being removed is if the files were set to read-only.
Quote:
So I delete them or do you want something as examples, then please tell me what you want me to do for your examination?
If you think there is an error, then I need examples before I can fix it. I will need a copy of the database plus the names and paths to the cover images that you think should have been removed. Either send me a PM with a location I can download them from, or I can send you an email address (though you might already have that).

If you want to check yourself, you can look in the database. If you have an SQLite database manager, you can open the database and the following SQL statement will check for the cover image you mentioned in the first post.

Code:
SELECT * 
FROM content
WHERE ImageID = 'FAkvhJeZMUqoRwrralLQQA'
The value in the quotes is the part of the file name before the dash.

If running the query returns a row, then there is a book on the device for the cover image and the image cleanup should not touch it. If it doesn't return a row, then the image cleanup should remove the file. If you run the cleanup and the file isn't removed, then there is a bug.
davidfor is offline   Reply With Quote