Quote:
Originally Posted by TCDNV
Howdy,
PC System: OS = Linux Mint, Mate, 22.0
Recently I have not been able to load ebooks from Calibre to my Kindle Oasis. I booted to a live USB for the same OS noted above and it still did not work. I have used Linux and Calibre for years with no problem until now.
Here's the error:
"The permissions of "Kindle" could not be determined".
1) How do I reset the permissions so I can restore this function?
|
Digging around, this message comes from Nemo, Mint's file manager (its ancestor Nautilus has this code too): it does not come from Calibre and as far as I can tell there is no way Calibre can directly generate it (though Nemo might be auto-launching when you plug your Kindle in and trying to display its contents). This message is displayed if the file (represented by an instance of the glib GLocalFile class) does not have a mode. Needless to say, all files in Unix have a mode! So what can cause this? As far as I can tell, nothing: the mode is literally the first attribute initialized when the class is created (so every instance, i.e. every file, has one of them) So this is a "can never happen" message of sorts.
I think what's possibly happening is that the GLocalFile instance corresponding to your Kindle mount point is failing to be created (and that error message is a *terrible* way of putting that across), probably because the directory in which the Kindle mount point is located isn't readable: if the thing is being auto-launched it is quite possible it's getting launched too soon, before the mount point is readable, and might then get in Calibre's way and stop *it* from using the thing too. I hope not (this is pure speculation with no evidence at this point). We need more info! So let's get some.
Now I'm not sure what that mount point is -- df before and after plugging in the Kindle may tell you -- but it's probably under /mnt or /media. If nothing changes in df after plugging in the Kindle, the automounting is failing: that's down to udisks probably. Running 'udisksctl monitor' as root and plugging in the Kindle may tell you what's going on -- I'd expect to see at least one Device line listed. If nothing is listed at all, your problem is at the udev (dynamic device registration) level: 'udevadm monitor' might tell you what's going on at that level.
(Nearly all of these things are configured using simple-ish plain text files, so it should be fairly easy to fix without rebuilding anything once we figure out what is going on.)