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
