Thread: Beta testers for calibre 2.0 needed
View Single Post
Old 08-17-2014, 03:49 AM   #129
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 kovidgoyal View Post
The problem happens in metadata_downloaded(), because of the error, the device_metadata_available signal is never emitted. Most device drivers dont use this signal, presumably the kobo one does.
The driver doesn't, but my Kobo Utilities does. So do the Reading List and Kindle Collections plugins. Not getting the signal makes sense with the earlier error. But, what I couldn't see was why only the Kobo devices where getting that error when the device was connected.
davidfor is offline   Reply With Quote