Description of problem: In nautilus, creating a .zip file with password and then trying to extract with wrong password results in returning 1 [ONE] file with the message "All file operations have been successfully completed" and at the same time "incorrect password" To note, even if you have let's say files from 1,2,3,4,5 only the file with the name "1" will get extracted in the folder. However, the contents of that file will be missing. Version-Release number of selected component (if applicable):nautilus-41.0-1.fc35.x86 How reproducible:Always Steps to Reproduce: 1. Run touch 1 2 3 4 5 2. Write some data in files 1 2 3. Right click and select all the files 4. In the dropdown, select .zip with password and enter your favorite password 5. Wait for the .zip to show up 6. Extract the .zip and enter wrong passphrase 7. End up seeing a folder with the $name of zip with 1 as empty file in it Actual results: Only one file shows up , empty none the less Expected results: Should say "wrong passphrase" and not extract anything Additional info:
Proposed as a Blocker and Freeze Exception for 35-beta by Fedora user sumantrom using the blocker tracking app because: https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Default_application_functionality It is a new functionality and pretty basic . If the user ends up putting the incorrect password and still get a folder with any content it in. This will confuse the user. As this shows "All file operations completed successfully"
Beta is signed off, nothing can be a blocker or FE for Beta now. That's a Final criterion, so this could be proposed for Final if you like.
Proposed as a Blocker for 35-final by Fedora user sumantrom using the blocker tracking app because: https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Default_application_functionality It is a new functionality and pretty basic . If the user ends up putting the incorrect password and still get a folder with any content it in. This will confuse the user. As this shows "All file operations completed successfully"
(In reply to Adam Williamson from comment #2) > Beta is signed off, nothing can be a blocker or FE for Beta now. > > That's a Final criterion, so this could be proposed for Final if you like. My bad, I think it got wrongly proposed. I proposed it to Final
Created attachment 1826614 [details] error dialog > results in returning 1 [ONE] file with the message "All file operations have been successfully completed" and at the same time "incorrect password" In my experience, it doesn't say "successfully", but "There was an error while extracting ...". See the attached screenshot. nautilus-41.0-1.fc35.x86_64
Created attachment 1826627 [details] testing with one encrypted and unencypted zip
(In reply to Kamil Páral from comment #5) > Created attachment 1826614 [details] > error dialog > > > results in returning 1 [ONE] file with the message "All file operations have been successfully completed" and at the same time "incorrect password" > > In my experience, it doesn't say "successfully", but "There was an error > while extracting ...". See the attached screenshot. > > nautilus-41.0-1.fc35.x86_64 Kamil, thanks for testing this out. I was able to test another corner cases and get the word successfully. I created two separate zips, one encrypted and one non-encrypted. I selected both of the above mentioned zip and selected "extract here" Since the one without password extracts and the other doesn't; GNOME still tells me "successfully completed" [attached screenshot]. I believe that is confusing the user.
Right, in this case Nautilus should mark one of the operations as failing, and the popup should reflect that. Can you file an upstream Nautilus bug about this and link it here?
Discussed during the 2021-09-27 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as we agree that this does not constitute "basic functionality" for archive management, but it would be desirable to fix it even after freeze if a safe fix is available. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-09-27/f35-blocker-review.2021-09-27-16.00.txt
This is tracked upstream as https://gitlab.gnome.org/GNOME/nautilus/-/issues/1954.
Hi Ondrej, just please note that the linked issue covers only one part of the described problem. The second part is the "everything successful" popup, when multiple archives get extracted (and one of them is with invalid password).
Hmm, you are right. But it seems this is nothing new, this happens for other file operations as well, just it is extremely visible here. If I am not mistaken, this notification is meant to be shown if the Nautilus window isn't focused in order to inform that all operations were finished. So this notification should not appear in this case at all, because Natuilus is focused. Another thing is that the word "successfully" is a little bit confusing in such cases. I will try to fix that, let's use https://gitlab.gnome.org/GNOME/nautilus/-/issues/1953 for this.
Just a quick update. https://gitlab.gnome.org/GNOME/nautilus/-/issues/1954 was fixed and will be part of the upcoming Nautilus 41.1 upstream release. Unfortunately, no time left for backporting to Fedora this week, sorry. https://gitlab.gnome.org/GNOME/nautilus/-/issues/1953 hasn't been fixed yet as it is not obvious to me how it should be done.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1953 is still open upstream, so at least that part is apparently not resolved.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Just tested, this appears to be valid in current Rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle. Changing version to 42.