Bug#263263: Re: Bug#263263: file-roller: original tgz lost, temporary tar damaged and unreadable

Ricardo Mones Ricardo Mones <ricardo.mones@gmail.com>, 263263@bugs.debian.org
Wed, 4 Aug 2004 02:09:46 +0200


  Hi Sebastien,

On Wed, 04 Aug 2004 01:07:55 +0200, Sebastien Bacher <seb128@debian.org> wr=
ote:
> Le mardi 03 ao=FBt 2004 =E0 17:07 +0200, Ricardo Mones a =E9crit :
>=20
> > It happened with a big tgz file (~120 Mib (~230 MiB uncompressed)).
> > Extracting a file it hanged with the cancel button disabled, after a
> > while a new dialog announced something like "deleting files" so I close=
d
> > the window.
>=20
> How have you extracted this file ? Right click and "extract here" in
> nautilus ? Open the dialog and extract a file or the whole tgz in a
> dir ?

  I just double-clicked the tgz, file-roller was opened up, selected
the file I wanted and dragged it to another nautilus window, dropped
and waited (this machine is not fast and tarbal was big) and waited,
until the strange things started to happen :-)  then closed the main
file-roller window (metacity killed it of course), but the damage was
done :-(

> Do you have enough empty space on your disk to extract the file ?=20

  Yes, space is enough for more than twice the uncompressed file.

> Can you reproduce the problem ?

  Well, as I've lost the original tarball it will take some time to
get it again to trying to reproduce it :-)

> Sorry for all these questions but I've just made some tests here and I
> don't have any problem. The cancel button works and file-roller never
> deleted a file. I'm tagging this bug as unreproducible for the moment.

  No problem, I'll keep you informed when I can grab the original file agai=
n.
=20
> > Anyway I think the original files shouldn't be altered under any
> > circumstance (except by user request), so I've set the severit to grave=
.
>=20
> Yes, sure. The problem is to get a way to reproduce this bug to fix
> it ...

  Of course, I'm on it :-)
=20
  Best regards,
--=20
Ricardo Mones.