File-Roller fails to extract password-protected rar-files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
File Roller |
Fix Released
|
High
|
|||
file-roller (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Natty |
Fix Released
|
Low
|
Unassigned | ||
Oneiric |
Fix Released
|
Low
|
Unassigned |
Bug Description
=== SRU Justification ===
Impact: Anyone trying to open a password protected rar file
Fixed upstream in 2.32.2.
Steps to reproduce:
1. Download https:/
2. Try to open it in file-roller
The attached patch fr.debdiff is a debdiff to update from 2.32.1 to 2.32.2. I've also uploaded this to natty-proposed.
=======
Binary package hint: file-roller
While trying to extract files from a protected rar-archive, I only get the error message
CRC failed in the encrypted file /home/EXAMPLE/
When trying the same with "rar e EXAMPLE.rar", I can enter the passowrd and it works without problems.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: file-roller 2.32.1-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.38-6-generic i686
Architecture: i386
Date: Thu Mar 10 15:10:53 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
ProcEnviron:
LANGUAGE=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: file-roller
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in file-roller (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → Low |
Changed in file-roller: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in file-roller: | |
importance: | Medium → High |
status: | New → Fix Released |
Changed in file-roller (Ubuntu Natty): | |
assignee: | nobody → constantin (roco-constantin-b) |
assignee: | constantin (roco-constantin-b) → nobody |
Thank you for your bug report. I'm seeing this bug too. Note that it works for files where only the files are password protected (option -p in rar), the problem is with files where also the information *about* the files is password protected (option -hp). I opened an upstream bug report about this, you can track it and make comments at: https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 646562