Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 588649 - [abrt] crash in file-roller-2.28.2-2.fc12: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
[abrt] crash in file-roller-2.28.2-2.fc12: Process /usr/bin/file-roller was k...
Status: CLOSED DUPLICATE of bug 557631
Product: Fedora
Classification: Fedora
Component: file-roller (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-04 04:03 EDT by Steve
Modified: 2010-05-25 04:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-25 04:31:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (14.16 KB, text/plain)
2010-05-04 04:03 EDT, Steve
no flags Details

  None (edit)
Description Steve 2010-05-04 04:03:19 EDT
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: file-roller file:///tmp/latest.zip
comment: file-roller crashes while draging & droping some files to a sftp-location
component: file-roller
executable: /usr/bin/file-roller
global_uuid: 4961edb0318286e58f09adb9f90f36dab3052f45
package: file-roller-2.28.2-2.fc12
rating: 4
reason: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. open zip-file
2. open sftp-location
3. drag & drop some files to extract to the sftp-location
Comment 1 Steve 2010-05-04 04:03:22 EDT
Created attachment 411218 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 04:31:33 EDT

*** This bug has been marked as a duplicate of bug 557631 ***
Comment 3 Karel Klíč 2010-05-25 04:31:33 EDT
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #557631.

Sorry for the inconvenience.

Note You need to log in before you can comment on or make changes to this bug.