I don't know if this is a proper dupe of #463347. The reporters there are referring to udev issues, which, afaik, should end up with the device nodes for the inserted media not being allocated?
I'm getting the same issue (with the same work-around: launch palimsest and re-plug the external storage device -- I'm hoping this will work for optical media too, since putting a DVD in my drive doesn't result in something showing up in my Places menu, and double-clicking my drive in the "Computer" view in Nautilus doesn't attempt to mount the drive either), but I do see messages in dmesg referring to the device being plugged in and a /dev/sdXN node being allocated to it. It's just not showing up in Nautilus.
Dolphin, however, *does* show the device and will let me mount and browse it. All of this makes me think the issue at hand here is not the death of udev by fd leak, but something either in gvfs or nautilus.
I don't know if this is a proper dupe of #463347. The reporters there are referring to udev issues, which, afaik, should end up with the device nodes for the inserted media not being allocated?
I'm getting the same issue (with the same work-around: launch palimsest and re-plug the external storage device -- I'm hoping this will work for optical media too, since putting a DVD in my drive doesn't result in something showing up in my Places menu, and double-clicking my drive in the "Computer" view in Nautilus doesn't attempt to mount the drive either), but I do see messages in dmesg referring to the device being plugged in and a /dev/sdXN node being allocated to it. It's just not showing up in Nautilus.
Dolphin, however, *does* show the device and will let me mount and browse it. All of this makes me think the issue at hand here is not the death of udev by fd leak, but something either in gvfs or nautilus.