FS#10615 - SSH and SMB connections are broken after GVFS/Nautilus upgrade

Attached to Project: Arch Linux
Opened by Thayer Williams (thayer) - Sunday, 08 June 2008, 23:23 GMT
Last edited by Thayer Williams (thayer) - Friday, 15 August 2008, 00:29 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Recent gvfs updates seem to have broken remote connections within nautilus.

The following errors are reported:

Couldn't display "sftp://thayer@firedrake".
Nautilus cannot handle sftp: locations.

Couldn't display "smb://athlon/c$/c$".
Nautilus cannot handle smb: locations.

Additional info:

gvfs 0.2.4-1, 0.2.5-1 and 0.2.5-2
nautilus (2.22.3-1 through 2.22.5-1)

Steps to reproduce:

1. Open Nautilus
2. Enter an SSH or SMB address in the location bar
This task depends upon

Closed by  Thayer Williams (thayer)
Friday, 15 August 2008, 00:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  *squashed*
Comment by Jan de Groot (JGC) - Monday, 09 June 2008, 06:53 GMT
Could you try force-downgrading gvfs to see if that fixes your problem? I have this working on x86_64.
Comment by Thayer Williams (thayer) - Monday, 09 June 2008, 15:03 GMT
Confirmed. Downgrading (pacman -Ud) to gvfs-0.2.3-1 fixes the issue.

In addition to GVFS errors above, Nautilus stopped loading entirely yesterday. When started from a terminal it spat:

seahorse nautilus module initialized
Segmentation fault
Comment by Jon Kapla (Xappe) - Friday, 13 June 2008, 21:02 GMT
I have the same issue here on a 686 setup. Haven't tried downgrading gvfs yet, but i'll try that as soon as possible.

To add some more information: All the choices except "Custom location" in the "Connect to server..." dialogue in nautilus has disappeared. And I get the same error as thayer with my sftp shortcuts.
Comment by Jan de Groot (JGC) - Thursday, 19 June 2008, 12:23 GMT
This is what I see in my dmesg on amd64:
gvfs-fuse-daemo[21903] general protection ip:7f4c5ec904ca sp:7fff688b3c10 error:0 in libpthread-2.8.so[7f4c5ec88000+16000]

Looks like gvfs-fuse-daemon needs a rebuild for the new glibc, or needs a patch to fix this segfault.
Comment by Jon Kapla (Xappe) - Thursday, 26 June 2008, 22:38 GMT
downgrading to gvs 0.2.3-1 worked
Comment by Thayer Williams (thayer) - Friday, 04 July 2008, 03:17 GMT
I'm really surprised more users haven't commented about these issues in the forums. The latest updates (nautilus 2.22.4-1 and gvfs 0.2.5-1) do not fix this issue for any 1 of our 3 workstations/notebooks. All three are 686-based and none of them can open SSH/SMB connections.

Downgrading to gvfs 0.2.3-1 again did the trick.

Jan, is there anything further I can do to assist with this? I'd be more than happy to help (jabber: thayerw AT gmail)
Comment by Will Smith (Factory) - Friday, 18 July 2008, 16:53 GMT
Confirming this bug with v 0.2.5-1 of gvfs. Downgrading to 0.2.3 solves this issue.
Comment by Thayer Williams (thayer) - Tuesday, 22 July 2008, 03:12 GMT
Sorry Jan, I re-opened this task because the latest version (0.2.5-2) does not remedy the issue. I rebooted some time after the update and then tried to open nautilus, which seg faulted numerous times. After logging in/out again it finally opened, but the gvfs problems are back: Can't handle sftp/smb locations, blah blah.
Comment by Jon Kapla (Xappe) - Thursday, 24 July 2008, 14:38 GMT
yes, I still see the same behaviour with gvfs 0.2.5-2 as well. I've never seen any nautilus segfaults though, just the inability to connect to remote machines.
Comment by Jan de Groot (JGC) - Thursday, 24 July 2008, 14:49 GMT
The bug that 0.2.5-2 fixed seems to be another bug then. I used to have a segfaulting gvfs-fuse-daemon which is fixed by upgrading to 0.2.5-2. I have no idea why SSH/SMB aren't available on your systems or why nautilus crashes, as I can't reproduce this bug on 2 systems running x86_64 and a laptop running i686.
Comment by Thayer Williams (thayer) - Thursday, 14 August 2008, 03:34 GMT
I decided to test 0.2.5-2 today after wiping a bunch of gtk-related stuff in my home directory and I'm glad to say it's working great now. There must have been something hanging around that was conflicting with the new changes.

Unless anyone has any objections, I'm going to close this report tomorrow.
Comment by Jon Kapla (Xappe) - Thursday, 14 August 2008, 15:13 GMT
What exactly did you remove to get this working again?
Comment by Thayer Williams (thayer) - Thursday, 14 August 2008, 15:52 GMT
To be honest, it's hard to say for sure because I was doing general housekeeping on my ~/ dir so much of what I removed probably had nothing to do with gvfs. The only dirs that seemed related at the time were:

~/.nautilus (contained metafiles named after previous ssh/smb connections)
~/.cache (probably from thunar)

At any rate, it's definitely working now as I've already made a few SSH and samba connections this morning.

EDIT: Looking through my pacman logs, it could have been the gnome-vfs upgrade (2.22.0-3 -> 2.22.0-4) I performed last night as well. No clue.
Comment by Jon Kapla (Xappe) - Thursday, 14 August 2008, 16:04 GMT
OK, thank you! I'll do some fiddling around tonight when I get home. I'll put a note here if I find the right spot, so that others with the same problem can get it fixed.
Comment by Jon Kapla (Xappe) - Thursday, 14 August 2008, 21:11 GMT
Seems this was a dbus issue for me. Realized it all worked with "dbus-launch nautilus --no-desktop". I haven't had to tinker with dbus before to get nautilus to connect remotely, but i'm glad I figured it out. Now everything works.

Loading...