So getting back to this issue. It still happens with a relatively upstream kernel version 3.4-rc3. When experimenting a bit more it seems that there are various cases:
1. automatically mounted by udisk under /media and not having a shell changed into that mount dir.
-> this seems to work, after resuming a new nautilus window appears as with a freshly inserted card
2. automatically mounted by udisk but having a shell changed into the mount dir.
-> Shows the mount error, the mountpoint does _not_ show up in df or /proc/mounts and typing ls
in the shell results in an IO error.
3. manually mounted (to /mnt) without shell changed into the mount dir.
-> Shows the mount error, df and /proc/mounts do contain the mount point, typing ls results
in the IO error.
4. manually mounted and changing into the mount dir seems the same as 3.
So getting back to this issue. It still happens with a relatively upstream kernel version 3.4-rc3. When experimenting a bit more it seems that there are various cases:
1. automatically mounted by udisk under /media and not having a shell changed into that mount dir.
-> this seems to work, after resuming a new nautilus window appears as with a freshly inserted card
2. automatically mounted by udisk but having a shell changed into the mount dir.
-> Shows the mount error, the mountpoint does _not_ show up in df or /proc/mounts and typing ls
in the shell results in an IO error.
3. manually mounted (to /mnt) without shell changed into the mount dir.
-> Shows the mount error, df and /proc/mounts do contain the mount point, typing ls results
in the IO error.
4. manually mounted and changing into the mount dir seems the same as 3.