Bug 674740 - [abrt] gnome-utils-2.28.1-10.el6: Process /usr/bin/gnome-search-tool was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-utils-2.28.1-10.el6: Process /usr/bin/gnome-search-tool was kill...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-utils
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 05:56 UTC by prashant ingale
Modified: 2018-11-14 14:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 17:20:18 UTC
Target Upstream Version:


Attachments (Terms of Use)
backtrace (3.31 KB, text/plain)
2011-02-03 05:56 UTC, prashant ingale
no flags Details

Description prashant ingale 2011-02-03 05:56:48 UTC
Created attachment 476700 [details]
backtrace

Description of problem:

 Process /usr/bin/gnome-search-tool was killed by signal 11 (SIGSEGV)

Version-Release number of selected component (if applicable):
 release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
 component: gnome-utils
 gnome-utils-2.28.1-10.el6

How reproducible:
 randomly 

Steps to Reproduce:
1.
2.
3.
  
Actual results:
 gnome-utils crashed.

Expected results:
 gnome-utils should not crash

Additional info:

Comment 2 RHEL Program Management 2011-07-06 00:13:47 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.


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