| Summary: | Ark crashes with unrar-free | ||
|---|---|---|---|
| Product: | [Applications] ark | Reporter: | Fabio <cy83rw4rr10r> |
| Component: | general | Assignee: | Harald Hvaal <metellius> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | cbell44, dankeschone, deamon.dreem, dnl_georgiev, franciscoadriansanchez, gerald.voss, gothik, jarmstrong, lucianosvinas, maugarta, mazdecth, prasmal, rakuco |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.6.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Fabio
2010-06-30 20:00:41 UTC
Does it happen to any file you try? Can you attach a sample file that causes this problem? For the record: Fabio has sent me a RAR file which causes the crash for him. Fabio: I was able to open that file just fine. What version of unrar are you using? Is it unrar or unrar-free? Last but not least, when you said "When i open an archive rar Ark go to crash before i have install unrar" does it mean you can only extract/list an archive by using unrar via the command line? In data venerdì 02 luglio 2010 16:47:32, Raphael Kubo da Costa ha scritto:
> https://bugs.kde.org/show_bug.cgi?id=243273
>
>
>
>
>
> --- Comment #2 from Raphael Kubo da Costa <kubito gmail com> 2010-07-02
> 16:47:31 --- For the record: Fabio has sent me a RAR file which causes the
> crash for him.
>
> Fabio: I was able to open that file just fine. What version of unrar are
> you using? Is it unrar or unrar-free?
>
> Last but not least, when you said "When i open an archive rar Ark go to
> crash before i have install unrar" does it mean you can only extract/list
> an archive by using unrar via the command line?
Well i use unrar-free 0.0.1.
No, i can't. When i try via the command line, it don't go to crash, but it
failed the extraction.
Indeed, it's broken for unrar-free. Was the symlink /usr/bin/unrar-free -> /usr/bin/unrar created manually by yourself? Fabio? In data giovedì 08 luglio 2010 06:22:40, Raphael Kubo da Costa ha scritto:
> https://bugs.kde.org/show_bug.cgi?id=243273
>
>
>
>
>
> --- Comment #5 from Raphael Kubo da Costa <kubito gmail com> 2010-07-08
> 06:22:37 --- Fabio?
Sorry, i don't have read your email.
I realized that i have in /usr/bin unrar and unrar-free
Can you confirm if those two are different programs, and which packages they belong to? In data giovedì 08 luglio 2010 16:12:30, Raphael Kubo da Costa ha scritto:
> https://bugs.kde.org/show_bug.cgi?id=243273
>
>
>
>
>
> --- Comment #7 from Raphael Kubo da Costa <kubito gmail com> 2010-07-08
> 16:12:29 --- Can you confirm if those two are different programs, and
> which packages they belong to?
No, i have installed unrar-free package only .
Can you then check that /usr/bin/unrar is a symlink to /usr/bin/unrar-free? In data giovedì 08 luglio 2010 20:07:48, Raphael Kubo da Costa ha scritto:
> https://bugs.kde.org/show_bug.cgi?id=243273
>
>
>
>
>
> --- Comment #9 from Raphael Kubo da Costa <kubito gmail com> 2010-07-08
> 20:07:44 --- Can you then check that /usr/bin/unrar is a symlink to
> /usr/bin/unrar-free?
It's a symlink to /etc/alternatives/unrar.
/etc/alternatives/unrar it is a symlink to /usr/bin/unrar-free.
*** Bug 250222 has been marked as a duplicate of this bug. *** *** Bug 257698 has been marked as a duplicate of this bug. *** *** Bug 256015 has been marked as a duplicate of this bug. *** SVN commit 1200794 by rkcosta: Rework clirarplugin's line reading logic again. The code looks more like a state machine, which is good and should make it easier to understand. This also made it possible to add some code to check the column names written before the header lines and decide whether we're using unrar-free or unrar based on that (which should fix Ark crashing when being used with unrar-free). If we're using unrar-free, we never try to parse the third file name entry line, as unrar-free never outputs it. It should be hopefully safe to backport, but I'll wait at least a few days. As I'm unsure whether it's OK to backport it, the FIXED-IN version will be 4.6.0. BUG: 243273 FIXED-IN: 4.6.0 M +59 -19 cliplugin.cpp M +5 -1 cliplugin.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1200794 SVN commit 1209201 by rkcosta: Rework clirarplugin's line reading logic again. The code looks more like a state machine, which is good and should make it easier to understand. This also made it possible to add some code to check the column names written before the header lines and decide whether we're using unrar-free or unrar based on that (which should fix Ark crashing when being used with unrar-free). If we're using unrar-free, we never try to parse the third file name entry line, as unrar-free never outputs it. It should be hopefully safe to backport, but I'll wait at least a few days. As I'm unsure whether it's OK to backport it, the FIXED-IN version will be 4.6.0. Backport of r1200794. CCBUG: 243273 M +63 -22 cliplugin.cpp M +5 -1 cliplugin.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1209201 *** Bug 261897 has been marked as a duplicate of this bug. *** *** Bug 264325 has been marked as a duplicate of this bug. *** Created attachment 56719 [details]
New crash information added by DrKonqi
Ark seems to crash when attempting to open an incomplete rar file or rar set. It apparently can't handle the error.
unrar-3.90.4-6.1.x86_64
rar-3.9.3-1.pm.2.1.x86_64
ark-4.4.4-1.3.x86_64
dankeschone: This is unrelated to this report about unrar-free, and should have been fixed in later KDE versions. Please consider updating your installation. Created attachment 59025 [details]
New crash information added by DrKonqi
No matter how many times I tried to open a RAR file or other archive, ARK crashed. Also , I noticed some performance reduction in desktop effects.
Daniel, this bug has already been fixed. Please consider updating your installation. *** Bug 272507 has been marked as a duplicate of this bug. *** *** Bug 272773 has been marked as a duplicate of this bug. *** *** Bug 274593 has been marked as a duplicate of this bug. *** *** Bug 278814 has been marked as a duplicate of this bug. *** |