When I do an "unrar e example-file.rar" with a particular encrypted rar archive I am asked to type in the password. When pressing enter all lower case text that is output from that point on becomes unreadable (when given the wrong pw unrar ends itself, but text is ok). Upper case letters, numbers and special characters are fine, however. The problem occurs with the console as well as with the Terminal (I use XFCE4). When new Terminal windows are opened later they are ok. This is unrar-3.8.5 Reproducible: Always Steps to Reproduce: 1.unrar e example-file.rar 2.type in password 3.see scrambled console text
Please, be more specific. What does "all lower case text that is output from that point on becomes unreadable" mean: - output of unrar becomes unreadable - your input after unrar finishes its job is unreadable - something else Also, could you give more details about that archive. Does it i.e. outputs its comment and then its output becomes unreadable ? Did you try a different terminal (xterm, urxvt, etc.) ?
By "all lower case text" I mean letters a to z are affected. The unreadable output includes output from unrar itself as well as output of other programms I start afterwards. So if I do ls in the same terminal its output is scrambled also. I have tried xterm now and here its different. After the "Enter password (will not be echoed) for example-file.rar:" the output is this: ---------------------------- ;(t¾ÚÔÈ Èdîzª«õ³_÷ÀWÞ8ª±¬çÖ&MÄpa@ÂK?´òúx!¦äNOKeQÏýt¶?%,³3XÔb`<A±ôà]Z¡u¦E`ÜöØì©*>QLÏø(ûÉ+ f³»îÅ - the file header is corrupt Encrypted file: CRC failed in example-file.rar (password incorrect ?) No files to extract jens@blackbox:~$ ---------------------------- Any output after this is not affected. urxvt I could not test as there is no ebuild.
urxvt stands for rxvt-unicode. So, is that archive really corrupt or is that a part of the bug ? What's the effect of 'unrar l <that archive>' ? Also, what is your locale ?
urxvt behaves like xterm, LXTerminal like Terminal. I have tried to unrar the archive under Windows now and it also says its corrupt. The output of 'unrar l <that archive>' is identical to that of 'unrar e <that archive>'. My locale is de_DE.utf8@euro
In that case, the problem lies within the archive - unrar probably tries to print archive's comment, which is probably corrupted, so among things printed are some control sequences, that those two terms you've mentioned try to interpret somehow. Random sequences - random effects. So, this is probably invalid.
Would you suggest to file a bug report against Terminal instead?
Not really, terminal probably work just fine - they interpret those sequences as they are supposed to. If a broken archive produces such effect, it's not really a bug in neither the terminals nor in unrar (well, perhaps unrar should be tweaked to examine the header before printing the comment, then again, there's no telling how corrupted that archive was).
We cannot fix broken rar-archives. Marking as INVALID.
