Ubuntu
linux-restricted-modules-2.6.24 package

[fglrx] X crashed in CreateGC [Mobility X700] with dual screen enabled

Bug #201855 reported by Ed Hargin
2
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.24 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hardware: Acer Aspire 5024.
 - Graphics Card Ati Mobility X700
 - fglrx drivers using dual screen.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: /usr/bin/X(CreateGC+0x1f) [0x809eecf]
3: /usr/bin/X(ProcCreateGC+0xdd) [0x808db2d]
4: /usr/bin/X [0x81576c1]
5: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
6: /usr/bin/X(main+0x495) [0x8076f05]
7: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d01050]
8: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

Revision history for this message
Ed Hargin (ed-hargin) wrote :

I'll happily provide any more information that you require.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

What version of Ubuntu are you running? When did it start crashing, did you upgrade recently?

Changed in xorg:
status: New → Incomplete
Revision history for this message
Ed Hargin (ed-hargin) wrote :

Running Gutsy 7.10, and have been for the past few months.
This was the first crash for ages, but I still thought I should post a bug report in case someone could see the problem and fix it.

Revision history for this message
Bryce Harrington (bryce) wrote :

Unfortunately, "X crashes randomly" is far from enough to begin troubleshooting with. We need to know either detailed steps to reproduce (even "random" crashes are triggered by _something_), or lacking that, a full backtrace.

For directions on obtaining a full backtrace, please see https://wiki.ubuntu.com/DebuggingXorg.

From the backtrace you did post, it looks like it crashed somewhere in CreateGC. I'm not sure what line #1 is pointing at, but possibly this may be an X server bug rather than one in -fglrx. The full backtrace will tell us more.

Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

As of Intrepid (8.10), we have a dedicated package 'fglrx-installer' for fglrx bugs, which now includes a process for upstreaming bugs to AMD.

  http://bugs.launchpad.net/ubuntu/+source/fglrx-installer

To transition your bug into the new fglrx-package, we need your help. Please do the following:

 a. Verify the bug occurs in Intrepid.
     (Intrepid ISOs: http://cdimage.ubuntu.com)
 b. If you haven't already, please include in the bug:
     * Your /var/log/Xorg.0.log
     * The output of `lspci -vvnn`
     * Steps to reproduce the issue
 c. Click 'Also affects distribution'
 d. Set 'Source Package Name' to 'fglrx-installer'
 e. Click Continue

Thank you. This will assist us in reviewing and upstreaming your fglrx bug, as appropriate.

[We'll expire the fglrx bugs in l-r-m-* in a month or so.]

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-restricted-modules-2.6.24:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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