H2O Aura memory problem

[Elaxon]

I don't know why this happens but everytime I try to load a book and then reload it causes serious problems. For example in Calibre after a restart I get

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 87, in run
File "site-packages\calibre\gui2\device.py", line 503, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1787, in books
File "site-packages\calibre\devices\kobo\driver.py", line 1662, in get_bookshelvesforbook
DatabaseError: database disk image is malformed


and also if I try to plug it into the pc it doesn't turn the frontlight off either

Is this a corrupt memory card?

[davidfor]

The error in calibre means the database on the device is corrupt. The device will seem to be working, but it is running on an in memory copy of the database. It is unlikely to be able to write changes to the database and if you power off and on, it will lose any updates such as the reading positions or recently added books. If you don't have a backup of the database, the fix is to sign out of the Kobo account. This will replace the database with an empty one and load the books after prompting you to login. If this doesn't fix things, you might need to do a factory reset.

The light not going off is unrelated. A recent firmware change means that the light doesn't always get turned off when the PC is connected to the PC.

[tshering]

Originally Posted by davidfor

A recent firmware change means that the light doesn't always get turned off when the PC is connected to the PC.

I cannot say anything about this, but I think Elaxon's problem is KSM related.

@Elaxon
if the light was switched off the last time you exited nickel, and if you switch on the light in KSM and then start nickel, the light is on, but nickel does not know about it. In this situation you cannot change the brightness level via the nickel menu, nor does nickel switch the light off if you connect it to the PC or when it goes to sleep. I will try to take care of this.

@Elaxon
The corrupted database is possibly also related to KSM, because of your previous problem with starting nickel. When ever you launched nickel, nickel started to modify the datebase; because of an unlucky situation, fmon got fired and killed nickel. I am not sure of how things go exatly at that point, but I guess it can cause damage to the database.