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 686655 - File Roller fails when tryings create zip files if is in "maximum" compression level.
File Roller fails when tryings create zip files if is in "maximum" compressio...
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
3.6.x
Other Linux
: Normal major
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2012-10-22 17:33 UTC by Muflone
Modified: 2012-10-28 08:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
An error occurred while adding files to the archive (10.12 KB, image/png)
2012-10-22 17:33 UTC, Muflone 		Details

Description Muflone 2012-10-22 17:33:53 UTC 
Created attachment 227015 [details]
An error occurred while adding files to the archive

When I try to create a new zip file with file roller  with maximum compression level it has an error. The problem can be fixed changing the compression level from "maximum" to "normal".

Steps to Reproduce:
1. Close File Roller
2. Install dconf-editor (if isn't installed) or use the command line method (I don't know how to do it).
3. Open Dconf-editor.
4. Go to "org.gnome.FileRoller.General" (without quotes).
5. Change "normal" for "maximum" in the "compression-level" key.
6. Close dconf-editor.
7. Open File Roller.
8. Create a new ZIP File.
9. Try to add a new file to the archive.
10. The message "An error occurred while adding files to the archive" appears

Expected Result:
The archive file is created and compressed with the maximum compression level.

Tested environment:
OS Linux 3.6.2-1-pae #1 SMP PREEMPT Mon Oct 15 21:12:48 EDT 2012 i686 GNU/Linux
Distribution Arch Linux i686
file-roller 3.6.1.1, Copyright © 2001-2012 Free Software Foundation, Inc.
Comment 1 Paolo Bacchilega 2012-10-28 08:44:53 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.