Kobo Start Menu - Page 57

Ebri · 02-01-2015, 02:45 AM

It seems logging out deleted the contents of the .kobo directory, including sub-directories. So after logging out, KSM scripts are deleted. I prefer using backups (but I agree, sometimes it doesn't work, but in this case it is better to copy the additions of .kobo folder and then copy them back, though I haven't tried whether it works).

NiLuJe · 02-01-2015, 07:16 AM

@Ebri: Yup, I can confirm that, which is why I promptly moved my custom stuff out of .kobo

.

tshering · 02-01-2015, 07:34 AM

Quote:

Originally Posted by Ebri

It seems logging out deleted the contents of the .kobo directory, including sub-directories. So after logging out, KSM scripts are deleted. I prefer using backups (but I agree, sometimes it doesn't work, but in this case it is better to copy the additions of .kobo folder and then copy them back, though I haven't tried whether it works).

As I mentioned in one of the previous posts I never logged out/in. Since I never sync with the Kobo server it would not make much sense in my case.
If logging out/in deleted all the contents of .kobo, that would mean that they/one had to restore afterwards all the dictionaries, pocket articles, configuration files. If this is the intended behaviour it strikes me somehow ... (Edit: After a second thought, I have to admit that this makes sense. Singing out is not primarily intended as a means to repair the database, after all.) Or are they preserving some contents and delete the rest?

booklover6 · 02-01-2015, 07:35 AM

So my Aura, which I thought was fine, got corrupt again. All I did was connect it to Calibre and load 1 small file. (Although apparently I left wifi on over night). So once again, I am waiting for it to finish processing after log out/log in. KSM will not start, clicking the image just brings up the image, although the files are still in .kobo, and after a restart, KSM starts. But Calibre said the DB was corrupt. So maybe switching back and forth between Nickel and KoReader is not such a good idea? I think I'll just stick with Nickel.

boriar · 02-01-2015, 07:50 AM

Quote:

Originally Posted by Ebri

It seems logging out deleted the contents of the .kobo directory, including sub-directories. So after logging out, KSM scripts are deleted. I prefer using backups (but I agree, sometimes it doesn't work, but in this case it is better to copy the additions of .kobo folder and then copy them back, though I haven't tried whether it works).

Said you login from your ereader with wifi or sync through PC (connected with wire)?

Ken Maltby · 02-01-2015, 08:32 AM

Quote:

Originally Posted by booklover6

So my Aura, which I thought was fine, got corrupt again. All I did was connect it to Calibre and load 1 small file. (Although apparently I left wifi on over night). So once again, I am waiting for it to finish processing after log out/log in. KSM will not start, clicking the image just brings up the image, although the files are still in .kobo, and after a restart, KSM starts. But Calibre said the DB was corrupt. So maybe switching back and forth between Nickel and KoReader is not such a good idea? I think I'll just stick with Nickel.

Logging out of your Kobo Account on your device will remove the database entries and rebuild the database. fmon (File Monitor) works by detecting when specified files are properly accessed by Nickel (Nickel uses the database to interact with the files) the rebuilding of the database does not include rebuilding the database entries for the Icon/png files for fmon's use.
You should not expect to be able to use those .png files to do any actions until they are reprocessed back into the database.

Luck;
Ken

tshering · 02-01-2015, 09:01 AM

@booklover6

It seems we are turning in a circle. Logging out/in to restore the database > nickel reads the KSM pngs newly into the database, but does not create all thumbnails > next time you start nickel it wants to create one or several of the thumbnails, for that purpose nickel opens a KSM png > this triggers fmon which shuts nickel down > somehow on the way the database gets corrupted > you log out/in > ...

Let us therefore try something different.

download the archive from this post, extract start_nickel_test_no_fmon.sh and copy it to .kobo\kbmenu\scripts.
start nickel by selecting in KSM "scripts" > "start nickel test no fmon.sh"
if your database is currently corrupted, log out/in to repair your database
play a little around with the library and the tiles on the home screen so that it is likely that nickel produces all the necessary thumbnails of the ksm pngs.
powering off the reader by using the power slider
power on and start nickel as in step 2 ("scripts" > "start nickel test no fmon.sh")
do your things with calibre (if there is some need for it)
make a backup of your database (in case the database gets corrupted again, you can just use the backed up, instead of logging out/in)
next time you start nickel from KSM regularly ("start nickel") everything should work as expected; from this point you can again use exit_nickel.png to return to KSM

booklover6 · 02-03-2015, 09:08 AM

@tshering

Would it not be easier and cleaner just to factory reset and start the KSM installation from scratch?

Is it recommended that one not switch often between Nickel and KoReader?

Ken Maltby · 02-03-2015, 11:56 AM

I seldom have reason to use Nickel and do not make use of the scripts to switch directly from one to the other. But I have no problem exiting to KSM to call up either one. I am having no trouble using the "Exit" icon in Nickel to return to KSM, but if I did, it is no real problem to use the powerslide and power off and back on, into KSM. Koreader exits to KSM smoothly.

Luck;
Ken

tshering · 02-03-2015, 02:59 PM

Quote:

Originally Posted by booklover6

@tshering
Would it not be easier and cleaner just to factory reset and start the KSM installation from scratch?

I am not sure whether this would be easier. For now you could follow only the first two steps of my above description. This will allow you to use nickel without any side effects from KSM, and you can take steps to get your database repaired. You would have to exit nickel by powering off with the power slider. One other thing: If you connect to the PC in order to load books you intend to read with nickel, you should connect from within nickel. But I guess you do so already.
Maybe it is not a good moment to reinstall KSM now. I will publish a new version one of this days.

Quote:

Originally Posted by booklover6

Is it recommended that one not switch often between Nickel and KoReader?

If you mean switching directly between the two applications without passing through the KSM menu, I have not much experience with this myself. I was once asked to add this option, and therefore I did it. Of course, I tested it a bit, but since I personally have not use for it ... I even do not know whether other people use it often and how it works for them. There was not much feedback.

booklover6 · 02-03-2015, 03:45 PM

Quote:

Originally Posted by tshering

I am not sure whether this would be easier. For now you could follow only the first two steps of my above description. This will allow you to use nickel without any side effects from KSM, and you can take steps to get your database repaired. You would have to exit nickel by powering off with the power slider.

The DB on my Aura is currently fine, after the last log out/in. I haven't tried to put KSM back on it. Still debating whether I should try again. I installed KSM and KoReader on my Mini today, with no issues whatsoever.

Quote:

Originally Posted by tshering

One other thing: If you connect to the PC in order to load books you intend to read with nickel, you should connect from within nickel. But I guess you do so already.

I see why. I loaded one through KoReader today and it doesn't show up in Nickel. So that must be a good way to keep Nickel from "processing" new books.

Quote:

Originally Posted by tshering

If you mean switching directly between the two applications without passing through the KSM menu,

No, I was not talking about doing it while bypassing KSM. Just if there are any reasons why one should not use both Nickel and KoReader.

tshering · 02-03-2015, 05:12 PM

Quote:

Originally Posted by booklover6

The DB on my Aura is currently fine, after the last log out/in. I haven't tried to put KSM back on it. Still debating whether I should try again. I installed KSM and KoReader on my Mini today, with no issues whatsoever.

Do you treat the Mini in the same way as the Aura (loading books with calibre, only put to sleep and never power off, or similar things)?

Quote:

Originally Posted by booklover6

I see why. I loaded one through KoReader today and it doesn't show up in Nickel. So that must be a good way to keep Nickel from "processing" new books.

This might work only temporarily, for instance up to the next log out/in.

Quote:

Originally Posted by booklover6

No, I was not talking about doing it while bypassing KSM. Just if there are any reasons why one should not use both Nickel and KoReader.

I use both without any issues.

booklover6 · 02-03-2015, 06:04 PM

Quote:

Originally Posted by tshering

Do you treat the Mini in the same way as the Aura (loading books with calibre, only put to sleep and never power off, or similar things)?

Yes, I use them the same, and mostly have the same books on them both. But there are some hardware differences between the Aura and all the other Kobo readers. So maybe that accounts for my issues.

ETA - I factory reset the Aura, (which updated to 3.12.1), then installed KSM, the update, KoReader, and lots of books. Everything seems to be working just fine, now! (I didn't install any patch or load any books via Nickel. I intend to use this device strictly with KoReader).

Hio · 02-04-2015, 10:33 PM

Hi, Thank you all for your file organization suggestions...
What i ended up doing was simply relabeling in calibre each book with a specific 'author sort' in the metadata.. and that mostly organised everything nicely..

Though after doing that and reloading all the books onto my kobo, nickel has now lost most of the content, recognising about half of the books actually on there, and when i try connecting the kobo to calibre, calibre wont read the kobo, and most of the time i get an error like this:

calibre, version 2.15.0
ERROR: Error: Error communicating with device

database disk image is malformed

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 1752, in books
DatabaseError: database disk image is malformed

any thoughts on how to fix this or what happened?

thank you!

PeterT · 02-04-2015, 10:48 PM

Database corruption on the Kobo.

Unless you have a backup copy, your only option is to force the device to rebuild the database. Just go to Settings | Accounts and perform a Logout from the Kobo account.

This will cause Kobo to delete the database, and then upon reboot you will have to go through device setup again.

Sideloaded books will remain on the device, and will be reprocess when the setup is completed.

02-01-2015, 09:01 AM	#847
tshering Wizard Posts: 3,489 Karma: 2914715 Join Date: Jun 2012 Device: kobo touch	@booklover6 It seems we are turning in a circle. Logging out/in to restore the database > nickel reads the KSM pngs newly into the database, but does not create all thumbnails > next time you start nickel it wants to create one or several of the thumbnails, for that purpose nickel opens a KSM png > this triggers fmon which shuts nickel down > somehow on the way the database gets corrupted > you log out/in > ... Let us therefore try something different. download the archive from this post, extract start_nickel_test_no_fmon.sh and copy it to .kobo\kbmenu\scripts. start nickel by selecting in KSM "scripts" > "start nickel test no fmon.sh" if your database is currently corrupted, log out/in to repair your database play a little around with the library and the tiles on the home screen so that it is likely that nickel produces all the necessary thumbnails of the ksm pngs. powering off the reader by using the power slider power on and start nickel as in step 2 ("scripts" > "start nickel test no fmon.sh") do your things with calibre (if there is some need for it) make a backup of your database (in case the database gets corrupted again, you can just use the backed up, instead of logging out/in) next time you start nickel from KSM regularly ("start nickel") everything should work as expected; from this point you can again use exit_nickel.png to return to KSM

02-04-2015, 10:33 PM	#854
Hio Member Posts: 15 Karma: 10 Join Date: Jan 2015 Device: kobo aura	Hi, Thank you all for your file organization suggestions... What i ended up doing was simply relabeling in calibre each book with a specific 'author sort' in the metadata.. and that mostly organised everything nicely.. Though after doing that and reloading all the books onto my kobo, nickel has now lost most of the content, recognising about half of the books actually on there, and when i try connecting the kobo to calibre, calibre wont read the kobo, and most of the time i get an error like this: calibre, version 2.15.0 ERROR: Error: Error communicating with device database disk image is malformed 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 1752, in books DatabaseError: database disk image is malformed any thoughts on how to fix this or what happened? thank you! Last edited by Hio; 02-04-2015 at 10:36 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
kobo menu and message	tshering	Kobo Developer's Corner	26	01-15-2014 09:18 AM
Kobo WiFi - Battery indicator outside menu?	Cyberman tM	Kobo Reader	1	03-06-2013 04:42 AM
Kobo constantly crashes back to Reading menu	avalanches	Kobo Reader	0	04-11-2011 09:35 PM
main menu, section menu, css for calibre mobipocket output	naisren	Calibre	2	08-23-2010 11:42 PM
Calibre start menu icon	Cy1clown	Calibre	1	02-06-2010 02:10 PM

02-01-2015, 02:45 AM	#841
Ebri Groupie Posts: 150 Karma: 48 Join Date: Apr 2014 Device: Kindle Paperwhite 2, Kobo Aura HD	It seems logging out deleted the contents of the .kobo directory, including sub-directories. So after logging out, KSM scripts are deleted. I prefer using backups (but I agree, sometimes it doesn't work, but in this case it is better to copy the additions of .kobo folder and then copy them back, though I haven't tried whether it works).

02-01-2015, 07:16 AM	#842
NiLuJe BLAM! 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	@Ebri: Yup, I can confirm that, which is why I promptly moved my custom stuff out of .kobo .

02-01-2015, 07:35 AM	#844
booklover6 Grand Sorcerer Posts: 6,545 Karma: 14008730 Join Date: May 2008 Location: PA (USA) Device: Kobo Clara, 2E, Libre 1, PW4, PW5, 2022 Kindle, Kobo Libre Colour	So my Aura, which I thought was fine, got corrupt again. All I did was connect it to Calibre and load 1 small file. (Although apparently I left wifi on over night). So once again, I am waiting for it to finish processing after log out/log in. KSM will not start, clicking the image just brings up the image, although the files are still in .kobo, and after a restart, KSM starts. But Calibre said the DB was corrupt. So maybe switching back and forth between Nickel and KoReader is not such a good idea? I think I'll just stick with Nickel.

02-03-2015, 09:08 AM	#848
booklover6 Grand Sorcerer Posts: 6,545 Karma: 14008730 Join Date: May 2008 Location: PA (USA) Device: Kobo Clara, 2E, Libre 1, PW4, PW5, 2022 Kindle, Kobo Libre Colour	@tshering Would it not be easier and cleaner just to factory reset and start the KSM installation from scratch? Is it recommended that one not switch often between Nickel and KoReader?

02-03-2015, 11:56 AM	#849
Ken Maltby Wizard Posts: 4,466 Karma: 6900052 Join Date: Dec 2009 Location: The Heart of Texas Device: Boox Note2, AuraHD, PDA,	I seldom have reason to use Nickel and do not make use of the scripts to switch directly from one to the other. But I have no problem exiting to KSM to call up either one. I am having no trouble using the "Exit" icon in Nickel to return to KSM, but if I did, it is no real problem to use the powerslide and power off and back on, into KSM. Koreader exits to KSM smoothly. Luck; Ken

02-04-2015, 10:48 PM	#855
PeterT Grand Sorcerer Posts: 13,534 Karma: 78910202 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Database corruption on the Kobo. Unless you have a backup copy, your only option is to force the device to rebuild the database. Just go to Settings \| Accounts and perform a Logout from the Kobo account. This will cause Kobo to delete the database, and then upon reboot you will have to go through device setup again. Sideloaded books will remain on the device, and will be reprocess when the setup is completed.

Advert

Advert