The permissions of "Kindle" could not be determined

TCDNV · 10-23-2022, 01:35 PM

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?

All comments and suggestions greatly appreciated!
Thanks,
Tom

JSWolf · 10-23-2022, 01:46 PM

Try a Windows system and see what happens.

Quoth · 10-23-2022, 02:28 PM

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?

All comments and suggestions greatly appreciated!
Thanks,
Tom

That error message usually means a "drive" is corrupt. It never means the permissions need reset.

Try a different cable and different USB port.
Reboot Kindle.

Trying Windows isn't a useful idea.

TCDNV · 10-23-2022, 02:59 PM

Thanks Quoth!

I rebooted several times, changed the cable even though Calibre see the Kindle and thinks it has successfully transferred the book. I have also swapped USB ports etc. I have rebooted the Kindle several times.

When I look at the properties via right click on the mounted icon I get the error message. When I look at the Kindle via sudo Caja I see the correct permissions correctly...

All comments and suggestions greatly appreciated!

Thanks,
Tom
PS: JSWolf, Resident Curmudgeon: I haven't owned or used Windows since XP.

JSWolf · 10-23-2022, 03:32 PM

Quote:

Originally Posted by TCDNV

Thanks Quoth!

I rebooted several times, changed the cable even though Calibre see the Kindle and thinks it has successfully transferred the book. I have also swapped USB ports etc. I have rebooted the Kindle several times.

When I look at the properties via right click on the mounted icon I get the error message. When I look at the Kindle via sudo Caja I see the correct permissions correctly...

All comments and suggestions greatly appreciated!

Thanks,
Tom
PS: JSWolf, Resident Curmudgeon: I haven't owned or used Windows since XP.

But you may know someone with a Windows computer.

Another thing to try is run a disk scanner to see if it finds anything wrong.

haertig · 10-23-2022, 04:58 PM

Does your Kindle auto-mount?

What does the "mount" command tell you?

My mount command shows this:

Code:

$ mount | grep KINDLE
/dev/sdc1 on /media/demo/KINDLE type vfat (rw,nosuid,nodev,noexec,noatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)

How much space do you have available on your Kindle? (Note: substitute your userid for mine, "demo")

Code:

$ df -h /media/demo/KINDLE
Filesystem      Size  Used Avail Use% Mounted on
/dev/sdc1       3.1G  309M  2.8G  10% /media/demo/KINDLE

Does your Kindle's directory listing look sane?

Code:

$ ls -al /media/demo/KINDLE
total 832
drwxr-xr-x  20 demo demo   4096 Dec 31  1969 .
drwxr-x---+  3 root root     60 Oct 23 14:45 ..
drwxr-xr-x   5 demo demo   4096 Sep  5  2020 .active_content_sandbox
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Alarms
drwxr-xr-x   2 demo demo   4096 Oct 14 18:25 amazon-cover-bug
drwxr-xr-x   3 demo demo   4096 Jul 14  2021 Android
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 .android_secure
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 DCIM
drwxr-xr-x  26 demo demo   4096 Oct 14 18:25 documents
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Download
-rwxr-xr-x   1 demo demo    300 Oct 14 18:21 driveinfo.calibre
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 LOST.DIR
-rwxr-xr-x   1 demo demo 766327 Oct 14 18:25 metadata.calibre
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Movies
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Music
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Notifications
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Pictures
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Podcasts
drwxr-xr-x   2 demo demo   4096 Jul 14  2021 Ringtones
drwxr-xr-x  16 demo demo   4096 Oct 30  2020 system
drwxr-xr-x   4 demo demo   4096 Oct 14 15:30 .Trash-1000
drwxr-xr-x   2 demo demo   4096 Mar 14  2018 voice

p.s. - Does your Kindle say "USB Drive Mode" when you plug it into your computer?

Quoth · 10-23-2022, 05:17 PM

Quote:

Originally Posted by JSWolf

But you may know someone with a Windows computer.

Another thing to try is run a disk scanner to see if it finds anything wrong.

Do stop. It's more use to examine disks on Linux than Windows.

NullNix · 10-23-2022, 07:48 PM

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

TCDNV · 10-23-2022, 10:04 PM

Heartig,

I think you are on to something!

tcd@tcd-yjl:~$ mount | grep Kindle
/dev/sdb on /media/tcd/Kindle type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask= 0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remou nt-ro,uhelper=udisks2)

I do not have a sub directory in /media called "demo". When I run "tcd@tcd-yjl:~$ df -h /media/tcd/Kindle"
Filesystem Size Used Avail Use% Mounted on
/dev/sdb 6.3G 572M 5.7G 9% /media/tcd/Kindle

"tcd@tcd-yjl:~$ ls -al /media/tcd/Kindle"
total 10276
drwxr-xr-x 9 tcd tcd 8192 Dec 31 1969 .
drwxr-x---+ 3 root root 4096 Oct 23 18:24 ..
drwxr-xr-x 5 tcd tcd 8192 Jun 13 2021 .active_content_sandbox
drwxr-xr-x 2 tcd tcd 40960 Oct 22 20:00 amazon-cover-bug
drwxr-xr-x 2 tcd tcd 8192 Jul 31 11:03 audible
drwxr-xr-x 118 tcd tcd 16384 Oct 21 15:27 documents
-rw-r--r-- 1 tcd tcd 298 Oct 22 19:42 driveinfo.bkup-calibre
-rw-r--r-- 1 tcd tcd 264 Oct 23 11:40 driveinfo.calibre
-rw-r--r-- 1 tcd tcd 298 Oct 22 19:42 driveinfo.up-calibre
drwxr-xr-x 2 tcd tcd 8192 May 9 2021 fonts
-rw-r--r-- 1 tcd tcd 132470 Aug 20 15:20 kindle_collections_path_cache.calibre
-rw-r--r-- 1 tcd tcd 10241195 Oct 23 11:40 metadata.calibre
drwxr-xr-x 19 tcd tcd 8192 Oct 23 08:54 system
drwxr-xr-x 4 tcd tcd 8192 Jul 11 2021 .Trash-1000

Unfortunately this has now progressed beyond my understanding. Can you tell me anything from these results?

I have also noticed that the /media/tcd directory is empty until I mount the kindle. Then is seems to id the Kindls as a USB:
Please see the attached screen clip.

Thanks VERY Much for all of your help!
Tom
PS: I would swear that I have used Calibre since I upgraded to Linux Mint, Mate 20.x. However I can't account for the sub directory "tcd" in the "media" sub directory.
t

TCDNV · 10-23-2022, 10:13 PM

Howdy NullNix,

Thanks for the help! As I mentioned in my response to Haertig the /media/tcd folder is empty until I mount the Kindle and Mint, Mate recognizes the Kindle every time. The file manager shows the Kindle directory's/file's and I can edit individual files.
Still getting the error message via Caja when I look at "Properties".

Thanks VERY Much for all of your help!
Tom

haertig · 10-23-2022, 11:34 PM

Quote:

Originally Posted by TCDNV

Can you tell me anything from these results?

What you copied/pasted shows that your Kindle is auto-mounting just fine, and you have plenty of available space on the Kindle to store files. I have a "demo" directory because I am logged in as a user named "demo". You are logged in as a user named "tcd", which is why you have a "tcd" directory as opposed to my "demo" directory. All of this is perfectly normal and expected.

Your directory listing (the output of the "ls -al" command you ran) is different than mine. But that just indicates that we have different models of Kindle, or different firmware. The fact that you get "reasonable looking" output is all I was trying to establish. The output from your "mount" command indicates that you Kindle is mounted in "rw" mode (read-write), which is what you want.

In a nutshell: everything looks good on your computer/Kindle connection based on the output from your commands. Now, why your file manager is complaining about your Kindle is a bit of a mystery.

We can get more information if you do this:

Immediately after plugging your Kindle into the USB port of your computer, run the command:

Code:

dmesg | tail -100

Then cut-n-paste the output of that command into your reply to this thread.

On some Linux installations, you may get an error if you try to run the dmesg command. That error might look something like this:

Code:

$ dmesg | tail -100
dmesg: read kernel buffer failed: Operation not permitted

If you see this error, add the word "sudo" before dmesg, like this:

Code:

sudo dmesg | tail -100

Normally this will ask you for your password. This will be the password that you enter when you login as user name "tcd". Most likely, when you installed Mint, you told it to to automatically login user tcd without asking for a password. If you indeed installed it this way, I hope you remember the password you set for user tcd, despite you rarely needing to use it.

Anyway, hopefully you will be able to run the dmesg command and post it's output for us to look at. dmesg will dump out a LOT of text if you run it plain, which is why I have you piping the output to the tail command ... so we only see that last 100 lines of what dmesg dumps out. This is also why I said to run dmesg immediately after you plug in your Kindle, so you don't run other commands and pollute the dmesg output with other messages that come later than the Kindle being plugged in (we want the Kindle stuff to be in the most recent 100 lines that we asked for with "tail").

TCDNV · 10-24-2022, 12:07 AM

haertig,
Thanks for all of this intense help!

HereWeGo!

Code:


tcd@tcd-yjl:~$ dmesg | tail -100
[10435.378531] usb 1-7: New USB device found, idVendor=1949, idProduct=0004, bcdDevice= 4.01
[10435.378545] usb 1-7: New USB device strings: Mfr=0, Product=4, SerialNumber=5
[10435.378552] usb 1-7: Product: Internal Storage
[10435.378557] usb 1-7: SerialNumber: G000P812837702LL
[10435.403446] usb-storage 1-7:1.0: USB Mass Storage device detected
[10435.403582] usb-storage 1-7:1.0: Quirks match for vid 1949 pid 0004: 80000000
[10435.403618] scsi host4: usb-storage 1-7:1.0
[10435.403737] usbcore: registered new interface driver usb-storage
[10435.406042] usbcore: registered new interface driver uas
[10436.405651] scsi 4:0:0:0: Direct-Access     Kindle   Internal Storage 0401 PQ: 0 ANSI: 2
[10436.406324] sd 4:0:0:0: Attached scsi generic sg2 type 0
[10436.406674] sd 4:0:0:0: Power-on or device reset occurred
[10436.407238] sd 4:0:0:0: [sdb] Media removed, stopped polling
[10436.408756] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[10446.553786] sd 4:0:0:0: [sdb] 13051821 512-byte logical blocks: (6.68 GB/6.22 GiB)
[10446.770525] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[10446.770537] sdb: detected capacity change from 0 to 13051821
[10446.774816]  sdb:
[10447.112862] FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[10706.802075] sdb: detected capacity change from 13051821 to 0
[10760.434445] usb 1-7: USB disconnect, device number 4
[10764.839981] usb 1-7: new high-speed USB device number 5 using xhci_hcd
[10764.989845] usb 1-7: New USB device found, idVendor=1949, idProduct=0004, bcdDevice= 4.01
[10764.989861] usb 1-7: New USB device strings: Mfr=0, Product=4, SerialNumber=5
[10764.989867] usb 1-7: Product: Internal Storage
[10764.989873] usb 1-7: SerialNumber: G000P812837702LL
[10764.991665] usb-storage 1-7:1.0: USB Mass Storage device detected
[10764.995201] usb-storage 1-7:1.0: Quirks match for vid 1949 pid 0004: 80000000
[10764.995372] scsi host4: usb-storage 1-7:1.0
[10766.001070] scsi 4:0:0:0: Direct-Access     Kindle   Internal Storage 0401 PQ: 0 ANSI: 2
[10766.001576] sd 4:0:0:0: Attached scsi generic sg2 type 0
[10766.002020] sd 4:0:0:0: Power-on or device reset occurred
[10766.002420] sd 4:0:0:0: [sdb] Media removed, stopped polling
[10766.003527] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[10768.083434] sd 4:0:0:0: [sdb] 13051821 512-byte logical blocks: (6.68 GB/6.22 GiB)
[10768.302996] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[10768.303007] sdb: detected capacity change from 0 to 13051821
[10768.304405]  sdb:
[10768.528143] FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[12807.262708] sdb: detected capacity change from 13051821 to 0
[12878.249483] usb 1-7: USB disconnect, device number 5
[12884.014894] usb 1-7: new high-speed USB device number 6 using xhci_hcd
[12884.164638] usb 1-7: New USB device found, idVendor=1949, idProduct=0004, bcdDevice= 4.01
[12884.164650] usb 1-7: New USB device strings: Mfr=0, Product=4, SerialNumber=5
[12884.164656] usb 1-7: Product: Internal Storage
[12884.164661] usb 1-7: SerialNumber: G000P812837702LL
[12884.166157] usb-storage 1-7:1.0: USB Mass Storage device detected
[12884.166527] usb-storage 1-7:1.0: Quirks match for vid 1949 pid 0004: 80000000
[12884.166684] scsi host4: usb-storage 1-7:1.0
[12885.171806] scsi 4:0:0:0: Direct-Access     Kindle   Internal Storage 0401 PQ: 0 ANSI: 2
[12885.172406] sd 4:0:0:0: Attached scsi generic sg2 type 0
[12885.172810] sd 4:0:0:0: Power-on or device reset occurred
[12885.173325] sd 4:0:0:0: [sdb] Media removed, stopped polling
[12885.174440] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[12887.255808] sd 4:0:0:0: [sdb] 13051821 512-byte logical blocks: (6.68 GB/6.22 GiB)
[12887.469209] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[12887.469221] sdb: detected capacity change from 0 to 13051821
[12887.470519]  sdb:
[12887.749946] FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[19353.191409] sdb: detected capacity change from 13051821 to 0
[19373.523705] usb 1-7: USB disconnect, device number 6
[19399.492663] usb 1-7: new high-speed USB device number 7 using xhci_hcd
[19399.642652] usb 1-7: New USB device found, idVendor=1949, idProduct=0004, bcdDevice= 4.01
[19399.642667] usb 1-7: New USB device strings: Mfr=0, Product=4, SerialNumber=5
[19399.642674] usb 1-7: Product: Internal Storage
[19399.642679] usb 1-7: SerialNumber: G000P812837702LL
[19399.644488] usb-storage 1-7:1.0: USB Mass Storage device detected
[19399.644912] usb-storage 1-7:1.0: Quirks match for vid 1949 pid 0004: 80000000
[19399.645079] scsi host4: usb-storage 1-7:1.0
[19400.665498] scsi 4:0:0:0: Direct-Access     Kindle   Internal Storage 0401 PQ: 0 ANSI: 2
[19400.666176] sd 4:0:0:0: Attached scsi generic sg2 type 0
[19400.666699] sd 4:0:0:0: Power-on or device reset occurred
[19400.667160] sd 4:0:0:0: [sdb] Media removed, stopped polling
[19400.668834] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[19402.746745] sd 4:0:0:0: [sdb] 13051821 512-byte logical blocks: (6.68 GB/6.22 GiB)
[19402.960526] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[19402.960542] sdb: detected capacity change from 0 to 13051821
[19402.962068]  sdb:
[19403.183532] FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[19757.581035] sdb: detected capacity change from 13051821 to 0
[19761.100954] usb 1-7: USB disconnect, device number 7
[19767.471504] usb 1-7: new high-speed USB device number 8 using xhci_hcd
[19767.621375] usb 1-7: New USB device found, idVendor=1949, idProduct=0004, bcdDevice= 4.01
[19767.621393] usb 1-7: New USB device strings: Mfr=0, Product=4, SerialNumber=5
[19767.621402] usb 1-7: Product: Internal Storage
[19767.621409] usb 1-7: SerialNumber: G000P812837702LL
[19767.623200] usb-storage 1-7:1.0: USB Mass Storage device detected
[19767.626869] usb-storage 1-7:1.0: Quirks match for vid 1949 pid 0004: 80000000
[19767.626967] scsi host4: usb-storage 1-7:1.0
[19768.628308] scsi 4:0:0:0: Direct-Access     Kindle   Internal Storage 0401 PQ: 0 ANSI: 2
[19768.628890] sd 4:0:0:0: Attached scsi generic sg2 type 0
[19768.629314] sd 4:0:0:0: Power-on or device reset occurred
[19768.629664] sd 4:0:0:0: [sdb] Media removed, stopped polling
[19768.630810] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[19768.688730] sd 4:0:0:0: [sdb] 13051821 512-byte logical blocks: (6.68 GB/6.22 GiB)
[19768.914777] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[19768.914794] sdb: detected capacity change from 0 to 13051821
[19768.916188]  sdb:
[19769.152449] FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[19782.922935] sdb: detected capacity change from 13051821 to 0

tcd@tcd-yjl:~$ fsck /media/tcd/Kindle
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
fsck.ext2: Is a directory while trying to open /media/tcd/Kindle

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>

Attached is the Gparted screen shot.

Maybe I should just wipe and reinstall the default Kindle OS and rebuild my ebook library which is not a big deal...

Thanks again,
Tom

NullNix · 10-24-2022, 06:14 AM

Quote:

Originally Posted by haertig

Anyway, hopefully you will be able to run the dmesg command and post it's output for us to look at. dmesg will dump out a LOT of text if you run it plain, which is why I have you piping the output to the tail command ... so we only see that last 100 lines of what dmesg dumps out. This is also why I said to run dmesg immediately after you plug in your Kindle, so you don't run other commands and pollute the dmesg output with other messages that come later than the Kindle being plugged in (we want the Kindle stuff to be in the most recent 100 lines that we asked for with "tail").

dmesg will almost certainly show nothing. The kernel is clearly happy with the USB and the filesystem mounted over it: and automounting worked so udev is clearly happy too (and so is udisks, which hooks into udev for block devices and actually does the automounting). The problem is *probably* at a higher level, which likely means that udisks is telling nemo the wrong thing about its mount points, or that nemo is misunderstanding it.

A udisksctl monitor would be really useful at this point

JSWolf · 10-24-2022, 06:17 AM

Quote:

Originally Posted by Quoth

Do stop. It's more use to examine disks on Linux than Windows.

It's not to examine the disk, it's to check if it could be an issue with Linux.

Quoth · 10-24-2022, 06:58 AM

Deleted

10-23-2022, 01:35 PM	#1
TCDNV Member Posts: 12 Karma: 10 Join Date: Dec 2018 Device: Kobo Clara HD	[SOLVED] The permissions of "Kindle" could not be determined 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? All comments and suggestions greatly appreciated! Thanks, Tom Attached Thumbnails Last edited by TCDNV; 10-24-2022 at 05:35 PM.

10-23-2022, 10:04 PM	#9
TCDNV Member Posts: 12 Karma: 10 Join Date: Dec 2018 Device: Kobo Clara HD	RE: The permissions of "Kindle" could not be determined Heartig, I think you are on to something! tcd@tcd-yjl:~$ mount \| grep Kindle /dev/sdb on /media/tcd/Kindle type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask= 0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remou nt-ro,uhelper=udisks2) I do not have a sub directory in /media called "demo". When I run "tcd@tcd-yjl:~$ df -h /media/tcd/Kindle" Filesystem Size Used Avail Use% Mounted on /dev/sdb 6.3G 572M 5.7G 9% /media/tcd/Kindle "tcd@tcd-yjl:~$ ls -al /media/tcd/Kindle" total 10276 drwxr-xr-x 9 tcd tcd 8192 Dec 31 1969 . drwxr-x---+ 3 root root 4096 Oct 23 18:24 .. drwxr-xr-x 5 tcd tcd 8192 Jun 13 2021 .active_content_sandbox drwxr-xr-x 2 tcd tcd 40960 Oct 22 20:00 amazon-cover-bug drwxr-xr-x 2 tcd tcd 8192 Jul 31 11:03 audible drwxr-xr-x 118 tcd tcd 16384 Oct 21 15:27 documents -rw-r--r-- 1 tcd tcd 298 Oct 22 19:42 driveinfo.bkup-calibre -rw-r--r-- 1 tcd tcd 264 Oct 23 11:40 driveinfo.calibre -rw-r--r-- 1 tcd tcd 298 Oct 22 19:42 driveinfo.up-calibre drwxr-xr-x 2 tcd tcd 8192 May 9 2021 fonts -rw-r--r-- 1 tcd tcd 132470 Aug 20 15:20 kindle_collections_path_cache.calibre -rw-r--r-- 1 tcd tcd 10241195 Oct 23 11:40 metadata.calibre drwxr-xr-x 19 tcd tcd 8192 Oct 23 08:54 system drwxr-xr-x 4 tcd tcd 8192 Jul 11 2021 .Trash-1000 Unfortunately this has now progressed beyond my understanding. Can you tell me anything from these results? I have also noticed that the /media/tcd directory is empty until I mount the kindle. Then is seems to id the Kindls as a USB: Please see the attached screen clip. Thanks VERY Much for all of your help! Tom PS: I would swear that I have used Calibre since I upgraded to Linux Mint, Mate 20.x. However I can't account for the sub directory "tcd" in the "media" sub directory. t Attached Thumbnails

10-24-2022, 06:58 AM	#15
Quoth Still reading Posts: 14,045 Karma: 105092227 Join Date: Jun 2017 Location: Ireland Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper	Deleted Last edited by Quoth; 10-24-2022 at 08:23 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Pressing "Restore Defaults" under "Book Details" wipes all "Look & Feel" settings.	MarjaE	Library Management	1	03-30-2021 11:46 AM
Reader and Educator Guide to "The Hobbit" and "The Lord of the Rings" (Kindle)	Fluribus	Deals and Resources (No Self-Promotion or Affiliate Links)	4	08-21-2012 02:12 PM
I found references to "PRIME_EBOOKS" and "kindle-video-slate" on Amazon pages!	nick541	Amazon Kindle	7	09-26-2011 02:56 PM
"Settings," then "311" - Int'l Kindle searches for wireless providers in the area	Dr. Drib	Amazon Kindle	2	08-28-2011 10:27 AM

10-23-2022, 01:46 PM	#2
JSWolf Resident Curmudgeon Posts: 79,758 Karma: 145864619 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Try a Windows system and see what happens.

10-23-2022, 02:59 PM	#4
TCDNV Member Posts: 12 Karma: 10 Join Date: Dec 2018 Device: Kobo Clara HD	Thanks Quoth! I rebooted several times, changed the cable even though Calibre see the Kindle and thinks it has successfully transferred the book. I have also swapped USB ports etc. I have rebooted the Kindle several times. When I look at the properties via right click on the mounted icon I get the error message. When I look at the Kindle via sudo Caja I see the correct permissions correctly... All comments and suggestions greatly appreciated! Thanks, Tom PS: JSWolf, Resident Curmudgeon: I haven't owned or used Windows since XP.

10-23-2022, 10:13 PM	#10
TCDNV Member Posts: 12 Karma: 10 Join Date: Dec 2018 Device: Kobo Clara HD	Howdy NullNix, Thanks for the help! As I mentioned in my response to Haertig the /media/tcd folder is empty until I mount the Kindle and Mint, Mate recognizes the Kindle every time. The file manager shows the Kindle directory's/file's and I can edit individual files. Still getting the error message via Caja when I look at "Properties". Thanks VERY Much for all of your help! Tom