After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 532789 - file-roller crashes when modifying archive, data destroyed
file-roller crashes when modifying archive, data destroyed
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
2.22.x
Other Linux
: Normal critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2008-05-12 15:30 UTC by Pedro Villavicencio
Modified: 2008-06-02 17:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Pedro Villavicencio 2008-05-12 15:30:40 UTC 
This bug has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/file-roller/+bug/229517

"Reproduction steps are as follows:
1) Create a tar.gz archive with some large files (100M +) and some smaller text files (preferably in different subdirectories)
2) Select some of the large files and delete them
3) While file-roller is processing the archive (deleting files) browse to the subdirectory with the smaller text files
4) Double-click on a text file to view it
5) File-roller exits (crash?) without notification. The original archive is gone.
The unzipped (and unmodified) tar-file can be found from .fr-XXXXX temp directory, so the data is still (luckily) intact."

"Thread 1 (Thread 0xb6cf4720 (LWP 11420)):

+ Trace 197548

  • #0 check_child
    at fr-process.c line 731
  • #1 g_timeout_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 3443
  • #2 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #3 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #4 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #5 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 main
    at main.c line 241 






Comment 1


Paolo Bacchilega





          2008-06-02 17:33:56 UTC
        



This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.