Bug 674791 - [abrt] metacity-2.28.0-20.el6: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
Summary: [abrt] metacity-2.28.0-20.el6: Process /usr/bin/metacity was killed by signal...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: metacity
Version: 6.1
Hardware: i686
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Owen Taylor
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-03 11:26 UTC by Siddharth
Modified: 2018-11-14 15:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-16 17:34:59 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Siddharth 2011-02-03 11:26:29 UTC
Description of problem:
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: metacity --sm-client-id 105387d5d71381214f129126774077385000000020290025
component: metacity
executable: /usr/bin/metacity
reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Client release 6.0 (Santiago)
metacity-2.28.0-20.el6
kernel: 2.6.32-71.7.1.el6.i686


How reproducible:
random crash.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Metacity was killed.

Expected results:
Metacity should not killed.

Additional info:

Comment 2 RHEL Program Management 2011-02-03 11:48:13 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 Owen Taylor 2011-05-16 17:19:20 UTC
Without reproduction instructions, it would be very hard to fix this. The reported error here is a out-of-memory inside the X server, which could just be the result of the machine running out of memory, or could be a result of a client application creating a window that is very, very big (nearly as big as the X window size limits of 16,000 pixels).

Comment 5 RHEL Program Management 2011-05-16 17:34:59 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.


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