file-roller: original tgz lost, temporary tar damaged and unreadable

Automatically imported from Debian bug report #263263 http://bugs.debian.org/263263

Message-ID: <email address hidden>
Date: Tue, 3 Aug 2004 17:07:56 +0200
From: Ricardo Mones <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: file-roller: original tgz lost, temporary tar damaged and unreadable

Package: file-roller
Version: 2.6.2-1
Severity: grave
Justification: causes data loss

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 closed
the window.

Now the original file has gone and I have a quarter GiB of unreadable data,
file-roller says:
tar: Saltando a la siguiente cabecera
tar: El archivo contiene cabeceras base 64 obsoletas
tar: Salida con error demorada desde errores anteriores
(roughly: skipping to next header, archive has obsolete base 64 headers
and the famous: Error exit delayed from previous errors)

If needed I probably can provide the file for testing purposes (they're
mostly pdf articles) but it will take some days as I've lost it, and
currently have no access to the backup machine (my University network is
down).

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.

regards,

P.S.: please CC me to the reply-To address, as I'm unable to access my
normal account.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.4.26-1-k6
Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro (ignored: LC_ALL set to es_ES@euro)

Versions of packages file-roller depends on:
ii bzip2 1.0.2-1 A high-quality block-sorting file
ii gconf2 2.6.2-1 GNOME configuration database syste
ii gzip 1.3.5-9 The GNU compression utility
ii libart-2.0-2 2.3.16-6 Library of functions for 2D graphi
ii libatk1.0-0 1.6.1-2.1 The ATK accessibility toolkit
ii libaudiofile0 0.2.6-4 Open-source version of SGI's audio
ii libbonobo2-0 2.6.2-5 Bonobo CORBA interfaces library
ii libbonoboui2-0 2.6.1-1 The Bonobo UI library
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libesd0 0.2.29-1 Enlightened Sound Daemon - Shared
ii libgconf2-4 2.6.2-1 GNOME configuration database syste
ii libgcrypt7 1.1.90-9 LGPL Crypto library - runtime libr
ii libglade2-0 1:2.4.0-1 Library to load .glade files at ru
ii libglib2.0-0 2.4.4-1 The GLib library of C routines
ii libgnome-keyring0 0.2.1-2 GNOME keyring services library
ii libgnome2-0 2.6.1-8 The GNOME 2 library - runtime file
ii libgnomecanvas2-0 2.6.1.1-2 A powerful object-oriented display
ii libgnomeui-0 2.6.1.1-3 The GNOME 2 libraries (User Interf
ii libgnomevfs2-0 2.6.1.1-5 The GNOME virtual file-system libr
ii libgnutls10 ...

Message-Id: <1091574475.6442.28.camel@seb128>
Date: Wed, 04 Aug 2004 01:07:55 +0200
From: Sebastien Bacher <email address hidden>
To: Ricardo Mones <email address hidden>, <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#263263: file-roller: original tgz lost, temporary tar
 damaged and unreadable

tag 263263 unreproducible
thanks

Le mardi 03 ao=FBt 2004 =E0 17:07 +0200, Ricardo Mones a =E9crit :

> 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 closed
> the window.

Hi,

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 ?=20
Do you have enough empty space on your disk to extract the file ? Can
you reproduce the problem ?

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.

> 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.

Yes, sure. The problem is to get a way to reproduce this bug to fix
it ...=20

Cheers,

Sebastien Bacher

Message-ID: <email address hidden>
Date: Wed, 4 Aug 2004 02:09:46 +0200
From: Ricardo Mones <email address hidden>
To: Sebastien Bacher <email address hidden>
Cc: <email address hidden>
Subject: Re: Re: Bug#263263: file-roller: original tgz lost, temporary tar damaged and unreadable

  Hi Sebastien,

On Wed, 04 Aug 2004 01:07:55 +0200, Sebastien Bacher <email address hidden> 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.

Message-Id: <1091605551.6432.0.camel@seb128>
Date: Wed, 04 Aug 2004 09:45:51 +0200
From: Sebastien Bacher <email address hidden>
To: Ricardo Mones <email address hidden>, <email address hidden>
Subject: Re: Bug#263263: Re: Bug#263263: file-roller: original tgz lost,
 temporary tar damaged and unreadable

Le mercredi 04 ao=FBt 2004 =E0 02:09 +0200, Ricardo Mones a =E9crit :
> Hi Sebastien,

> until the strange things started to happen :-) then closed the main
> file-roller window (metacity killed it of course), but the damage was
> done :-(

You have killed the window ? If you are killing an app in the middle of
its work it's not really a bug due to the app ..

Cheers,

Sebastien Bacher

Message-ID: <email address hidden>
Date: Wed, 4 Aug 2004 10:21:03 +0200
From: Ricardo Mones <email address hidden>
To: Sebastien Bacher <email address hidden>
Cc: <email address hidden>
Subject: Re: Re: Bug#263263: Re: Bug#263263: file-roller: original tgz lost,
 temporary tar damaged and unreadable

On Wed, 04 Aug 2004 09:45:51 +0200, Sebastien Bacher <email address hidden> wr=
ote:
> Le mercredi 04 ao=FBt 2004 =E0 02:09 +0200, Ricardo Mones a =E9crit :
> > Hi Sebastien,
>=20
> > until the strange things started to happen :-) then closed the main
> > file-roller window (metacity killed it of course), but the damage was
> > done :-(
>=20
> You have killed the window ? If you are killing an app in the middle of
> its work it's not really a bug due to the app ..

  The bug is deleting the original tarball. I understand perfectly all
temporary files created are damaged due killing the app in the middle
of processing, but that shouldn't affect the original compressed file.
That's the data loss I'm referring to. You may retitle the bug if you
prefer. I put that second part because it surprised me to found the
file uncompressed but damaged.

I don't know about file-roller internals, but seen that I supposed it
had uncompressed the whole tarball to speed up processing, which is
perfectly ok. Founding that one was also damaged double-surprised me
:-)

  regards,
--=20
Ricardo Mones.

Message-Id: <1091608092.6432.19.camel@seb128>
Date: Wed, 04 Aug 2004 10:28:12 +0200
From: Sebastien Bacher <email address hidden>
To: Ricardo Mones <email address hidden>, <email address hidden>
Subject: Re: Re: Bug#263263: Re: Bug#263263: file-roller: original tgz
 lost, temporary tar damaged and unreadable

Le mercredi 04 ao=FBt 2004 =E0 10:21 +0200, Ricardo Mones a =E9crit :

> That's the data loss I'm referring to. You may retitle the bug if you
> prefer. I put that second part because it surprised me to found the
> file uncompressed but damaged.

No, it's fine, it was just to be sure. That's still weird since file-
roller use standard command line commands to do the job and should not
modify the original archive.

Cheers,

Sebastien Bacher

Message-Id: <email address hidden>
Date: Thu, 5 Aug 2004 16:56:20 +0200
From: Josselin Mouette <email address hidden>
To: <email address hidden>
Subject: severity of 263263 is important

# Automatically generated email from bts, devscripts version 2.7.95.1
severity 263263 important

Message-ID: <email address hidden>
Date: Fri, 6 Aug 2004 10:38:41 +0200
From: Ricardo Mones <email address hidden>
To: Sebastien Bacher <email address hidden>
Cc: <email address hidden>
Subject: Re: Re: Re: Bug#263263: Re: Bug#263263: file-roller: original tgz lost,
 temporary tar damaged and unreadable

On Wed, 04 Aug 2004 10:28:12 +0200, Sebastien Bacher <email address hidden> wr=
ote:
> Le mercredi 04 ao=FBt 2004 =E0 10:21 +0200, Ricardo Mones a =E9crit :
>=20
> > That's the data loss I'm referring to. You may retitle the bug if you
> > prefer. I put that second part because it surprised me to found the
> > file uncompressed but damaged.
>=20
> No, it's fine, it was just to be sure. That's still weird since file-
> roller use standard command line commands to do the job and should not
> modify the original archive.

  Well, I've got the original big tarball again and have tested
several times in several ways and I'm unable to reproduce the weird
behaviour I described originally :-(

  I can confirm drag'n'drop is severely damaged, but that has already
been filed on #210235,
so I'll refrain from using it.

  I was going to downgrade severity to normal, but noticed joss has
already set it to important, but looks also like an automated email,
do you know why? (the only reason I can imagine is that tagging a RC
bug unreproducible auto-downgrades it to a non-RC level, but I wasn't
aware of that BTS procedure).

  thanks and best regards,
--=20
Ricardo Mones.

Message-Id: <1091782837.6778.20.camel@seb128>
Date: Fri, 06 Aug 2004 11:00:37 +0200
From: Sebastien Bacher <email address hidden>
To: Ricardo Mones <email address hidden>
Cc: <email address hidden>
Subject: Re: Re: Re: Bug#263263: Re: Bug#263263: file-roller: original tgz
 lost, temporary tar damaged and unreadable

Le vendredi 06 ao=FBt 2004 =E0 10:38 +0200, Ricardo Mones a =E9crit :

> Well, I've got the original big tarball again and have tested
> several times in several ways and I'm unable to reproduce the weird
> behaviour I described originally :-(

Ok, I can't reproduce it neither ...

> already set it to important, but looks also like an automated email,
> do you know why?

I think he used the "bts" command line, it's a part of the devscrips
package. "bts severity 263263 important" and you get this result (you
need to have your local MTA working).

Cheers,

Sebastien Bacher

unreproducible -> severity minor

We don't have a NEEDINFO state, I don't think it's useful to keep it open, we
will probably do nothing about that since nobody can reproduce the problem. I'm
closing it, if somebody disagree please let me know.