Calibre 5.33 Not Correctly Reading Metadata on Kindle Fire HD

watani · 12-04-2021, 01:20 AM

After updating to Calibre 5.33, I was surprised to find that Calibre detected no books on my Kindle Fire HD 8 (7th gen). Books that I'd previously loaded onto the device with Calibre 5.32 were all still on the device and readable, but Calibre 5.33 did not detect any of them.

Upon sending a few new books to the device, disconnecting it, and then reconnecting it, I determined that Calibre 5.33 also did not detect any of the books that were just uploaded prior to the reconnection.

Calibre 5.33 also does an extra scan for metadata in the documents folder on the device that added an extra two minutes on top of the normal scan time (about 2.5 minutes normally).

Downgrading to Calibre 5.32 resulted in Calibre only detecting books that were uploaded in the final connected session with 5.33, but after "reuploading" all the books that were on the device subsequent device connections all correctly detect all existing books on the device.

kovidgoyal · 12-04-2021, 01:50 AM

there werent any changes to the kindle driver in 5.33. Try running in debug mode and post the log (right clickthe preferences button and choose restart in debug mode).

watani · 12-04-2021, 08:10 AM

I just updated from 5.32 to 5.33.2 and was unable to reproduce the bug anymore. I was previously using 5.33.0 when the bug occurred, so either it was fixed since then or something corrupted my Calibre install. I'm leaning towards the latter because when I updated to 5.33.0 the installer gave a warning that another install was ongoing and the install had to be rolled back, but after the progress bar showed the rolling back finished, the update still progressed and eventually completed. I'd been using Calibre after the update and didn't see any issues until I connected my device so I didn't think much of the weirdness, but in hindsight something probably went wrong.

kovidgoyal · 12-04-2021, 09:30 PM

No, it was a bug in 5.33.0 caused by an unrelated change preparing calibre for python 3.10 this had an undocumented side effect that broke the mtp driver on windows 64bit only.

12-04-2021, 01:20 AM	#1
watani Connoisseur Posts: 51 Karma: 10 Join Date: Oct 2014 Device: Kindle Fire HD	Calibre 5.33 Not Correctly Reading Metadata on Kindle Fire HD After updating to Calibre 5.33, I was surprised to find that Calibre detected no books on my Kindle Fire HD 8 (7th gen). Books that I'd previously loaded onto the device with Calibre 5.32 were all still on the device and readable, but Calibre 5.33 did not detect any of them. Upon sending a few new books to the device, disconnecting it, and then reconnecting it, I determined that Calibre 5.33 also did not detect any of the books that were just uploaded prior to the reconnection. Calibre 5.33 also does an extra scan for metadata in the documents folder on the device that added an extra two minutes on top of the normal scan time (about 2.5 minutes normally). Downgrading to Calibre 5.32 resulted in Calibre only detecting books that were uploaded in the final connected session with 5.33, but after "reuploading" all the books that were on the device subsequent device connections all correctly detect all existing books on the device.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre sent AZW3 not showing correctly on Kindle.	Josieb1	Calibre	16	01-09-2021 08:23 AM
Can I stop Calibre while it is reading my Kindle Fire?	MrJamesEMcBride	Devices	17	09-09-2019 06:41 AM
Image displays correctly on Kindle Fire but not Kindle Paperwhite	Cepheus	Kindle Formats	0	03-27-2019 03:22 PM
Calibre keeps shutting down while reading books in my Kindle Fire library	jmrizz	Library Management	1	09-26-2017 02:32 AM
Calibre 2.57.1 x64 NOT reading Kindle Fire HD	bighunt	Devices	3	05-24-2016 09:23 AM

12-04-2021, 01:50 AM	#2
kovidgoyal creator of calibre Posts: 45,318 Karma: 27111242 Join Date: Oct 2006 Location: Mumbai, India Device: Various	there werent any changes to the kindle driver in 5.33. Try running in debug mode and post the log (right clickthe preferences button and choose restart in debug mode).

12-04-2021, 08:10 AM	#3
watani Connoisseur Posts: 51 Karma: 10 Join Date: Oct 2014 Device: Kindle Fire HD	I just updated from 5.32 to 5.33.2 and was unable to reproduce the bug anymore. I was previously using 5.33.0 when the bug occurred, so either it was fixed since then or something corrupted my Calibre install. I'm leaning towards the latter because when I updated to 5.33.0 the installer gave a warning that another install was ongoing and the install had to be rolled back, but after the progress bar showed the rolling back finished, the update still progressed and eventually completed. I'd been using Calibre after the update and didn't see any issues until I connected my device so I didn't think much of the weirdness, but in hindsight something probably went wrong.

12-04-2021, 09:30 PM	#4
kovidgoyal creator of calibre Posts: 45,318 Karma: 27111242 Join Date: Oct 2006 Location: Mumbai, India Device: Various	No, it was a bug in 5.33.0 caused by an unrelated change preparing calibre for python 3.10 this had an undocumented side effect that broke the mtp driver on windows 64bit only.

Advert