|
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.
|