Bug 183405 - failed to start or decompress
Summary: failed to start or decompress
Status: RESOLVED DUPLICATE of bug 175637
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.12
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-06 11:01 UTC by Saalo Sparkes
Modified: 2009-02-06 13:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Saalo Sparkes 2009-02-06 11:01:26 UTC 
Version:           2.12 (using KDE 4.2.0)
OS:                Linux
Installed from:    SuSE RPMs

App was loaded via Dolphin right-click. Ark was used to uncompress a gz file. Ark never completed and the following error message appeared after system was restarted (restart unrelated):

[error report]

Application: Ark (ark), signal SIGSEGV
[Current thread is 1 (Thread 0xb5f20700 (LWP 3722))]

Thread 1 (Thread 0xb5f20700 (LWP 3722)):
[KCrash Handler]
#6  0x0805294f in _start ()
Comment 1 Dario Andres 2009-02-06 12:07:54 UTC 
You close a blank window before the crash appeared? If you did, this is a duplicate of bug 175637.
Anyway, was the file completely unzipped (the extracted file appeared), does the notification progress remained at 0% ?
Comment 2 Saalo Sparkes 2009-02-06 12:53:22 UTC 
Apologies, it's a duplicate.

Additionally, though, the compressed file was stuck at 0%. I had closed it when there was no progress, but as with the duplicate, it re-opened the next time I booted the machine; showing a blank windows.
Comment 3 Dario Andres 2009-02-06 13:01:40 UTC 
No problem :)

*** This bug has been marked as a duplicate of bug 175637 ***