Copying from FTP freezes

[Valentin Neacsu]

Actually there are 2 bugs in one, might be related:
First, when logging in to my FTP, the 1st attempt always fails and then logging in works as expected. After that I can upload and delete files, but I can not copy files from FTP to my laptop. It stays like the attached picture, even after clicking the Cancel button.

valentin@valentin-laptop:~$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04
valentin@valentin-laptop:~$ apt-cache policy gvfs
gvfs:
  Installed: 1.2.2-0ubuntu1
  Candidate: 1.2.2-0ubuntu1
  Version table:
 *** 1.2.2-0ubuntu1 0
        500 http://archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

[Sebastien Bacher (seb128)]

thank you for your bug report, can you open it on bugzilla.gnome.org too where the software written will read about the issue?

[Valentin Neacsu (valentin.neacsu)]

Posted the bug: http://bugzilla.gnome.org/show_bug.cgi?id=580124

[Valentin Neacsu (valentin.neacsu)]

Also posted the 2nd bug: http://bugzilla.gnome.org/show_bug.cgi?id=580125

[Valentin Neacsu (valentin.neacsu)]

From the bugzilla page:
"Could you please try this:
in daemon/gvfsbackendftp.c find the line that sends "OPTS UTF8 ON" and replace
the 0 with RESPONSE_PASS_500.
Build, install and test if this solves the problem?"

Any clue how to do that? I can compile and install, but I have no clue which package in Ubuntu that is. Also I'd appreciate it if you could give me a .deb to test instead of installing all the build dependencies myself.

[Sebastien Bacher (seb128)]

the issue is fixed in karmic now

[Valentin Neacsu (valentin.neacsu)]

Will it be backported to Jaunty?

[Sebastien Bacher (seb128)]

not likely, there has been no other request for that and that's not a high priority bug or a security issue

[mabawsa (mabawsa)]

Just upgraded to Jaunty and I am afflicted by this bug as well on all my machines. I will try to compile the fix.
This is quite a nasty bug as it locks the gvfs FTP backend.
I think it should be backported to Jaunty.

[mabawsa (mabawsa)]

This is an important bug as it basically stops FTP functionality in Ubuntu!
Anyway, here are the compile options I used to get FTP working:
sudo apt-get build-dep gvfs
apt-get source gvfs
tar -xzvf gvfs_1.2.2.orig.tar.gz
rm gvfs_1.2.2.orig.tar.gz
rm gvfs_1.2.2-0ubuntu2*
sed 's/ftp_connection_send (conn, 0, "OPTS UTF8 ON");/ftp_connection_send (conn, RESPONSE_PASS_500, "OPTS UTF8 ON");/' gvfs-1.2.2/daemon/gvfsbackendftp.c > /tmp/gvfsbackendftp.c
mv /tmp/gvfsbackendftp.c gvfs-1.2.2/daemon/gvfsbackendftp.c
cd gvfs-1.2.2/
./configure
make
sudo make install

I want to put this on a ppa so I tried pbuilder https://wiki.ubuntu.com/PbuilderHowto.
However it all got a bit greasy so if anybody can point me to a tutorial on how to create these multiple debs from one source I will try again.

For now I have FTP capabilities again in Jaunty.

[mabawsa (mabawsa)]

A fix has not been released for Jaunty only Karmic. This bug basically renders FTP useless in Jaunty. I think its importance should be raised as Karmic is not gonna be stable till October.

[Sebastien Bacher (seb128)]

don't reopen a closed bug because you have a similar issue but open a new one

[Sebastien Bacher (seb128)]

did you also try karmic before reopening the bug? having it closed if it's fixed in karmic is correct a jaunty task can be opened if required but nautilus is not a strong ftp client in any case so that's not a stopper you could use gftp for example

[Valentin Neacsu (valentin.neacsu)]

Then it's only fair that you open a jaunty task for it.

[mabawsa (mabawsa)]

With all due respect Sebastien,

1 The bug I have was exactly the same as Valentin's. So if I open another bug then it is a duplicate. Fairly pointless....
2 The bug was opened on 9.04. So a fix has NOT been released; this is misleading.
3 By default Nautilus handles FTP and it used to make a decent job of it. So this should function by default in ubuntu. A strong FTP client is a matter of opinion, I like the way gvfs-ftp backend integrates into the gnome shell. Most of the time I use the command line for FTP'ing but many of the other people in my charge do not. So I have had to fix about 10 machines today.
4 Karmic is alpha NOT a release, therefore why should I try it to fix a Jaunty issue by upgrading to Karmic, and be ladened with a bunch of development bugs for at least 2-3 months? (this is why I waited to upgrade to Jaunty till now).
5 The bug is so easy to fix. Indeed I want to create the debs for a ppa if nobody else wants to fix it on the official release.

So I suggest you re-open the bug and help fix it for the official release, or mark it as wont fix for Jaunty.

All best

[Valentin Neacsu (valentin.neacsu)]

It's sad to see this attitude, Sebastien. I helped fix the bug upstream, just as you have previously asked me to, and now you refuse to port the bug fix that I helped develop and that affects me. What kind of bug-reporting reward is that? Is this how you encourage your community to help? You previously said there were not enough requests for a fix - poor excuse IMO; now you have enough requests to fix it. What is the reason for not fixing it for the release I filed the bug report for?

[Sebastien Bacher (seb128)]

The reason to not backporting every small change to stable is an manpower one, those backports need testing and work and that's efforts we don't put on getting the next version working correctly, all the bugs fix can't be backported to stable, only major issues and security issues are fixed in stable. Nautilus is not the best ftp client around and will not be with this change if you need to connect to a ftp there is other client available that you can use to workaround the issue easily, the bug is fixed in karmic which means you work has been useful and appreciated so there is no reason to add doubtful comments there

[mabawsa (mabawsa)]

OK Sebastian can I ask a simple question.
What is the default FTP system of Ubuntu?
Gvfs-FTP backend? It should have the least bugs.
Your notions on what constitutes a strong FTP client have nothing to do with it.

This bug is NOT fixed in Jaunty as per the original bug report.
Please mark it as WONT FIX as marking it as fixed is dishonest.

Oh by the way you noticed I opened a new bug as per your instructions in comment 12, "don't reopen a closed bug because you have a similar issue but open a new one". Sorry if this was inappropriate to follow your instruction.

It pretty funny that the counting the time you have wasted on this bug you could have had a properly fixed package in testing repos :).

Allbest

[Sebastien Bacher (seb128)]

> What is the default FTP system of Ubuntu?
> Gvfs-FTP backend? It should have the least bugs.
> Your notions on what constitutes a strong FTP client have nothing to do with it.

Nobody argued that gvfs-ftp should have extra bugs, it's just not a strong client for ftp now and it's not worth investing too much efforts fixing side issues in jaunty when it will not be really useful anyway, if you need a ftp client better to use gftp or lftp which handle passive mode, file permissions on the server etc

> This bug is NOT fixed in Jaunty as per the original bug report.
> Please mark it as WONT FIX as marking it as fixed is dishonest.

the way opensource projects are working is that bugs are closed when the fix is available in the current version (karmic for ubuntu), you can request a jaunty nomination if you think a backport is required though

> Oh by the way you noticed I opened a new bug as per your instructions in comment 12, "don't reopen a closed bug because you have a similar issue but open a new one". Sorry if this was inappropriate to follow your instruction.

you reopened the bug which suggested that your issue was not fixed in karmic where this one is, your bug change was confusing since you should have requested a jaunty nomination if what you wanted is to get the change in jaunty

> It pretty funny that the counting the time you have wasted on this bug you could have had a properly fixed package in testing repos :).

Commenting there took a few minutes, getting the change in stable would mean building the change, figuring how to set up a buggy server somewhere, having the change reviewed by the sru team and tested by the busquad to make sure it doesn't break anything, for that they would have to set up and test nautilus on a variety or ftp servers which is not a trivial work. The efforts are just not worth the gain for a stable update, we don't have the manpower to fix the thousand of bugs fixed in karmic to jaunty too anyway and spending all those ressources to backport changes would mean they would not be invested to fix other issues for karmic. Not having nautilus working on a specific ftp server for you might be annoying but it's easy enough to use gftp for example and wait for karmic that bug is neither a stopper for most users, nor a security issue nor something you can't workaround easily

[Valentin Neacsu (valentin.neacsu)]

Sebastien, as far as ubuntu.com is concerned, Ubuntu 9.04 (jaunty) is the *current* version. There's no mention about karmic, which I suppose is the development version. Regular users don't really care about development versions, so how about you fix reported bugs for the *current* release, and not for some future unstable development release? Otherwise I really can't see the benefit of reporting bugs any more.

[Sebastien Bacher (seb128)]

the code is being changed in the currently work version, ie karmic, not in the stable version which by definition is stable, ie doesn't change. it's useful to report bugs because issues are fixed for the next version then (ie in 6 months you will upgrade and get ton of issues fixed and new features added too) and importants fixes are backported to stable

[mabawsa (mabawsa)]

yeah karmic is not the current release. The bug has not been fixed on the current release 9.04.
Also every one of my ftp copy attempts fail on nautilus without Valentin's patch.
Most users would also expect ftp to work in nautilus out of the box in the current release.
All my FTP servers are passive and since fixing gvfs the connections work perfectly.
So how do I go about nominating the fix for the CURRENT release?

Allbest

[Sebastien Bacher (seb128)]

you can also note that this is true for any OS, you will not get microsoft shipping you a new vista CD or an internet upgrade for each win7 bug they fix now by example

[mabawsa (mabawsa)]

U r being a bit silly now ;)
MS is a leviathan the joy of using ubuntu is that it moves fast when needed.
I assumed out-of-the-box FTP connections would be a desirable in the current release and be part of the stability measure of a release (no matter what you think of gvfs I like the way it integrates into the gnome shell).
OK I'll try to learn how to ppa this weekend.
As I have no clue how to nominate this for the current release except by filing a bug report as Valentin did for Jaunty already, and you obviously have no desire to try to fix this because of the extra work you should mark it as WONT FIX. If I am successful in getting the ppa version I can then link to this.

What do you think Sebastien?

[mabawsa (mabawsa)]

Maybe I should read the wiki.
lol

[Sebastien Bacher (seb128)]

There is no need to start being insulting and call people stupid, we get thousand bugs every week and there is a small team of volunteers working on those, the stable update policy is strict and this change will probably not be accepted for jaunty since there is only one bug requesting for the fix, the issue is easy to workaround using an another software and is not a security issue. Now I've been spending enough time discussing that here and trying to explain why every code change can't be applied to a stable version, you are welcome to work on a ppa version or a on stable update candidate and go through the procedure but I'm not going to spend efforts on a change which will probably not be accepted there.
To nominate a fix for jaunty you can use the button bellow the tasks table

[mabawsa (mabawsa)]

I am soo sorry you feel insulted. I was trying to lighten up the dialogue. I think ubuntu is fantastic and the support is far superior to Microsoft as one can actually become involved (thus the silly comment). I am fairly new to all of this, but want to volunteer more having only used ubuntu for 18 months. It has put the fun back into computing and I am trying to switch as many people as possible into using Linux (almost 20 people now). However it is little bugs like this that turn most users off, for example I think a similar bug or regression in Windows explorer (a far less superior FTP client than GVFS FTP backend) would be fixed post haste by Redmond.
I release that you and other developers are doing a Sterling job so please accept my humblest apologies. I am looking forward to the ppa learning curve ahead.

Thanks