Quote:
Originally Posted by Majutsushi
Do you have the "store on connect" option enabled for the relevant profile? If yes and it's still not working then it would be really helpful if you could create a debug log of the situation. I'm not sure why any of the relevant options could have gotten deselected, nothing should have changed there.
|
Yes, I have that selected in the relevant profile (which is the only 'default' profile that I have).
Please see attached log files both for the rolled back 2.23 and current 2.24.1 versions.
I'm running Windows 11 Pro Version 10.0.26100 Build 26100
I notice the log refers to this as Windows '10' but I assume this is quite possibly me misreading the log.
For each of these logs all I did was:
restart in debug mode.
Connect Kobo
Wait for it to finish all jobs.
Eject Kobo via Windows 'safely remove hardware'
Shut Calibre.
One thing to add is that when connecting (before, outside of debug mode), progress seems to be the only thing not working. Other actions like backing up the Kobo database seem to be working fine, as well as recognising which books are on device.
Hopefully this helps you find what the issue is, but let me know if there is anything else I can do to help.
**ETA**
After the above, I also added a book to Calibre and transferred to Kobo to test that. For the book I included series info and added it to a collection (one that did not exist on Kobo yet).
First time I did it, after ejecting and disconnecting the Kobo, this caused the Kobo to immediately move into reboot and prompt me to register from the start.
After doing so, I reconnected to the computer (without Calibre active) and moved the back up database files over to Kobo. The database did not appear to have saved any of my recent reading progress since the last time that I manually saved the progress (which I have done once since this issue occurred). I then started Calibre and connected the Kobo. The most recent book that I had transferred was showing as present on the Kobo, so deleted that and did the transfer process again from start, which then worked fine without issue. So the 'crash' may have been a coincidence (have certainly had some, but not many, of those in the past). Sorry, no log file for any of this as was done outside of debug mode.