Yes, there are reaons for this. Primarily, because it usually does not
make sense to mount hardware on a different machine, since you do not
have physical access to it. The more important reason, though, is to
prevent a race condition between the local foreground user session and
other sessions.
(Another reason for wont fix is that g-v-m stopped doing the automount
handling in Hardy, but that's really secondary.)
--
gvm doesn't work for remote sessions
https://bugs.launchpad.net/bugs/161763
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Warning: i don't know the impact of the described workaround. Use at
your own risk...
--
gvm doesn't work for remote sessions
https://bugs.launchpad.net/bugs/161763
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-volume-manager
