Catalyst Control Centre Crashes when started.

[Hayden Heapy]

Screen flickers and program refuses to launch but generates no error.

ProblemType: Crash
Architecture: i386
AssertionMessage: amdcccle: ../../src/xcb_io.c:542: _XRead: Assertion `dpy->xcb->reply_data != ((void *)0)' failed.
Date: Sun Nov 1 19:08:04 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/amdcccle
MachineType: System manufacturer System Product Name
Package: fglrx-amdcccle 2:8.660-0ubuntu4
ProcCmdLine: root=UUID=4ba2579a-ddfe-41ef-8146-012aa1fc2935 ro quiet splash
ProcCmdline: amdcccle
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
Signal: 6
SourcePackage: fglrx-installer
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 _XRead () from /usr/lib/libX11.so.6
Title: amdcccle assert failure: amdcccle: ../../src/xcb_io.c:542: _XRead: Assertion `dpy->xcb->reply_data != ((void *)0)' failed.
Uname: Linux 2.6.31-14-generic i686
UserGroups:

dmi.bios.date: 10/22/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0412
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2N68
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0412:bd10/22/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

[Peter Cordes (peter-cordes)]

Is the fglrx kernel module loaded properly? Your Xorg.0.log shows that you are using the fglrx driver, but the 3D part of it failed to initialize.

[code]
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
[/code]

 It is always a bug when a program exits with an assertion failure, so it ought to be fixed by ATI. You can probably get things working on your system by making sure the drivers are installed properly. e.g.
install the fglrx packages and then reboot, to make sure the fglrx kernel module is loaded.

The .deb packages have a problem on amd64 (http://ati.cchtml.com/show_bug.cgi?id=1695), although it doesn't affect 32-bit systems like yours.

[Bryce Harrington (bryce)]

[This is an automatic notification.]

Hi Hayden,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 469239

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 469239 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/469239

[Hayden Heapy (hayden-heapy)]

I have ceased to use the fglrx drivers on my system, due to a change in graphics card. This bug is therefore no longer relevant to me and I have no way of testing if the problem still occurs in lucid.