Summary: | Ark crash | ||
---|---|---|---|
Product: | [Applications] ark | Reporter: | kazmafrost |
Component: | general | Assignee: | Raphael Kubo da Costa <rakuco> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kazmafrost, rakuco |
Priority: | NOR | ||
Version: | 2.15 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Action for crash
Reproduce crash for backtrace |
Description
kazmafrost
2010-10-15 06:16:02 UTC
From the backtrace, it looks like you canceled the creation of the archive. Is this correct? Are you able to reproduce this crash? Yes. I first task cancel, and immediately try again. Then crash. But, in spite of crashed generated compressed file that has been made successfully. And what steps did you follow to cancel the archive creation? I was cancel in the notification area. (stop button) Hmm, the weird thing is that I get no notification when compressing an archive here. Can you tell me what text is shown in the notification for you? Created attachment 52631 [details]
Action for crash
I screenshot attached.
Perhaps, only kubuntu problem? hmm..
Thanks for the screenshots -- I was creating a new archive from Ark instead of compressing via the context menus. I got a crash when I stopped Ark here too, but the backtrace was different. They might all be related to bug 193908. Do you always get the same backtrace when you do this? Uncertain but, backtrace seems to be the other. And I have a same problem as bug 193908. But the difference, regardless of file size. Just close Ark with windows x button before the file loaded. Can you post another (or some other) backtrace(s) you get? As for bug 193908, yes, that happens regardless of the size of the file. Created attachment 52711 [details] Reproduce crash for backtrace Reproduced the crash on .zip format. Strangely, this backtrace appears to be related with bug 222392. Changing the default assignee in the currently open Ark bug reports to me. OK, I think this is a duplicate of bug 222392 indeed. *** This bug has been marked as a duplicate of bug 222392 *** |