Bug 683384 - [abrt] gnome-session-2.28.0-15.el6: g_slice_alloc: Process /usr/bin/gnome-session was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-session-2.28.0-15.el6: g_slice_alloc: Process /usr/bin/gnome-ses...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnome-session
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 782183 1056252
TreeView+ depends on / blocked
 
Reported: 2011-03-09 10:18 UTC by Siddharth
Modified: 2018-11-26 19:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-20 19:56:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
backtrace (28.31 KB, text/plain)
2011-03-09 10:28 UTC, Siddharth 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Siddharth 2011-03-09 10:18:31 UTC 
Description of problem:

abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gnome-session
component: gnome-session
crash_function: g_slice_alloc
executable: /usr/bin/gnome-session


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

release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
gnome-session-2.28.0-15.el6

How reproducible:
Random crash.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
gnome-session killed by segmentation fault.

Expected results:
gnome-session should not crashed.

Additional info:
Comment 2 Siddharth 2011-03-09 10:28:06 UTC 
Created attachment 483150 [details]
backtrace
Comment 4 RHEL Program Management 2011-03-09 10:38:11 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 5 RHEL Program Management 2011-03-09 11:18:11 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 10 RHEL Program Management 2012-07-10 06:16:43 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 11 RHEL Program Management 2012-07-10 23:20:48 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 12 Tom Lavigne 2012-09-18 15:23:29 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 unable to address this
request at this time.
    
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 13 RHEL Program Management 2013-10-14 01:08:43 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 unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 15 Ray Strode [halfline] 2014-03-31 18:19:51 UTC 
with not reproducer and such a terse backtrace there's no way to diagnose this crash.
Note You need to log in before you can comment on or make changes to this bug.