Bug 675854 - nouveau: crash in _mesa_test_framebuffer_completenes
Summary: nouveau: crash in _mesa_test_framebuffer_completenes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a6fc5786571351b864db40b2088...
: 681624 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-07 23:13 UTC by Jóhann B. Guðmundsson
Modified: 2011-11-29 16:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-29 12:54:26 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (60.84 KB, text/plain)
2011-02-07 23:13 UTC, Jóhann B. Guðmundsson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Jóhann B. Guðmundsson 2011-02-07 23:13:31 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 62298 bytes
cmdline: mutter --mutter-plugins=libgnome-shell
component: mutter
Attached file: coredump, 125579264 bytes
crash_function: _mesa_test_framebuffer_completeness
executable: /usr/bin/mutter
kernel: 2.6.38-0.rc3.git4.1.fc15.x86_64
package: mutter-2.91.6-2.fc15
rating: 4
reason: Process /usr/bin/mutter was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1297113928
uid: 500

How to reproduce
-----
1. started gnome terminal clicked maximise 
2.
3.
Comment 1 Jóhann B. Guðmundsson 2011-02-07 23:13:34 UTC 
Created attachment 477521 [details]
File: backtrace
Comment 2 Owen Taylor 2011-03-26 18:18:21 UTC 
*** Bug 681624 has been marked as a duplicate of this bug. ***
Comment 3 Peter Robinson 2011-10-11 10:21:57 UTC 
is this still an issue with the latest updates?
Comment 4 Peter Robinson 2011-11-29 12:54:26 UTC 
Closing as no response
Comment 5 Jóhann B. Guðmundsson 2011-11-29 16:15:20 UTC 
Hum somehow I lost the needinfo anyway have not seen it again.
Note You need to log in before you can comment on or make changes to this bug.