Summary: | Okular cannot open .cbr document | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | t4m |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | qwertymaniac, t4m |
Priority: | NOR | ||
Version: | 0.10.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.4.2 |
Description
t4m
2010-03-25 03:26:29 UTC
Can't reproduce this, .cbr files seem to work fine with 3.93. `unrar` version banner reports this: UNRAR 3.93 freeware Copyright (c) 1993-2010 Alexander Roshal Tested with Okular trunk and 4.4.1 Do you, by any chance, also have the unrar free version installed? the only rar installed to this system reports RAR 3.93 Copyright (c) 1993-2010 Alexander Roshal 15 Mar 2010 Shareware version Type RAR -? for help Okular says "cannot open document, unrar was not found" Okay I think the problem here could be that your unrar exec is named 'rar' instead of 'unrar', and although they seem to be different packages they do support the same operations. 'rar' needs to be supported by Okular, I'll work on that (mostly change the code to detect unrar based on its 'freeware' keyword than its name, like how the GNOME app does iirc). P.s. Could this also be a distro packaging issue? Cause afaik, all distros ship the unrar package with the exec named as 'unrar' and not 'rar', although both exist. Huh? The system is pclinuxos 2010 beta2. The only rar pkg installed is "rarlinux-3.9.3-2pclos2010" SVN commit 1107586 by harshj: For Okular's Comic Book backend (.cbr files): * Add support for the 'rar' executable, since some distros seem to use it. BUG:232061 M +4 -0 unrar.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1107586 SVN commit 1107588 by harshj: For Okular's Comic Book backend (.cbr files): * Add support for the 'rar' executable, since some distros seem to use it. (Backport of 1107586) CCBUG:232061 M +4 -0 unrar.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1107588 Should be fixed in 4.4.2. |