gvfs claming that http is not supported - except under sudo.

Neil Williams codehelp at debian.org
Sat Mar 22 11:43:51 UTC 2008


On Sat, 22 Mar 2008 11:12:18 +0000
Neil Williams <codehelp at debian.org> wrote:

> On Sat, 2008-03-22 at 11:23 +0100, Sebastian Dröge wrote:
> > Am Samstag, den 22.03.2008, 09:25 +0000 schrieb Neil Williams:
> > 
> > > $ gvfs-info http://www.google.com/
> > > Error getting info: The specified location is not supported

OK, this is a test from that powerpc laptop I mentioned.

Prior to restarting dbus, same behaviour as before - only sudo worked.

After restarting dbus (and losing/re-gaining the network connection via
Network-Manager), nothing worked, not even sudo.

However, once I killed the root processes for gvfs, then things worked
- with and without sudo.

$ gvfs-info http://www.google.com
display name: /
edit name: /
type: unknown
size: 0
attributes:
  standard::display-name: /
  standard::edit-name: /
  standard::content-type: text/html
  id::filesystem:
type='http',uri='http://www.google.com',mount_prefix='/'

and updating deb-gview CVS on this machine to current also allows
deb-gview to operate with remote files without sudo - as long as dbus
has been restarted since the installation of gvfs and gvfs has not
tried to start before dbus is restarted.

I think gvfs may need a daemon control script in /etc/init.d/ and some
PID tracking in /var so that gvfs can be restarted *and the root
processes killed/restarted* in one operation and this needs to be done
after restarting dbus. Certainly it appears to me that the gvfs
processes that start before dbus is restarted are just zombies.

So, my results:
1. After installing gvfs-backends, gvfs only works with sudo.
2. After restarting dbus gvfs stops working completely.
3. After killing remaining gvfs processes, gvfs works properly.

My only concern is that the first command I used to test was a sudo
command so I can't be sure that userspace commands would work *without
at least one sudo command* after this sequence but it is difficult to
be certain of that. Restarting dbus now no longer affects gvfs -
userspace works as before:

$ sudo invoke-rc.d dbus restart
Stopping System Tools Backends: system-tools-backends.
Stopping network connection manager: NetworkManager.
Stopping power management daemon: powersaved.
Stopping Hardware abstraction layer: hald.
Stopping DHCP D-Bus daemon: dhcdbd.
Stopping system message bus: dbus.
Starting system message bus: dbus.
Starting DHCP D-Bus daemon: dhcdbd.
Starting Hardware abstraction layer: hald.
Starting power management daemon: powersaved.
Starting network connection manager: NetworkManager.
Starting System Tools Backends: system-tools-backends.
neil at fergus:deb-gview$ gvfs-info http://www.google.com
display name: /
edit name: /
type: unknown
size: 0
attributes:
  standard::display-name: /
  standard::edit-name: /
  standard::content-type: text/html
  id::filesystem:
type='http',uri='http://www.google.com',mount_prefix='/'

but if gvfs is started *before* dbus is restarted, I get these problems
requiring sudo *and then* I have to kill the existing gvfs processes
before gvfs will work at all.

(At least I didn't need to logout and login or reboot.)

-- 

Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20080322/b6b92eb8/attachment-0001.pgp 


More information about the pkg-gnome-maintainers mailing list