Summary: | ark dies when i extract lots of rar part-archives simultaneously and cancel this action | ||
---|---|---|---|
Product: | [Applications] ark | Reporter: | Benedikt Haus <benedikt.haus> |
Component: | general | Assignee: | Harald Hvaal <metellius> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, frederico.cerveira, hamhouke, jorgen.vero, joshlukas, ochach, rakuco, termnet |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.4.5 | |
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Benedikt Haus
2010-01-06 18:12:29 UTC
This looks related to bug 196856. - Does Ark always crash if you repeat the situation with the same fileset ? Thanks Hi, I can reproduce this. It happens with all password-protected sets of part1.rar,part2.rar etc I tried. This is what I exactly do: Select all archives from the set, right click, "extract here"(?) (german: "Archiv hierher auspacken"). Then he asks me for the password, I click cancel and ark segfaults. Created attachment 42463 [details]
New crash information added by DrKonqi
I tried to unpack multiple rar-files using the mouse context menu - 'unpack archive...'
Created attachment 43213 [details]
New crash information added by DrKonqi
upacking lot of rar part archives canceld after first unpacked pice of archive.
*** Bug 237169 has been marked as a duplicate of this bug. *** *** Bug 236386 has been marked as a duplicate of this bug. *** *** Bug 241328 has been marked as a duplicate of this bug. *** SVN commit 1140174 by rkcosta: Check if we have a thread before executing operations on it. BUG: 221551 M +4 -0 jobs.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1140174 SVN commit 1140181 by rkcosta: Backport r1140174. Check if we have a thread before executing operations on it. CCBUG: 221551 M +3 -0 jobs.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1140181 *** Bug 253902 has been marked as a duplicate of this bug. *** |