Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.9 detected a crash. architecture: i686 Attached file: backtrace cmdline: mutter --mutter-plugins=libgnome-shell --replace component: mutter crash_function: meta_compositor_process_event executable: /usr/bin/mutter global_uuid: 04611d1ceb2f3c445f5f96983961ed32b076bc42 kernel: 2.6.32.11-99.fc12.i686.PAE package: mutter-2.28.0-2.fc12 rating: 4 reason: Process /usr/bin/mutter was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 412285 [details] File: backtrace
*** Bug 592503 has been marked as a duplicate of this bug. ***
*** Bug 588682 has been marked as a duplicate of this bug. ***
Package: mutter-2.29.1-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.TEntar ativar o gnome-shell 2. 3.
Package: mutter-2.29.1-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Install gnome-shell from packagekit 2. System - Prefs - Desktop Effects 3. Choose Gnome Shell Comment ----- Any known conflict w. the nvidia binary driver?
Package: mutter-2.29.1-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Start FC13, 64-bit, with the kmod-nvidia-2.6.33.6-147.fc13.x86_64-195.36.31-1.fc13.1.x86_64 driver, two separate X screens (one at 24 fps and one at the default monitor refresh), and metacity on w. compositing 2.System - Preferences - Display Effects 3.Choose "Gnome Shell" 4.Mutter crashes Comment ----- Just tried to fire up "mutter" via the Preferences - Display Effects menu. Wondering if it is somehow related to the nvidia binary driver being set up in separate X screens mode (with the two refreshes not matching).
Package: mutter-2.29.1-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.not a clue, never saw the crash 2. 3.
Package: mutter-2.29.1-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Trying to start gnome shell
*** Bug 623977 has been marked as a duplicate of this bug. ***
*** Bug 624064 has been marked as a duplicate of this bug. ***
We don't support binary drivers. Please report the issue to the manufacturer.