Comment 74 for bug 215499

Sebastien Bacher wrote:
> nautilus can have several issues, why do you insist to want to use this
> code issue which was a libglib bug and has been fixed now? bug #247980
> seems to describe this one so you should rather comment on this one, not
> sure why the firefox maintainer didn't reply but I expect there is just
> too many bugs being open against firefox for him to work on everything
>
>
I expect the Firefox Maintainer hasn't responded to it because copying
files saves the last mtime stamp from the site when doing a copy with
Firefox 2 or Firefox 3 working with Nautilus 2.20.0 under Ubuntu 7.10
and the last mtime is lost when doing the same operation from either
Firefox 2 or Firefox 3 when copying to a folder in Nautilus 2.22.3 under
Ubuntu 8.04

To make sure this behavior is as reported I have two machines, one with
Ubuntu 7.10 and Firefox 2 and Firefox 3 and another separate machine
with Ubuntu 8.04 and Firefox 2 and Firefox 3.

Why should the Firefox maintainer think there is something wrong with
Firefox when the two versions do the job with Nautilus 2.20.0 under
Ubuntu 7.10 but not with Nautilus 2.22.3 under Ubuntu 8.04? What looks
like the common point of failure among these programs?

I'd love to have you explain it to me offside if you want. The
questions might be "In a drag and drop operation who ends up taking
charge of the copy function, the sender, Firefox 2 or 3, or the
receiver, Nautilus? If it's the sender, Firefox 2 or 3, then why do
they send different information to Nautilus 2.20.0 and Nautilus 2.22.3?
If it's the receiver, then when after 2.20.0 did Nautilus stop asking
for the complete information about the files coming from Firefox 2 or 3?"

No, sorry, I haven't tried backporting Nautilus 2.22.3 to Ubuntu 7.10 yet.

<email address hidden>.