Quote:
Originally Posted by macnoodle
This seems to be a widespread issue, and I have seen posts from people with *exactly the same problem that I have, but none of the things that have so far been suggested worked for me, so I thought I’d post this as a thread of its own. The error message that pops up in Calibre is very specific, so I hope that someone with coding experience can point me in the right direction. Here is my sad story:
My brand-new Kindle Paperwhite Signature Edition is not being detected by Calibre, no matter what I try (different cables, different USB ports, nothing works). I’m using the latest version of Calibre with the latest version of MacOS, on a MacBook Pro M1 Pro (Apple Silicon). Resetting the Kindle to factory defaults works, but only temporarily, and of course it wipes any downloaded and sideloaded content from the Kindle in the process. After a factory reset Calibre will detect the Kindle exactly once, then never again! I suspect this has something to do with Amazon cracking down on DRM removal. This is what Calibre reports when the Kindle is disconnected (it is only “detected“ by Calibre upon disconnecting):
Failed to get storage info for device.
Traceback (most recent call last):
File "calibre/gui2/device.py", line 112, in run
File "calibre/gui2/device.py", line 532, in _get_device_information
File "calibre/devices/mtp/base.py"
, line 24, in synchronizer
File "calibre/devices/mtp/unix/driver.py", line 358, in free_space libmtp.MTPError: Failed to get storage info for device.
I’m not sure what to do with that or if it can be patched in a future Kindle firmware update or a Calibre software update, but a Kindle (or any other e-reader) that won’t talk to Calibre is of no use to me, so my new Kindle Paperwhite Signature Edition will be going back to Amazon. It is a real shame - I really like the new screen and the device overall, but Amazon’s greed is ultimately going to cost them in the long run. I would have happily bought the Matcha basic Kindle in addition to this new Kindle Paperwhite Signature Edition, but instead I’ll be returning it for a refund if a solution cannot be found before the return window closes.
|
This is the problem I've been having as well. As the OP emphasises in that thread, neither he nor I have any other MTP app or programme open when we connect to Calibre. I have had more luck than him getting my device to connect to Calibre, but it is definitely hit-and-miss, and when it does connect it takes minutes rather than seconds as it should. Maybe I have a defective device as well.