> Is there a way to stop gvfsd-gphoto2 from respawning?
It's started by the volume manager which is started by system-wide
defaults for Gnome/Ubuntu systemd user session.
Tell systemd that you want that service to be disabled for your (current) user
account:
systemctl --user mask gvfs-gphoto2-
Is there a way to stop gvfsd-gphoto2 from respawning?
Even after killing and disabling the process, blacklisting
'60-glibphoto2-6.rules' from udev, GTK still respawn it:
153716 tty2 Sl+0:00 /usr/libexec/gvfsd-gphoto2 --spawner :1.6
/org/gtk/gvfs/exec_spaw/20
--
You received this bug not
** Changed in: gvfs (Ubuntu)
Status: Triaged => Confirmed
--
gvfsd-gphoto2 locks camera
https://bugs.launchpad.net/bugs/388712
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
In Karmic, with kernel 2.6.31-14, I still see the 'cannot lock device'
error when connecting a digital camera. Killing 'gvfs-gphoto2-volume-
monitor' stops the error. However, once I load f-spot and import the
photos, the gvfs-gphoto2-volume-monitor process is started again. Also,
killing this p
** Package changed: libgphoto2 (Ubuntu) => gvfs (Ubuntu)
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Low
** Changed in: gvfs (Ubuntu)
Status: New => Triaged
--
gvfsd-gphoto2 locks camera
https://bugs.launchpad.net/bugs/388712
You received this bug notification because you ar
