View Single Post
Old 09-24-2019, 09:25 PM   #95
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
(Should have read to the end of the thread before replying before)

Quote:
Originally Posted by perisiana View Post
I have 3 columns, current reading location, percent read and last read, set in the plugin for the Kobo h20, to work automatically when the device is connected.
But in automatic mode the columns remain empty, or the reading percentages are not modified, so I imagine that it doesn't work.
That should only happen if the you don't have it configured to get the percentage and put it in a column. Do you you have profiles for different devices that might be different?

Also, do you have it prompting before updating the library? The prompt will show what changes are to be made and might tell use where it is going wrong.
Quote:
If I start it manually (usually with all the kepubs I have on Kobo selected, around 3000), Calibre freezes and it takes a while to restart, and then it takes about a quarter of an hour to stores bookmarks, percentages etc, but works perfectly and all the data are correct.
There will appear to be a hang when starting as the plugin collects the information it needs to query the device. It shouldn't take more than a couple of minutes, but, that will depend on the computer. After that, if it is running as a job, calibre should be responsive.

If the configuration seems to be correct, I need to see a debug log to see what is happening. If you can restart calibre in debug mode, connect the device with the automatic fetch happening, close calibre when it finished and then post the log that calibre shows, I can look at what is actually happening.

And we should take this to the plugins thread. This isn't a firmware version issue.

Forgot something:

There is a change in the firmware that does affect this. The way the current location is stored for epubs has changed. But, this only affects getting the location. The percent read and last read date is still working. The location will be blank for this. I have a fix for this but, have not had time to test it properly as I need to make sure it still works with old firmware, and that the currently stored locations can be restored to the new firmware properly.

Last edited by davidfor; 09-24-2019 at 09:43 PM.
davidfor is offline   Reply With Quote