abrt version: 1.1.17 architecture: i686 Attached file: backtrace, 45586 bytes cmdline: mutter --mutter-plugins=libgnome-shell component: mutter Attached file: coredump, 79351808 bytes crash_function: src_register executable: /usr/bin/mutter kernel: 2.6.38-0.rc4.git0.1.fc15.i686 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: 1297338774 uid: 500 How to reproduce ----- 1. 2. 3.
Created attachment 478631 [details] File: backtrace
This looks like a crash in the ATI mesa 3D driver
Indeed.. I do believe this is the underlying cause for my mutter crashes... Feb 14 19:05:22 localhost kernel: [ 244.755020] mutter[2761]: segfault at bf8f7750 ip 04c3f32e sp bf8f2dc0 error 4 in r300_dri.so[4a90000+386000] 01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300]
This seems to be fixed in alpha tc2 - if so this bug can be closed?
Was not fixed for me in TC2 confirmed fixed in RC2 alpha
Argh - yes - my bad - it was a typo! I should have written RC2 and not tc2 in #4 - apologies.
Sorry for (probably) capturing this bug: I tried mutter --replace on a system equipped with such a card. System immediately freezes. No logs found. Smolt profile: http://www.smolts.org/client/show/pub_e6aeaf20-165f-43af-a633-5f14d3c95782 Should I file another bug, is it the same?
(In reply to comment #7) > Should I file another bug, is it the same? Yes, please. Please provide a backtrace of your crash, together with /var/log/Xorg.0.log, /var/log/messages, and the output of dmesg AFTER the crash happens (but before reboot obviously). Thank you
My crash has been solved lately with the release of kernel-2.6.38-1 cf. https://bugzilla.redhat.com/show_bug.cgi?id=683994 I guess, the original problem is solved also.
Should be working in current Mesa.