View Single Post
Old 09-06-2014, 08:55 PM   #628
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 Jellby View Post
When I connect the Aura through the Kobo Start Menu rather than through nickel, the database backup is stored as "KoboTouch" instead of "KoboAura". Is this something than can be fixed in the plugin? In KSM? Nowhere?
The name is what the driver gets based on the device id. It should be shown in the bottom left corner of the calibre window when the device is connected and displayed in the title of the driver configuration dialog. If that isn't happening, it might be something that KSM does, but I'm surprised that it changes the device id.

So that I can check, can you run calibre in debug mode, connect the device and post the debug log. That will show details of what the driver is seeing.
davidfor is offline