View Single Post
Old 10-28-2016, 08:45 PM   #2
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
It is most likely to be a configuration problem. The most common is missing the setting for the metadata management option. But the "Im_Reading" collection wouldn't show up if this was the case.

The next most common is the wrong column names in the collections column field of the driver configuration. That's usually forgetting the "#" for custom columns.

After that, it is configuring the wrong driver. If you are using the extended driver, make sure you configure that and not the KoboTouch driver.

If you post the driver configuration file, I can check what is in it. Depending on which driver you are using it is either "device_drivers_KOBOTOUCH.py" or "device_drivers_KOBOTOUCHEXTENDED.py' in the calibre configuration directory.

If that doesn't show anything, I need a debug log. This usually shows what is wrong. This is started by right-clicking on the preferences button and selecting "Restart in debug mode". When calibre restarts, connect the device, wait for the initial jobs to run and close calibre. The log will be displayed. Please post or PM the full log.
davidfor is offline   Reply With Quote