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 779941 - Have archive options such as encryption in Nautilus's compression dialog
Have archive options such as encryption in Nautilus's compression dialog
Status: RESOLVED DUPLICATE of bug 773366
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-03-12 14:51 UTC by Inactive account
Modified: 2017-03-12 15:03 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Inactive account 2017-03-12 14:51:11 UTC
My system runs the latest version of Arch and GNOME 3.22 and I have found that in this version of GNOME if one right-clicks on a file or folder or a group of them and goes to "Compress..." that they are provided with 3 different formats to compress into, however the options which allow splitting of large archives into smaller ones as well as the ability to encrypt them with a password are gone. This can obviously still be done through the CLIs of the various tools, however it would be useful to have such features accessible as they used to be through the GUI. Perhaps this is a side-effect of making all Nautilus activities central to the Nautilus GUI? Because I think I remember it possibly opening another program in the past which had these options.

Regardless of what it and how it did it in the past, these are vital options which are missing and I think should be added back for ease of use.

I am fine with using the CLI, but many users are not.
Comment 1 Ernestas Kulik 2017-03-12 15:03:19 UTC
There is already bug 777285 for the encryption options. If you’re missing anything else specifically, please comment on bug 773366.

*** This bug has been marked as a duplicate of bug 773366 ***