View Single Post
Old 01-11-2019, 07:20 PM   #8
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
Quote:
Originally Posted by Harzmounty View Post
Sorry,

back to normal workload, haven't had the time during the week.

I think you got it.

Metadata handling was set to [Manual management]. I changed that to [Automatic management], turned "Read matadata from files on device" in Aura driver back ON, transferred a book and didn't get an error.
The "Read metadata from files on device" option wasn't what I was talking about. It was "Update metadata on the device" and it options.
Quote:
So: problem solved, thank you.

Note: I haven't changed anything, the set up was OK for more than two years.
But it seems to be OK again, and that's perfect.
The code where the error happens, has recently been completely rewritten. Along with a reasonable amount of the rest of the driver. Unfortunately, finding an error with no configuration changes isn't that surprising. Though, I still haven't worked out how it reach the code in the state to trigger the error.
davidfor is offline   Reply With Quote