Bug 681514

Summary: [abrt] mutter-2.31.5-3.fc14: intelSetTexBuffer2: Process /usr/bin/mutter was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jeff Layton <jlayton>
Component: mutterAssignee: Peter Robinson <pbrobinson>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: maxamillion, otaylor, pbrobinson, steved, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8c1b8479664a056041cb1cafdc4f14c58f544cd0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-04 04:04:44 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
File: backtrace none

Description Jeff Layton 2011-03-02 12:56:01 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 32395 bytes
cmdline: mutter --mutter-plugins=libgnome-shell
component: mutter
Attached file: coredump, 150929408 bytes
crash_function: intelSetTexBuffer2
executable: /usr/bin/mutter
kernel: 2.6.38-0.rc6.git6.1.fc15.x86_64
package: mutter-2.31.5-3.fc14
rating: 4
reason: Process /usr/bin/mutter was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: Just working within GNOME Shell.
time: 1299070708
uid: 4447

comment
-----
Nothing special. May have changed window focus at the time that it crashed.
Comment 1 Jeff Layton 2011-03-02 12:56:04 UTC 
Created attachment 481858 [details]
File: backtrace
Comment 2 Jeff Layton 2011-03-02 21:33:59 UTC 
For whatever reason, this seems to be affected by the kernel version.

With kernel-2.6.38-0.rc6.git6.1.fc15.x86_64, I see mutter crash regularly with this backtrace. With 2.6.38-0.rc5.git5.1.fc15.x86_64, I've not seen it crash this way at all.
Comment 3 Peter Robinson 2011-03-04 04:04:44 UTC 

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