File open in geany and other editors fails over ssh mount

[Jon Jenkins]

It seems that this has been a recurring bug in the last couple of years: I mount an SSH folder in Nautilus, try to open a file in Geany, and the program opens to a blank, untitled file instead. The thing is, I actually downgraded to 11.04 instead of 11.10 because of this bug, and it seems to have leeched its way back into 11.04 somehow.

I have looked at the source code and seen that it is patched for the various other incarnations of this bug that I've found. I've tried setting "use_safe_file_saving" to true in geany.conf, I've tried all sorts of different editors, etc.

This did not affect me on Friday. However, according to my apt log, I updated that same day. Here is the output of the update log:

Start-Date: 2012-03-23 11:32:51
Upgrade: thunderbird-locale-zh-cn:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts
1), thunderbird-locale-en-gb:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), linux-image-2.6.38-13-generic:amd64 (2.6.38-13.56, 2.6.38-13.57), thunderbird-locale-en-us:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), thunderbird:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), linux-headers-2.6.38-13-generic:amd64 (2.6.38-13.56, 2.6.38-13.57), libfreetype6:amd64 (2.4.4-1ubuntu2.2, 2.4.4-1ubuntu2.3), thunderbird-locale-es-ar:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), thunderbird-locale-es-es:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), libfreetype6-dev:amd64 (2.4.4-1ubuntu2.2, 2.4.4-1ubuntu2.3), libpng12-0:amd64 (1.2.44-1ubuntu3.2, 1.2.44-1ubuntu3.3), thunderbird-globalmenu:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), enigmail:amd64 (1.3.5-0ubuntu0.11.04.1~mtn1, 1.4-0ubuntu0.11.04.1~mtn1), linux-libc-dev:amd64 (2.6.38-13.56, 2.6.38-13.57), linux-headers-2.6.38-13:amd64 (2.6.38-13.56, 2.6.38-13.57), thunderbird-locale-zh-hans:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), thunderbird-locale-en:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), thunderbird-locale-es:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), thunderbird-locale-ru:amd64 (10.0.2+build1-0ubuntu0.11.04.1~mts1, 11.0+build1-0ubuntu0.11.04.1~mts1), libpng12-dev:amd64 (1.2.44-1ubuntu3.2, 1.2.44-1ubuntu3.3)
End-Date: 2012-03-23 11:34:44

The only thing of importance that looks like it was updated was the kernel.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gvfs 1.8.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-13.57-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Mon Mar 26 15:56:55 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: gvfs
UpgradeStatus: Upgraded to natty on 2011-11-22 (125 days ago)

[Sebastien Bacher (seb128)]

thank you for your bug report, if geany doesn't handle remote locations it's a bug in geany though

[Colomban Wendling (banw)]

The reporter said:

> I've tried all sorts of different editors

So I guess Geany isn't the only application suffering from the bug?

This said, note that Geany *does not* handle remotes locations by itself, and thus requires gvfs-fuse to be installed and running for such locations to work. This makes me think that it's not a bug in Geany, but rather one in gvfs-fuse, or simply a lack of gvfs-fuse in reporter's machine.

[Jon Jenkins (jon-50eaa)]

It worked for me up until a couple of days ago, and I have been using Geany for months to do my work with no problems whatsoever. So yes, I do have gvfs-fuse installed. I'll try compiling and running the newest version of Geany and see what happens.

I say it's a bug in gvfs because this bug has been a recurring issue for a couple of years now, and all of a sudden it's popped up again for apparently no reason whatsoever.

[Jon Jenkins (jon-50eaa)]

Actually, you can now close this bug. It started working automagically.

[Vadim Rutkovsky (roignac)]

Closing as Fix Released per latest comment