View Single Post
Old 12-19-2022, 02:57 PM   #1191
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Quote:
Originally Posted by jasius View Post
When in Nickle and I upload a book it via usb using calibre it usually hangs when rebooting and updating it's database, with a hard reset it's fine in Nickel, but in KO Reader there will always be missing GUI elements that I need to do a dev to stable update to get it fixed. The desired new book does get added too, so it's merely annoying.

I have added the required line to ignore all the ui elements that Nickel picks up, but it still now has those elements in it's database, is there a quick way to remove those from it's database?
It's unclear to me whether this is actually a Nickel DB issue or simply a good old filesystem corruption one .

If the ignore directives takes, nothing makes it to the DB *at all*, so I'd be inclined to vote for "FS corruption" .

(As for why KOReader and not Nickel: KOReader lives in the onboard, USBMS partition: that's FAT32, which is not journalled, and notoriously terrible at recovering from system faults. Nickel, on the other hand, lives in the rootfs, which uses a sane journalled Linux fs).
NiLuJe is offline   Reply With Quote