Bug 663496 - [abrt] file-roller-2.32.0-2.fc14: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
Summary: [abrt] file-roller-2.32.0-2.fc14: Process /usr/bin/file-roller was killed by ...
Keywords:
Status: CLOSED DUPLICATE of bug 678592
Alias: None
Product: Fedora
Classification: Fedora
Component: file-roller
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:918cebde5a6345ea65195845fcc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-15 23:25 UTC by Paul Smith
Modified: 2012-03-30 13:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-30 13:10:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (67.10 KB, text/plain)
2010-12-15 23:25 UTC, Paul Smith 		no flags Details
View All

Description Paul Smith 2010-12-15 23:25:27 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: file-roller file:///tmp/026201243XLearningMachine.rar
component: file-roller
crash_function: gtk_tree_view_move_cursor_page_up_down
executable: /usr/bin/file-roller
kernel: 2.6.35.6-48.fc14.x86_64
package: file-roller-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/file-roller was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Thanks.
time: 1291160890
uid: 500
Comment 1 Paul Smith 2010-12-15 23:25:30 UTC 
Created attachment 468993 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 13:10:58 UTC 
Backtrace analysis found this bug to be similar to bug #678592, closing as duplicate. This bug seems to belong to component gtk2.

Bugs which were found to be similar to this bug: 
  evolution: bug #621703
  firefox: bug #575797
  gnome-system-monitor: bug #633465
  nautilus: bug #542488, bug #603473, bug #642455, bug #678592
  xfce4-settings: bug #749019

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 678592 ***
Note You need to log in before you can comment on or make changes to this bug.