Bug 592594 - [abrt] crash in file-roller-2.28.2-2.fc12: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in file-roller-2.28.2-2.fc12: Process /usr/bin/file-roller was k...
Status: CLOSED DUPLICATE of bug 561279
Alias: None
Product: Fedora
Classification: Fedora
Component: file-roller   
(Show other bugs)
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:253dfc5c3a19b2c7241defd9b1c...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-15 16:25 UTC by Alexey
Modified: 2010-05-25 08:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 08:32:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (16.44 KB, text/plain)
2010-05-15 16:25 UTC, Alexey
no flags Details

Description Alexey 2010-05-15 16:25:22 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: file-roller /media/Data/temp/compiz-0.8.6.tar.gz
component: file-roller
crash_function: egg_tree_multi_drag_button_release_event
executable: /usr/bin/file-roller
global_uuid: 253dfc5c3a19b2c7241defd9b1c63a976ad5fa7e
kernel: 2.6.32.11-99.fc12.i686
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)

Comment 1 Alexey 2010-05-15 16:25:25 UTC
Created attachment 414264 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 08:32:10 UTC

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

Comment 3 Karel Klíč 2010-05-25 08:32:10 UTC
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 #561279.

Sorry for the inconvenience.


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