Bug 683024

Summary: [abrt] gnome-settings-daemon-2.28.2-11.el6: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV)
Product: Red Hat Enterprise Linux 6 Reporter: prashant ingale <pingale>
Component: gnome-settings-daemonAssignee: Bastien Nocera <bnocera>
Status: CLOSED DUPLICATE QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: rdassen, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-15 16:10:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
backtrace none

Description prashant ingale 2011-03-08 11:18:40 UTC
Created attachment 482877 [details]
backtrace

Description of problem:

reason: Process /usr/libexec/gnome-settings-daemon was killed by signal 11 (SIGSEGV).


Version-Release number of selected component (if applicable):

architecture: x86_64
component: gnome-settings-daemon
package: gnome-settings-daemon-2.28.2-11.el6
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)

How reproducible:
randomly 
  
Actual results:
gnome-setting-daemon crashed.


Expected results:
gnome-setting-daemon should not crashed.

Additional info:

Comment 2 RHEL Program Management 2011-07-06 00:29:22 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.

Comment 4 Bastien Nocera 2011-12-15 16:10:53 UTC
Duplicate of bug 717739.

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