Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 335316 - gnome-base/gvfs-1.6.3: sftp fails with openssh 5.6
Summary: gnome-base/gvfs-1.6.3: sftp fails with openssh 5.6
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL: http://bugzilla.gnome.org/show_bug.cg...
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2010-08-30 19:06 UTC by Guillaume ZITTA
Modified: 2010-09-27 21:55 UTC (History)
7 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
log for reproducing on new user account (test-xsession-errors,1.77 KB, text/plain)
2010-09-04 08:07 UTC, Hans Nieser
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Guillaume ZITTA 2010-08-30 19:06:27 UTC
after updating openssh from 5.5_p1-r2 to 5.6_p1, sftp:// in nautilus stops to work

Reproducible: Always

Steps to Reproduce:
1.have gvfs 1.6.3 installed (I haven't tryed older gvfs)
2.have openssh 5.6_p1 installed
3.gvfs-mount sftp://user@host

Actual Results:  
Error mounting location: Erreur lors de la lecture depuis unix : Erreur d'entrée/sortie

BTW, unseting LANG and LANGUAGE envvars failed to avoid translation.
"Erreur lors de la lecture depuis unix : Erreur d'entrée/sortie" means
Error while reading from unix : I/O error

Expected Results:  
$ ls .gvfs/
sftp on host

I have tried to recompile gvfsd in order to avoid link inconsistency (like revdep rebuild) : same error
rollback to openssh 5.5_p1-r2 worked instantly (whitout recompile gvfs)
Comment 1 Hans Nieser 2010-09-02 05:39:33 UTC
Also ran into this issue on two seperate gentoo machines (~amd64) after updating world recently. The precise error in english/default locale is "Error reading from unix: Input/output error".

Issue remains after updating to openssh-5.6_p1-r1, downgrading tot 5.5_p1-r2 like Guillaume did also makes it work again for me.
Comment 2 Pacho Ramos gentoo-dev 2010-09-03 19:43:04 UTC
Please try if you are able to reproduce on a new created user account and, in that case, attach ~/.xsession-errors file just after reproducing
Comment 3 Hans Nieser 2010-09-04 08:05:02 UTC
I can reproduce it on a new account, unfortunately the .xsession-errors file doesn't seem to contain anything useful (I'll attach it anyway, just in case)
Comment 4 Hans Nieser 2010-09-04 08:07:14 UTC
Created attachment 245926 [details]
log for reproducing on new user account
Comment 5 Pacho Ramos gentoo-dev 2010-09-04 14:00:30 UTC
Looks like this could be an upstream problem since also affects people in other distributions:
http://bugs.archlinux.org/task/20737
Comment 6 Mike Auty (RETIRED) gentoo-dev 2010-09-09 12:51:02 UTC
As far as I can tell, this is some kind of a timing issue, since when stepping through the handle_login in gvfsd-sftp with gdb everything works fine.  Running strace against it doesn't show a significant difference between the two ssh processes, and indeed they both end up waiting for a password-prompt/attempting publickey auth.  However, it appears that 5.6 opens /proc/<pid>/fd and then closes an additional file descriptor and it's not clear if that's causing the problem.

I'm happy to dig a little deeper, but I'm not sure where I should be looking, how I should be testing, so I'm open to suggestions?  Also does anyone have an upstream bug number for this yet?
Comment 7 Pacho Ramos gentoo-dev 2010-09-09 13:33:02 UTC
I have been searching in upstream bugzilla without success, could any of the affected people open it and post link here?

Thanks
Comment 8 Mike Auty (RETIRED) gentoo-dev 2010-09-09 15:29:09 UTC
Ok, it's gnome bug 629184.  I haven't reported it to openssh yet, since it's not clear they're doing anything wrong.

http://bugzilla.gnome.org/show_bug.cgi?id=629184
Comment 9 Pacho Ramos gentoo-dev 2010-09-09 15:41:37 UTC
Thanks
Comment 10 Gilles Dartiguelongue (RETIRED) gentoo-dev 2010-09-27 21:55:31 UTC
just commited 1.6.4 to the tree which ships with the fix. Thanks for reporting.