Thread: The newer the Kindle, the worse the problems.
View Single Post
Old 12-02-2022, 08:13 PM   #3
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,572
Karma: 169115148
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
One minor nit: your device is a Fire tablet. Amazon dropped the Kindle Fire name back in 2014 so what you have is a Fire 10 Plus.

And as Kovid already mentioned, this line in your debug listing tells the story:

Code:
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling already LIBMTP
DNSB is offline   Reply With Quote