Calibre force close

[stanlefor]

hi,
this morning I pluged my kobo aura hd to add a few books, and calibre closes!
Everytime I try to plug the reader, calibre just closes...
I'm on latest calibre and kobo firmware.
Any idea?
Thanks

[stanlefor]

Well...

Not that much help!

I did reinstall the 3.12 firmware on my aura hd, and the problem is still there. So it's really a calibre problem.
But how should I fix it...

[kovidgoyal]

I dont recall if the HD is an MTP device, is it? Does it show up as a drive in windows explorer or as a Media Player?

[stanlefor]

It shows as a drive, so it's not MTP.

Looks like it's a driver issue to me. Maybe a procedure to reset the calibre driver?

thanks

[kovidgoyal]

There is no driver for non-MTP devices, all calibre uses is standard file system access. In fact I can't think of any calibre code that could possibly crash with a non-MTP device.

The only exception is reading metadata from files. It maybe that there is a corrupted epub or pdf file on the device that is causing the crash. You can test that by disabling the metadata reading plugins for epub and pdf in Preferences->Plugins in calibre.

[stanlefor]

Disabled those plugins and still the crash :s

EDIT :
Ok, deleted metadata.calibre, driveinfo.calibre and all books, and still doesn't work!

[kovidgoyal]

Then I'm out of ideas, sorry.

[davidfor]

@stanlefor: Sorry, I missed this one last night.

The Kobo Aura HD is accessed with the KoboTouch driver. Assuming you haven't installed the extended driver. If you have installed the extended driver, please disable it and retest.

The questions and suggestions I can think of are:

- Is this new behaviour? Has it worked in the past and this has just started? Or is it a new device and it is the first use?
- After calibre closes, can you access the device? That is browse its drive or copy a file to it.
- If you don't have calibre running, can you access the drive when it is first connected?
- When the device is connected, calibre runs three jobs. Which one gets run?
- As well as what Kovid suggests, change the metadata management to manual. This is on the "Sending books to devices" page. That cuts out on of the connection startup jobs. It is also the one that is most likely to have problems.
- What OS?
- As you didn't say anything about them, I assume there were no error messages.
- Is the device working OK? If you power off and on do you lose books or the reading status of books?

Running calibre in debug mode might also tell us something. Usually I recommend restarting in debug mode, connecting the device and waiting for the jobs to finish. Then closing calibre and the debug log is displayed. But, I'm not sure if that will happen in this case. Calibre will display the full path for the debug log when it restarts, you should take note of this to find it after calibre closes. The full debug log will tell me a lot about what is happening.

[stanlefor]

ok, I did a full reset and now it works, so sorry about doing that before investigating more.
I guess it was a device error then!

to answer david :
- no extended driver
- It's a new behaviour, the calibre/reader used to works well
- I could access the drive after calibre close
- can't know the jobs calibre was doing : didn't watched that
- os is windows 7 x86
- no error messages
- device was working ok

To finish, I did install KSM and uninstalled it : maybe it comes from there.

Thanks guys

[davidfor]

A factory reset fixed it? Good. That would have been my suggestion if the debugging didn't show anything useful. I'm curious about what caused this, but the important thing is you can read your books.