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 618909 - bad behavior when deleting files from encrypted 7-Zip archive
bad behavior when deleting files from encrypted 7-Zip archive
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
: 741025 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-05-17 18:12 UTC by leonardo.rolla
Modified: 2015-02-15 16:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description leonardo.rolla 2010-05-17 18:12:04 UTC
If you double-click an encrypted 7-Zip archive, file-roller asks you for the password and opens the archive.

The archive open, you can open the files, you can add more files or even whole folders. You can even copy-paste folders from the archive to elsewhere inside the same archive.

However the following operations lead to unexpected behavior:

- delete file/folder
prompts again for the password, then opens another file-roller window, which promps for the password on further time, and no change in the archive

- cut-paste inside the archive
prompts the password in loop, until you click cancel

- rename file/folder
"An error occurred while adding files to the archive."

Downstream:
https://bugs.launchpad.net/file-roller/+bug/575302
Comment 1 Alexander Kandaurov 2012-02-15 08:28:22 UTC
The same happens for .rar archives with file list encrypted. Also, if some file from the same archive was opened, it will be opened instead of deleting any file in the archive when trying to delete some. If none was opened, the archive itself will be opened in a new window.
Comment 2 André Klapper 2014-12-04 02:09:01 UTC
Wondering if this is a duplicate of bug 741025?
Comment 3 Declan McGrath 2014-12-05 11:25:57 UTC
*** Bug 741025 has been marked as a duplicate of this bug. ***
Comment 4 Paolo Bacchilega 2015-02-15 16:53:19 UTC
This is fixed in the current development version, the fix will be available in version 3.15.90 and 3.14.3.  Thanks for the bug report.