Summary: | Ark crashes on close when opening a broken (incomplete) multi-part RAR and getting an error message [exception, __cxa_pure_virtual, Kerfuffle::CliInterface::handleLine, Kerfuffle::CliInterface::readStdout] | ||
---|---|---|---|
Product: | [Applications] ark | Reporter: | Grzegorz Gostomski <grzesiu.gostomski> |
Component: | general | Assignee: | Harald Hvaal <metellius> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, rakuco, sergey.nikulov, slashdevdsp |
Priority: | NOR | Keywords: | investigated, triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Grzegorz Gostomski
2010-03-14 01:13:45 UTC
From bug 232923 (4.5trunk): -- Information about the crash: - What I was doing when the application crashed: Ark crashed when extracting rar file with dolphin running embedded konsole. I think it was a broken rar file ( 10 rar files but I had only a few ) when ark tried to load the rar file. It showed an error saying broken/error, but ark crashed after closing ark *** Bug 232923 has been marked as a duplicate of this bug. *** Created attachment 42610 [details]
New crash information added by DrKonqi
Trying to open big (18Gb) tar.gz archive.
Arc starting to read archive content.
Wait for about 1min.
Close Arc through window caption Close button (x).
Arc crash with this report.
Created attachment 42611 [details]
New crash information added by DrKonqi
repeated my described steps - it crashed again.
just one correction - archive was tar.bz2
Sergey, your problem is unrelated to this one - yours is bug 193908. Thank you Raphael. I just selected related in proposed by krash report tool - DrKonqi bug 193908 was not in list, so I select this one. Sorry for that. Right, people. We need more information on this to move on. People who experienced this crash, what files were you trying to open? Were they valid? What were their names? Is it possible to attach them? Is the problem still reproducible? mine was along the lines of filename.rar with 10 parts filename.r00, filename.r01 but I had only copied only filename.rar to filename.r05, the rest filename.r06 to filename.r09 were not copied. I just wanted to take a quick look at the contents with ark. i.e., ark filename.rar It showed a few warning messages (file not complete/broken) dialog with OK button which I closed, then I can see the content inside the rar's as say filename.iso. Now I closed Ark, then the crash happened. mine was along the lines of filename.rar with 10 parts filename.r00, filename.r01 but I had only copied only filename.rar to filename.r05, the rest filename.r06 to filename.r09 were not copied. I just wanted to take a quick look at the contents with ark. i.e., ark filename.rar It showed a few warning messages (file not complete/broken) dialog with OK button which I closed, then I can see the content inside the rar's as say filename.iso. Now I closed Ark, then the crash happened. unfortunately I do not have those rar files after I extracted the iso. I have not tried it with the latest trunk yet. Could you make random content multi-part rar file and delete some of the parts and try to view the content with ark? I created some sample multi-volume rar files with "rar a -vNNNNNN", but they were named "foo.part01.rar", "foo.part02.rar" etc. I got the message about the file being broken ("Extraction failed because of an unexpected error"), but I was able to close Ark with no crashes. Do you know if some other program generates multi-volume rars according to your naming schema? Almost 1 month has passed with no response, so I'm closing the report for now. If any of you has further information regarding this bug, please don't hesitate to reopen. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |