Comment 19 for bug 282298

At the moment it's giving me the "Transport endpoint is not connected" message when I try to cd into .gvfs but previously I could do an ls and see the shares listed. But when I cd into one I got an error message and the share disappeared. The same as you I believe. I'm out of my depth here but looking at your attached crash log it seems as if things are crashing when "fuse_add_direntry ()" called. I'm guessing this function adds a directory entry and so is called multiple times to populate a directory (duh!) in this case the share folder, with the real share contents from samba. If it's crashing out here it must be passing corrupt (or null?) paremeters or something which I guess would have to be coming from the smb client like that. Maybe the last character of the filename missing thing is relevant here? When I do "smbclient -N //server/share" then an ls at the prompt I also get all the filenames in the list returned missing the last character. Whereas if I do this on one of the working shares on my gutsy box the filenames are as they should. I think it's too much of a coincidence for these not to be related. I hypothesize filenames from 2.2.8 samba servers are somehow corrupted or incomplete and when this info is fed into gvfs to populate the directories it chokes and crashes on the first entry. That's my uneducated guess anyway!