Hi Ivan, thanks for the input but your workaround is sort of "too invasive" kind of workaround.
"Testing" users can be less advanced than that (like me for example). My main reason for using testing is to avoid the stable_to_stable upgrade pain. What I mean is that "testing" can (and will) allow some breakage but this specific issue is too mmuch of a functionality loss. A better workaorund would be to restore automounting in g-v-m until nautilus 2.24 is ready for "testing". I know that I can compile g-v-m from source with automounting enabled. Still, if a g-v-m with automounting could be uploaded to "testing" that would be nice. Regards Vittorio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org