Bug 556135

Summary: [abrt] crash in mutter-2.28.0-3.fc13
Product: [Fedora] Fedora Reporter: Kjartan Maraas <kmaraas>
Component: gjsAssignee: Peter Robinson <pbrobinson>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: otaylor, pbrobinson, walters
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:ba412075ec2d87552374d9956a0bb5fec884f1ca
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 14:48:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Kjartan Maraas 2010-01-16 17:57:49 UTC
abrt 1.0.2 detected a crash.

Comment: Crashed after logging in
Attached file: backtrace
cmdline: mutter --mutter-plugins=libgnome-shell
component: mutter
executable: /usr/bin/mutter
kernel: 2.6.31.5-127.fc12.i686.PAE
package: mutter-2.28.0-3.fc13
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)

Comment 1 Kjartan Maraas 2010-01-16 17:57:52 UTC
Created attachment 384830 [details]
File: backtrace

Comment 2 Peter Robinson 2010-02-03 10:34:31 UTC
It looks like an issue in gjs

#0  0x01acf159 in addMem (bytes=65536, mem=<value optimized out>, this=
    0x8a2ef60) at nanojit/CodeAlloc.cpp:327
No locals.
#1  nanojit::CodeAlloc::alloc (bytes=65536, mem=<value optimized out>, this=
    0x8a2ef60) at nanojit/CodeAlloc.cpp:132
        mem = <value optimized out>
        b = 0xffffffff
#2  0x01ac516a in nanojit::Assembler::codeAlloc (this=<value optimized out>, 
    start=<value optimized out>, end=<value optimized out>, 
    eip=<value optimized out>) at nanojit/Assembler.cpp:192
No locals.

Comment 3 Bug Zapper 2010-03-15 14:05:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2011-06-02 16:51:49 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2011-06-27 14:48:39 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.