Bug 681514 - [abrt] mutter-2.31.5-3.fc14: intelSetTexBuffer2: Process /usr/bin/mutter was killed by signal 6 (SIGABRT)
Summary: [abrt] mutter-2.31.5-3.fc14: intelSetTexBuffer2: Process /usr/bin/mutter was ...
Keywords:
Status: CLOSED DUPLICATE of bug 681161
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8c1b8479664a056041cb1cafdc4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-02 12:56 UTC by Jeff Layton
Modified: 2014-06-18 07:40 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-04 04:04:44 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (31.64 KB, text/plain)
2011-03-02 12:56 UTC, Jeff Layton 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.