You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: I am encountering an issue when trying to extract a password-protected RAR file using the file manager. The problem is that the file explorer does not prompt me to enter the password when I start the extraction process. Instead, it completes the extraction, but the resulting file is corrupted or unusable.
Steps to Reproduce:
Right-click on a password-protected RAR file in the file explorer.
Select the "Extract" option.
No password prompt appears.
The extraction finishes, but the extracted file is invalid or unusable.
What did you expect to happen?
Expected Behavior: The file explorer should prompt me for the password before starting the extraction process and should extract the file correctly after entering the password.
Actual Behavior: No password prompt is shown, and the resulting extracted file is corrupted or invalid.
Output of rpm-ostree status
No response
Output of groups
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Description: I am encountering an issue when trying to extract a password-protected RAR file using the file manager. The problem is that the file explorer does not prompt me to enter the password when I start the extraction process. Instead, it completes the extraction, but the resulting file is corrupted or unusable.
Steps to Reproduce:
What did you expect to happen?
Expected Behavior: The file explorer should prompt me for the password before starting the extraction process and should extract the file correctly after entering the password.
Actual Behavior: No password prompt is shown, and the resulting extracted file is corrupted or invalid.
Output of
rpm-ostree status
No response
Output of
groups
No response
Extra information or context
No response
The text was updated successfully, but these errors were encountered: