Hi Folks,

The gvfs daemon is not being started.

There is a gvfs-daemon.service file in /usr/share/dbus-1/services which is supposed to execute /usr/lib/gvfs/gvfsd

What startup or configuration file needs to be edited to ensure that the gvfs daemon is started when the system is initialised? Or, is there some other way that this is supposed to be configured?

Thanks, Michael.

that file is not present of my a4 system, nor is gvfs installed. gvfs isn't needed for anything in antiX IIRC. Even spacefm doesn't use it, preferring its own VFS implementation.

You haven't answered the question.

SpaceFM doesn't support PTP cameras.

I am hoping that I can add an entry to the udevil.conf file for the GVFS Daemon so that SpaceFM can automaticaly detect and mount PTP cameras.

With GALPon MiniNo Ártabros 2.1, which has GVFS installed by default to support PCManFM, once the camera has been mounted by PCManFM or via the command line using gvfs-mount, SpaceFM can access the files on the camera which are mounted at HOME/<USER>/.gvfs.

So, once again, what needs to de done to have the GVFS Daemon started when the system is initialised?

Thank you, MTB.

Install gvfs?

anticapitalista wrote:Install gvfs?

Yes, I've done that.

I can't tell you how to get the daemon to autostart ( I see gvfs in jessie has a systemD dependency as well that gets pulled in).

But I can offer 2 other options:

1. use gtkam (installed by default in antiX) to access the camera. Its not fancy, but it worked on my only camera that supports ptp mode.

2. Instead of gvfs, try gphotofs, availabe in the repo. It also uses libphoto2, which is already installed by default. its a fuse filesystem. on my system, I made a all excessible mount point in /media (I used /media/camera). then the command, with the camera plugged in, which mounted the camera files system in /media/camera, now accessible to every file managing utility out there. I added that command to a menu in spacefm, as well as for easy unmounting.

I tried to get gvfs installed and working, but I'm actually thinking that perhaps the hooks are now systemD rather than systemVinit that antiX uses. When I launchd the gvfsd manually, my cpu usage went to 100% and stayed there, so obviously there is something else going on.

Next version of antiX-a5 will have nosystemd gvfs in its repos. I'm not sure if it will work in a4.
If you want to try it, make sure your etc/apt/sources.list.d/antix.list looks like this.
You will also need to create a file in etc/apt/prefrences called 00systemd with the following contents.
If it works, great, otherwise you get to pick up the (alpha) pieces

anticapitalista wrote:Next version of antiX-a5 will have nosystemd gvfs in its repos. I'm not sure if it will work in a4.
If you want to try it, make sure your etc/apt/sources.list.d/antix.list looks like this.

Code: Select all

# Use with Debian Testing (or Sid) repositories. Set as default for antiX-14R.
deb http://antix.daveserver.info/testing testing main nosystemd 
# Use with Debian Stable/Jessie repositories.
deb http://antix.daveserver.info/stable stable main 

You will also need to create a file in etc/apt/prefrences called 00systemd with the following contents.

Code: Select all

Package: *systemd*
Pin: origin""
Pin-Priority: -1

If it works, great, otherwise you get to pick up the (alpha) pieces

Thanks for popping in on this topic.

I'm still very much a new Linux user but not new to computing. Documentation, in general, is dreadful which is the main factor inhibiting my progress with installing and configuring systems.

So, should I completely remove all the GVFS related packages, including PCManFM, that I have installed before attempting to install the nosystemd version of gvfs?

I think it will overwrite what you have. But I'm not 100% sure.

dolphin_oracle wrote:I can't tell you how to get the daemon to autostart ( I see gvfs in jessie has a systemD dependency as well that gets pulled in).

But I can offer 2 other options:

1. use gtkam (installed by default in antiX) to access the camera. Its not fancy, but it worked on my only camera that supports ptp mode.

2. Instead of gvfs, try gphotofs, availabe in the repo. It also uses libphoto2, which is already installed by default. its a fuse filesystem. on my system, I made a all excessible mount point in /media (I used /media/camera). then the command, with the camera plugged in,

Code: Select all

gphotofs /media/camera.

which mounted the camera files system in /media/camera, now accessible to every file managing utility out there. I added that command to a menu in spacefm, as well as

Code: Select all

umount /media/camera

for easy unmounting.

I tried to get gvfs installed and working, but I'm actually thinking that perhaps the hooks are now systemD rather than systemVinit that antiX uses. When I launchd the gvfsd manually, my cpu usage went to 100% and stayed there, so obviously there is something else going on.

Hi D.O.,

I had already gone through all those options you suggested.

Besides looking for another Distro for my Laptop, I am also trying to configure GALPon MiniNo Ártabros 2.1 on an old Pentium 4 Desktop for my landlord's daughter who is only 9 years old and hence I want things to be seamless for her and I really like the features provided by SpaceFM especially the multiple panes and reopening of same.

I was hoping that antiX already had this problem solved given that SpaceFM is the default File Manager for some of the Desktop Environment options and then I could apply the same techniques to MiniNo Ártabros.

The following is what I have attempted in the GALPon MiniNo Ártabros environment.

I was hoping that I could add an entry to the udevil.conf file for the GVFS Daemon so that SpaceFM can automaticaly detect and mount PTP cameras.

I tried the following in the udevil.conf file but without success.

default_options_fuse.gvfs-fuse-daemon = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
default_options_gvfs-fuse-daemon = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID

With GALPon MiniNo Ártabros 2.1, which has GVFS installed by default to support PCManFM, once the camera has been mounted by PCManFM (which appears to have 'hooks' for gvfs) or via the command line using"gvfs-mount gphoto2://[usb:bbb,ddd]/" (where bbb = the USB Bus and ddd = the USB Device on the bbb Bus), SpaceFM can access the files on the camera which are mounted at HOME/<USER>/.gvfs.

I can see that SpaceFM is detecting the camera being mounted to the system because I can see a new device entry being added under /dev/bus/usb/bbb (where bbb = the USB Bus identifier) but there is nothing being displayed in the Devices pane of SpaceFM and it can only view the files when either the gphotofs or"gvfs-mount gphoto2" commands have been executed but there is still nothing displayed in the Devices pane.

I even created and tested a simple Custom Menu item for the Devices context menu, in SpaceFM, to use the"gvfs-mount gphoto2" command.

The documentation for SpaceFM and udevil appear to be written for people who already have a thorough understanding of the ins and outs of mounting file systems with Linux. Therefore, I am finding it bloody difficult to determine if what I am trying to achieve is feasible or not.