"connect to server" dialog empty when dbus environment not set correctly

[Viktor Kojouharov]

Binary package hint: nautilus

I'm using Ubuntu 8.04.1 with the following nautilus and gvfs packages:

  Installed: 1:2.22.3-0ubuntu2
  Candidate: 1:2.22.3-0ubuntu2
  Version table:
 *** 1:2.22.3-0ubuntu2 0
        500 http://ubuntu.ipacct.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     1:2.22.2-0ubuntu4 0
        500 http://ubuntu.ipacct.com hardy/main Packages

  Installed: 0.2.4-0ubuntu1
  Candidate: 0.2.4-0ubuntu1
  Version table:
 *** 0.2.4-0ubuntu1 0
        500 http://ubuntu.ipacct.com hardy-updates/main Packages
        100 /var/lib/dpkg/status
     0.2.3-0ubuntu4 0
        500 http://ubuntu.ipacct.com hardy/main Packages

The problem I'm experiencing is that Nautilus lost its ability to access any URI other than file://.

Because of this, the following problems arise:

1. Nautilus cannot access URIs begining with smb://, ssh://, ftp://, dav://, etc
2. The "Connect to server" dialog contains the "Custom location" as the only service type
3. Going to the Trash from Places hangs Nautilus (while using 100% CPU)

ProblemType: Bug
Architecture: i386
Date: Thu Jun 12 23:30:17 2008
DistroRelease: Ubuntu 8.04.1
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.22.3-0ubuntu2
PackageArchitecture: i386
ProcEnviron:
 PATH=/home/username/.local/bin:/opt/e17/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux 2.6.24-19-generic i686

[Dimitrios Symeonidis (azimout)]

Have you tried reinstalling the packages? type: 'sudo aptitude reinstall nautilus gvfs'.

If this doesn't fix it, can you describe when the problem first occured?

[Viktor Kojouharov (vkojouharov)]

I have tried reinstalling them multiple times, even from different servers, just in case.

I don't know when this problem first appeared. It definitely worked when I first upgraded to Hardy.

[Dimitrios Symeonidis (azimout)]

Can you try checking if you have the package 'libsmbclient' installed? Type 'aptitude show libsmbclient' and see if you get 'State: installed'.

[Viktor Kojouharov (vkojouharov)]

I have it installed. Though even if I didn't, it wouldn't account for the absence of the rest of the URI. There is most likely something wrong with gvfs, or with the link between nautilus and gvfs, but I don't know what.

[Dimitrios Symeonidis (azimout)]

try to run 'aptitude search gvfs' and see what's installed and that not? I get:

i A gvfs - userspace virtual filesystem - server
i A gvfs-backends - userspace virtual filesystem - backends
i gvfs-bin - userspace virtual filesystem - binaries
i gvfs-fuse - userspace virtual filesystem - fuse server
p libgvfscommon-dev - userspace virtual filesystem - development files
i A libgvfscommon0 - userspace virtual filesystem - library

Particularly important seems gvfs-backends:
Description: userspace virtual filesystem - backends
 gvfs is a userspace virtual filesystem where mount runs as a separate processes which you talk to
 via dbus. It also contains a gio module that seamlessly adds gvfs support to all applications using
 the gio API. It also supports exposing the gvfs mounts to non-gio applications using fuse.

 This package contains the archive, burn, cdda, computer, dav, dnssd, ftp, http, localtest, network,
 obexftp, sftp, smb, smb-browse and trash backends.

[Viktor Kojouharov (vkojouharov)]

I have the gvfs-backends installed, and it does contain all the necessary backends.

Tried reinstalling that too. Still doesn't work.

[Dimitrios Symeonidis (azimout)]

Sorry, don't know how else to help you.

Unfortunately, I also don't see how I could reproduce this bug (if it is actually a bug), in order to confirm it...

Maybe someone else can join this discussion?

[Viktor Kojouharov (vkojouharov)]

I found out what causes it.

There is a problem with the gvfs and/or gvfs-backends package in hardy-updates (0.2.4). Once these are upgraded, nautilus loses its knowledge of anything other than file://

Should I start another bug somewhere for these packages?

[Dimitrios Symeonidis (azimout)]

I'm not so sure this is the cause: I have the same versions of the packages as you, and I don't have this problem.
Anyway, this bug report is fine, no need to start a new one...

gvfs & gvfs-backends: 0.2.4-0ubuntu1
nautilus: 1:2.22.3-0ubuntu2

[Dimitrios Symeonidis (azimout)]

Could it be your user priviledges that stop you from accessing these resources? What is the output of the 'id' command?

[Viktor Kojouharov (vkojouharov)]

I don't see how it could possibly be privileges, because:

1. everything works fine with the previous version of gvfs
2. why would it stop me from accessing the trash? it's in ~/.local/share

Also, this problem happens on three different computers which use the hardy-updates repository.

[Sebastien Bacher (seb128)]

could you run /usr/lib/gvfs/gvfsd -r on a command line and then try to run /usr/lib/gvfs/gvfsd-network for example and note what is printed there? there is not so many changes between 0.2.3 and 0.2.4 and the update is working correctly for almost everybody, do you change your boxes in a special way?

[Viktor Kojouharov (vkojouharov)]

All the systems are generic ubuntu installs. All the update sources in the 'Software Sources' are enabled. And all of them were updated whenever updates were present. There's nothing out of the ordinary in them

As far as that testing goes, this output is for 0.2.4:
/usr/lib/gvfs/gvfsd-trash
Added new job source 0x8075408 (GVfsBackendTrash)
Queued new job 0x8076820 (GVfsJobMount)
send_reply, failed: 0
register_mount_callback, mount_reply: 0x8070e00, error: (nil)

/usr/lib/gvfs/gvfsd -r

And this is for 0.2.3:

/usr/lib/gvfs/gvfsd-trash
Added new job source 0x8075408 (GVfsBackendTrash)
Queued new job 0x8076820 (GVfsJobMount)
send_reply, failed: 0
register_mount_callback, mount_reply: 0x8072648, error: (nil)
backend_dbus_handler org.gtk.vfs.Mount:CreateFileMonitor
Queued new job 0x8086400 (GVfsJobCreateMonitor)
send_reply(0x8086400), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:QueryInfo
Queued new job 0x8088c10 (GVfsJobQueryInfo)
send_reply(0x8088c10), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:QueryInfo
Queued new job 0x8088c60 (GVfsJobQueryInfo)
send_reply(0x8088c60), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:CreateDirectoryMonitor
Queued new job 0x8086448 (GVfsJobCreateMonitor)
send_reply(0x8086448), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo
Queued new job 0x8086490 (GVfsJobQueryFsInfo)
send_reply(0x8086490), failed=1 (Operation not supported by backend)
backend_dbus_handler org.gtk.vfs.Mount:QueryInfo
Queued new job 0x8088cb0 (GVfsJobQueryInfo)
send_reply(0x8088cb0), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:Enumerate
Queued new job 0x808b008 (GVfsJobEnumerate)
send_reply(0x808b008), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo
Queued new job 0x80864d8 (GVfsJobQueryFsInfo)
send_reply(0x80864d8), failed=1 (Operation not supported by backend)

/usr/lib/gvfs/gvfsd -r
automounting...
Added new job source 0x8073418 (GVfsBackendBurn)
Queued new job 0x8073458 (GVfsJobMount)
send_reply, failed: 0
register_mount_callback, mount_reply: 0x80705d0, error: (nil)
backend_dbus_handler org.gtk.vfs.Mount:CreateDirectoryMonitor
Queued new job 0x8079038 (GVfsJobCreateMonitor)
send_reply(0x8079038), failed=1 (Not supported)

all tests were done while trying to access the Trash in nautilus

With 0.2.4, gvfs doesn't even know that nautilus is trying to use it.

[toneman77 (toni-eleftheriadis)]

I get the same errors on two machines running up-to-date hardy.

- Nautilus cannot access URIs begining with smb://, ssh://, ftp://, dav://, etc
- The "Connect to server" dialog contains the "Custom location" as the only service type

BUT

I just set up another user "test", opened nautilus and everything worked like expected. computer:// ssh:// ... all worked.
Don't know what's the real issue behind all that or how I can fix it for my original user.

[Dimitrios Symeonidis (azimout)]

toneman77, this is bringing us closer to resolving the issue, thank you.
can you send me the output of the 'id' command?
viktor, the same goes for you too...

[Viktor Kojouharov (vkojouharov)]

id
uid=1000(USER) gid=1000(USER) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),104(scanner),106(fuse),108(lpadmin),110(admin),115(netdev),117(powerdev),119(vboxusers),125(sambashare),1000(USER)

[Viktor Kojouharov (vkojouharov)]

p.s.:

I created a test user using the 'Desktop user' profile. That user had the same problem

My user has the default admin privileges

[toneman77 (toni-eleftheriadis)]

sure:
tone@tonesdell:~$ id
uid=1000(tone) gid=1000(tone) Gruppen=4(adm),10(uucp),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),104(scanner),108(lpadmin),114(netdev),116(powerdev),118(admin),121(vboxusers),127(sambashare),1000(tone),1001(vmc)

test@tonesdell:~$ id
uid=1001(test) gid=1002(test) Gruppen=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),29(audio),30(dip),44(video),46(plugdev),104(scanner),106(fuse),127(sambashare),1002(test)

[Dimitrios Symeonidis (azimout)]

I would have said it's the fuse group, but viktor is already a member of it...
By the way, my 'id' is:
uid=1000(azimout) gid=1000(azimout) groups=4(adm),20(dialout),21(fax),24(cdrom),29(audio),30(dip),44(video),46(plugdev),104(scanner),108(lpadmin),110(admin),115(netdev),117(powerdev),1000(azimout),1002(usrp)

And for me it works...

[Viktor Kojouharov (vkojouharov)]

It's not logical to be a permission problem, otherwise it wouldn't have worked with the 0.2.3 version of gvfs (unless of course the package does something with user's groups in itself)

[Dimitrios Symeonidis (azimout)]

You're right. What else then? Maybe the configuration files?

[toneman77 (toni-eleftheriadis)]

I also tried the "trick" on my desktop machine (adding a new user) and again it worked: (previous try was on my laptop)

user that doesn't work:
tone@tones:~$ id
uid=1000(tone) gid=1000(tone) Gruppen=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),100(users),109(lpadmin),111(scanner),114(admin),120(fuse),125(sambashare),1000(tone),1001(vboxusers)

user that works:
toneman77@tones:~$ id
uid=1001(toneman77) gid=1002(toneman77) Gruppen=4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),29(audio),30(dip),46(plugdev),100(users),111(scanner),1002(toneman77)

[Candle Jack (c-c-c-c-c-c-c-c-c-combobreaker)]

Had this exact problem. My dbus daemon wasn't exporting the $DBUS_SESSION_BUS_ADDRESS env var. You can test if this is your problem by checking:

echo $DBUS_SESSION_BUS_ADDRESS

If it's blank, this is your problem! See this comment for the fix:

https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/207157/comments/6

[Candle Jack (c-c-c-c-c-c-c-c-c-combobreaker)]

Quick fix is here
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/207157/comments/6
Apparently this happens to users who don't use gnome/kde/xfce. Probably should revert these changes:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/207157/comments/10

[toneman77 (toni-eleftheriadis)]

Candle Jack, thanks a lot. I was already getting disperate coz i reinstalled my laptop and the problem reappeared.

Your hint fixed the problem for me.

Thank you very much

[Sebastien Bacher (seb128)]

weird that the dbus environment is not correct, are you using GNOME or an another environment?

[Viktor Kojouharov (vkojouharov)]

the dbus problem it is.

Though I think the changes introduced in that version of the dbus package should be reverted, or at least something should be done to compensate for users not using KDE/GNOME/xfce

[Candle Jack (c-c-c-c-c-c-c-c-c-combobreaker)]

Sebastien: I'm using fluxbox, though I still use GDM to start the session.

[Sebastien Bacher (seb128)]

closing the bug after upstream discussion, nautilus could maybe display some error about the configuration but that's a broken user configuration and not really a bug