Mutter/Gala crash on FGLRX 12.8

Bug #1046986 reported by Jonathan Alfonso
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gala
Invalid
Undecided
Unassigned
elementary OS
Invalid
Undecided
Unassigned
mutter (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm using Elementary OS Luna 0.2 and I had installed the FGLRX drivers to attempt to get WebGL support. I had rebooted to a unusable desktop (only window manager was gala and I could not use the keyboard) so I had installed mutter from TTY1. Once I installed it, mutter also crashed with the same issue that Gala crashes with (see below). I assume that this is because Gala's forked off mutter? Anyways I had to install Metacity and every login I must now type metacity --replace in a terminal.

----------------------------------------------------------------
Mutter:

(mutter:21179): Gdk-WARNING **: The program 'mutter' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 127 error_code 1 request_code 139 minor_code 66)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Gala:

(gala:21825): Gdk-WARNING **: The program 'gala' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 127 error_code 1 request_code 139 minor_code 66)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
----------------------------------------------------------------
Version info:

mutter:
  Installed: 3.4.1-0ubuntu99~elementary2
  Candidate: 3.4.1-0ubuntu99~elementary2
  Version table:
 *** 3.4.1-0ubuntu99~elementary2 0
        500 http://ppa.launchpad.net/elementary-os/daily/ubuntu/ precise/main amd64 Packages
        999 http://ppa.launchpad.net/elementary-os/os-patches/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status
     3.4.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Package

gala:
  Installed: 0.1-0~r219+pkg13~precise1
  Candidate: 0.1-0~r219+pkg13~precise1
  Version table:
 *** 0.1-0~r219+pkg13~precise1 0
        500 http://ppa.launchpad.net/elementary-os/daily/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: elementary 0.2
Package: elementary-desktop 1.275-0~345~precise1
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
ApportVersion: 2.0.1-0ubuntu12+elementary3~precise1
Architecture: amd64
CrashDB: elementary_meta
Date: Thu Sep 6 14:40:01 2012
InstallationMedia: elementary OS 0.2 "Luna" - Build amd64 LIVE Binary 20120902-20:44
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: elementary-meta
SuspiciousXErrors:

ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jonathan Alfonso (alfonsojon1997) wrote :
Revision history for this message
Sergey "Shnatsel" Davidoff (shnatsel) wrote :

fglrx is known to be buggy, and we can do nothing about that. It's blacklisted in Jockey in elementary OS for a reason, you know.

Changed in elementaryos:
status: New → Invalid
Changed in gala:
status: New → Invalid
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for reporting this bug to Ubuntu. 11.04 reached End of Life in 2012. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

I've tried recreating this bug with your release and was unable to, given the information you've provided. Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.

Changed in mutter (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.