Opening Kindle devices in Calibre will cause a disconnect from Linux LTS 4.19.51+ onwards
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
calibre |
Fix Released
|
Undecided
|
Unassigned | ||
calibre (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Please check this issue here: https:/
To summarize, a change to the VFAT handling in the Linux kernel introduced in 4.19.51 for the Linux LTS release (I'm not sure in which version it was introduced in the mainline kernel), will cause the Kindle to disconnect when issuing a sync. In practice this means when "opening" the Kindle in Calibre and inspecting the files, this sync command will be issued and the Kindle will immediately disconnect, effectively preventing usage with Calibre. I've had this issue for a few Linux releases now and finally realized that it was a change in the Kernel -- I'm not sure why more people aren't reporting this.
As suggested by Ogawa Hirofumi, you might want to contact the UDisk developers and request the "nobarrier" option to be put on the whitelist, so Calibre can request this option when mounting the device to prevent this behavior.
summary: |
Opening Kindle devices in Calibre will cause a disconnect from Linux LTS - 4.19.50+ onwards + 4.19.51+ onwards |
I use Linux as my daily driver with a Kindle PaperWhite, running
kernel 5.1.9 and see no disconnects. The analysis in that bug report
makes no sense.
1) nobarrier is a really bad idea, it means applications cannot rely on
fsync() anymore, so there is no way to guarantee that data is actually
written to the disk. In particular this means you *have* to unmount the
disk before disconnecting the cable. And any database or similar software
running on a nobarrier fs will lead to data corruption.
2) If nobarrier is indeed the only way forward (which I highly doubt,
but...) then it should be done system wide. Otherwise depending on
whether the device is mounted by calibre or something else, you will get
different behavior, which is just chaos.
Since no one else has reported this issue and I cannot replicate it
either, I am guessing it is something specific to your system. I suggest
trying to update your Kindle firmware to the latest, also (although I
dont think this should matter) try a different USB cable and port (for
instance USB 2 vs 3 or a different USB hub).