Le 28/02/2011 14:49, Josselin Mouette a écrit :
Good. Since nautilus allows to specify a different action for each media
type.
did you test that? I was proposed several actions, but *all of them*
mounted the drive first, including the "do nothing" action. My current
nautilus configuration
Le lundi 28 février 2011 à 14:31 +0100, Baptiste Carvello a écrit :
> Le 28/02/2011 14:17, Josselin Mouette a écrit :
> > [insulting part snipped] #544148 is about not starting the gvfs
> > daemons at all. Your problem, as I understand it, is not that a volume
> > monitor process is started: it is
Le 28/02/2011 14:17, Josselin Mouette a écrit :
[insulting part snipped] #544148 is about not starting the gvfs
daemons at all. Your problem, as I understand it, is not that a volume
monitor process is started: it is just a volume monitor and doesn’t act
upon itself. The actual mounting is initia
Le lundi 28 février 2011 à 12:59 +0100, Baptiste Carvello a écrit :
> The automatic starting of gvfs-gphoto2-volume-monitor breaks my workflow: I
> need
> to manually unmount the camera before I can do anything (the fact that I was
> also bitten by bug #546398 makes it even worse).
Please don’
severity 544148 normal
kthxbye
Version: 1.6.4-3
Package: gvfs or gvfs-backends
Upon upgrading to squeeze, I got bitten by this bug: I am used to downloading my
photos using gphoto2 on the command line. This is a perfectly legitimate and in
my case optimal workflow. I won't change it: I own th
5 matches
Mail list logo
