Xorg crashes with /usr/bin/X(FontFileCompleteXLFD+0x1e1)

[Diego Gaustein]

Hi. By advice of Tormod Volden ( https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/71913/comments/46 ) I'm filing a new bug, since my backtrace seems different.

When using Compiz, X crashes apparently randomly. The backtrace always is

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d2f050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

It only happens when Compiz is activated. I've tried both nvidia-glx-new and latest driver with Envy, and the results are the same. The crashes only happen when doing something, and not when the computer is idle, but can't find a way to reproduce it consistently.

I've read https://wiki.ubuntu.com/DebuggingXorg , but there're many methods and I'm not sure which one is the proper one, in order to get useful debug information. I have another computer and ssh setup, if needed; any info on how to debug this would be appreciated.

Cheers.

[Diego Gaustein (gregorovius)]

$ uname -a
Linux gregorovius 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

This is a newly installed Gutsy, but the same happened with a Gutsy upgraded from Feisty.

I have an NVidia 6200 TC video card.

[mod (wehavenoprivacy)]

I'm not sure if this is the same bug or not, but I experienced a hang when using Google Earth. This was with a fresh install of Gutsy using NVIDIA 7600GT (nvidia-glx-new) with Compiz activated (dual-head display).

[Abhinay Mukunthan (lexxonnet)]

This isn't an Nvidia bug, since my backtrace is exactly the same when using compiz or kwin-composite(kde3).
I'm using an ATI Radeon 9600 Mobility with the DRI drivers shipped by default in gutsy. I've recreated the error deliberately a couple of times, and the backtraces are always identical.

The best way to recreate the bug is to run Yakuake, and do something intensive on it, such as running apt-get.
Repeatedly hiding and showing Yakuake is almost sure to cause the crash.

My backtrace is attached for reference:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dea050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

[Abhinay Mukunthan (lexxonnet)]

Oh.. I forgot to mention, the bug only occurs when a compositing manager is used. Its fine as long as normal Kwin is run.

[Diego Gaustein (gregorovius)]

It's quite confusing... I use Yakuake as well, but I never noticed any correlation between it and the crashes.

So! if this isn't NVidia's fault, where should I point the bug? Xorg?

Cheers

[Abhinay Mukunthan (lexxonnet)]

I believe Xorg is at fault. I've had it happen to me other than times that I use Yakuake, but that's the easiest way to reproduce it. Whatever it is, I'm quite sure Nvidia isn't at fault, since it happens to me with an ATI card, and as seen on the other bug report, it happened to someone with an Intel card too.

Btw... you can probably mark the bug as confirmed as well :)

Its interesting that Yakuake doesn't seem to cause you issues. People on this thread have similar issues, and one of them (other than me :)) mentions Yakuake as well... http://ubuntuforums.org/showthread.php?t=354697&page=2

[Abhinay Mukunthan (lexxonnet)]

I dont think this is an nVidia bug... I've got the same backtrace on an ati card, with the DRI drivers used in xorg-driver-ati(not part of restricted modules)

[Abhinay Mukunthan (lexxonnet)]

Sorry... hit a button by mistake :(

[taw (tomasz-wegrzanowski)]

I'm getting similar random crashes (also while using yakuake) on a Macbook with Intel 945.
I'm not sure if that's the same bug or something else. It's a fresh installation,
I didn't have this problem when I was running kUbuntu 7.10 (+yakuake) on the same hardware.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e39d]
3: /usr/bin/X [0x817a9ef]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x816129a]
5: /usr/bin/X [0x8168f19]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d16050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4

[loqsae (loqsae)]

I have a generic kubuntu 7.10 install w/ nvidia proprietary drivers.
I am not running gcompriz/beryl.
My box drops to console and then to kdm login.

This happens only when I load nomachine's free linux version and logs into a remote host(X).
As long as I don't change desktops on the local machine(Y), everything is stable. The second
I switch from the local virtual desktop to another local virtual desktop the whole thing drops.

It didn't happen in 7.04. It doesn't happen when I am sitting in from of the remote host(X) and
using nomachine to get to the above local machine (Y). They both were installed from the same
CD. They both are using the nvidia drivers. They both should roughly have the same drivers/software.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X [0x817e279]
3: /usr/bin/X [0x817ac05]
4: /usr/bin/X(CompositePicture+0x153) [0x8161113]
5: /usr/bin/X [0x81673ef]
6: /usr/bin/X [0x8164315]
7: /usr/bin/X [0x815754e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7db4050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

[John D (zahadum76)]

Same bug?

(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 11 17:44:41 2008
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in

Backtrace:
0: X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: X(main+0x2af) [0x8076d1f]
3: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d99050]
4: X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

Aborted

[Emilio Scalise (emisca)]

I'm using debian Etch, and I had the same crashes with a similar backtrace...

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c43e4]
1: [0xffffe420]
2: /usr/bin/X [0x815ad8c]
3: /usr/bin/X [0x81572f5]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x814466a]
5: /usr/bin/X [0x814c228]
6: /usr/bin/X [0x81476a5]
7: /usr/bin/X(Dispatch+0x19b) [0x8086ccb]
8: /usr/bin/X(main+0x489) [0x806e6b9]
9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0x47580ea8]
10: /usr/bin/X(FontFileCompleteXLFD+0xa5) [0x806d9f1]

Fatal server error:
Caught signal 11. Server aborting
My xorg server version is 1.1.1-21etch2, nvidia geforce go 7400, nvidia drivers 169.07. As many users found on the forum, using yakuake makes this bug to occur less rarely.

[Shiv V (svenkata)]

I'm running Ubuntu gutsy on a Macbook Pro (+ fglrx with AIGLX not Xgl). X crashes when I resume from suspend-to-RAM with compiz running (resumes fine with metacity) with the following backtrace. In addition, I can't get to a text virtual terminal when compiz is running (Ctrl+Alt+F1).

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xb7f98420]
2: /usr/lib/xorg/modules//libfb.so(fbCopyWindowProc+0x149) [0xb77082d9]
3: /usr/lib/xorg/modules//libfb.so(fbSaveAreas+0x7a) [0xb76f052a]
4: /usr/lib/xorg/modules//libxaa.so [0xb7695ee9]
5: /usr/bin/X [0x8120ddb]
6: /usr/bin/X [0x8137441]
7: /usr/bin/X(miValidateTree+0x400) [0x8138540]
8: /usr/lib/xorg/modules/extensions//libdri.so(DRIValidateTree+0x57) [0xb7c31b87]
9: /usr/bin/X(miMoveWindow+0x247) [0x813ea97]
10: /usr/bin/X(compMoveWindow+0xad) [0x810b67d]
11: /usr/bin/X(ConfigureWindow+0x775) [0x807c765]
12: /usr/bin/X(ProcConfigureWindow+0xa1) [0x808ebf1]
13: /usr/bin/X [0x81575b1]
14: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
15: /usr/bin/X(main+0x495) [0x8076f05]
16: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dac050]
17: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

This seems related to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/158761

[Adam Porter (alphapapa)]

I'm running Debian testing/unstable with Xorg 7.2 from testing, NVIDIA GeForce 4 Ti4200 with the 96.43.01 drivers. I HAVE been running Yakuake, but I have NOT been using Compiz, Beryl, or any other compositing manager.

I am getting this crash, and it is quite frustrating. It has happened to me when logging in to KDE, without even accessing the Yakuake window. It has happened to me when Amarok was the only window on screen. It has happened to me when hiding Yakuake. Today I got a crash while KDE was logging in, and it froze up the computer completely, with the Caps Lock and Scroll Lock lights blinking.

This was not happening to me a week ago! I have gone through my aptitude log but I can't figure out what upgrade might have caused it. I have rebuilt and reinstalled the NVIDIA drivers but it didn't help. I downgraded from Xorg 7.3 to 7.2, but that didn't help.

For the time being I will stop using Yakuake and see if that helps. However, all of yesterday I used it as usual and had no crashes. I have used Yakuake for years, and I've never had any trouble with it except when using compositing.

Argh!

[Adam Porter (alphapapa)]

Oh:

(I think this is with 7.3)
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c644e]
1: [0xffffe420]
2: /usr/bin/X(dixChangeGC+0x60d) [0x809bc8d]
3: /usr/bin/X(ProcChangeGC+0xa3) [0x808b553]
4: /usr/bin/X [0x814d3ce]
5: /usr/bin/X(Dispatch+0x2bf) [0x808d0bf]
6: /usr/bin/X(main+0x48b) [0x807461b]
7: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0x42311450]
8: /usr/bin/X(FontFileCompleteXLFD+0x205) [0x8073991]

(and this is with 7.2)
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c89c1]
1: [0xffffe420]
2: /usr/bin/X(dixChangeGC+0x60d) [0x809dadd]
3: /usr/bin/X(ProcChangeGC+0xa7) [0x808d5f7]
4: /usr/bin/X [0x8154c9e]
5: /usr/bin/X(Dispatch+0x1a1) [0x808eff1]
6: /usr/bin/X(main+0x47e) [0x8076e2e]
7: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0x43a4f450]
8: /usr/bin/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]

[Diego Gaustein (gregorovius)]

Well, I've been using Compiz without Yakuake for about 2 days now and it hasn't crashed yet. Though this is far from definitive, it seems something Yakuake does tends to trigger this bug. Anyhow, a userspace app shouldn't be able to bring X down.

@ John D: your backtrace is completely different. Try to see if there's a bug already filed, else, file your own.

@ Adam Porter: Though your backtrace seems kinda similar, it's not exactly the same, but you're running Debian, and I have no idea how different Debian's X is from Ubuntu's.

I'd really like to hear what the X MOTUs think. I've had this bug since Feisty, and I'd love to see it fixed for Hardy.

Cheers.

[goibhniu (cillian-deroiste)]

I get the same here with an nVidia GeForce 8600 GT on gutsy
2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 GNU/Linux

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6d) [0x48672d]
1: /lib/libc.so.6 [0x2b827665c7d0]
2: /usr/bin/X [0x53389c]
3: /usr/bin/X [0x533a96]
4: /usr/bin/X [0x52fee9]
5: /usr/bin/X [0x51d6ef]
6: /usr/bin/X(Dispatch+0x1db) [0x4514eb]
7: /usr/bin/X(main+0x45d) [0x439f4d]
8: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b8276648b44]
9: /usr/bin/X(FontFileCompleteXLFD+0x231) [0x439249]

The odd thing is that it just started happening last week and the system has been very stable up until then. I am running compiz and avant-window-navigator (but not yakuake) and the system isn't under much load. It happened 3 times today so I'm going to try life without compiz for a while.

[Ivo Roghair (ivo-82)]

I am also experiencing this bug more and more lately, twice today. I have seen an xorg update a few weeks ago, maybe that would be the reason? I am using nvidia TI4600, Compiz fusion and ubuntu gutsy gibbon on AMD Athlon XP2100+ w/ 1G ram. The crash of the x server is experienced when clicking in firefox on a link, and the system crashes before the link is actually opened (after logging in again, and starting firefox with 'resume session', the old page is displayed, not the page of which I clicked the link).

Similar bug as https://bugs.launchpad.net/bugs/140554 in which I posted a similar bug report a few weeks ago (found this thread by searching for the actual error of xorg/X FontFileComplete...., but the main error message in my syslog would be "gdm_slave_xioerror_handler: Fatal X error - Restarting :0"

Could it be firefox?
Could it be flash?
Could it be a bug in Xorg?
Someone tried another browser?

[the_streets (boeseboeseuni)]

I am experiencing this bug for a while now, so some more updates:

Mostly happens in Firefox (often like described above). Also happens regularly in Kile / Texmaker (which is very annoying) and while using Digitale Bibliotek in wine (<-- most reliable source for crashes, restarts gdm almost all the time). Often occurs while scrolling via the right border of the touchpad, occurs in any programs mentioned above and also in evince pdf viewer for example.

Mostly the restart is invoked by keyboard our touchpad usage, but not exclusively. It has also restarted while I was doing nothing.

So much for this totally annoying bug,
chris

[the_streets (boeseboeseuni)]

Dang, now i forgot the most important part:
I tried to evade the bug by turning off all desktop effects, but the bug also occurs with a new user and a blank session with all the effects switched off.

[ubertoo (ubertoo)]

I can confirm this as well. I do not believe it is related to the restricted driver, it happens no matter if I use the open source radeon driver, or ATI's fglrx in aiglx mode. It most notably occurs when pulling down yakuake, but it could happen in other applications as well. It could run fine for a few days, and then crash two or three times in one hour, usually it occurs about once a day (8 hour day). The issue does not occur if I switch window managers to kwin, as others have reported. I am also using 2.6.24-5-generic from Hardy (in a attempt to resolve this issue with no luck).

I did not notice this in Feisty, probably because I used fglrx with xgl instead aiglx. Could aiglx also be involved with this issue?

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xb7fcb420]
2: /usr/bin/X [0x817e4ad]
3: /usr/bin/X [0x817aaff]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x81613aa]
5: /usr/bin/X [0x8169029]
6: /usr/bin/X [0x8164425]
7: /usr/bin/X [0x815765e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dce450]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch
disable montype: 2
disable montype: 1
(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0): MC_FB_LOCATION : 0x1fff0000
(II) RADEON(0): MC_AGP_LOCATION : 0x27ff2000
finished PLL2
finished PLL1
Entering Restore TV
Restore TV PLL
Restore TVHV
Restore TV Restarts
Leaving Restore TV

[Adam Porter (alphapapa)]

Apparently my crashes were caused by a stick of memory that suddenly
went bad. It seems strange that the backtrace was always the same
(though I also developed kernel panics, etc), but memtest showed many
errors, and after locating the bad DRAM and removing it, the crashes
went away.

I doubt that everyone else's crashes are caused by bad memory, but if
you have time, it's probably worth running memtest (let it run all the
tests; only 2 of 7 found errors for me).

[casseen (bulkkasten)]

I have the same bug. I can reproduce it while using yakuake under gnome with compiz loaded.
Its gone as soon as compiz is deactivated or if i dont use yakuake. My Hardware is a HP Compaq 530 with Intel Corporation Mobile 945GME Express graphic adapter. Memtest has found no errors.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: /usr/bin/X [0x817e4ad]
3: /usr/bin/X [0x817aaff]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x81613aa]
5: /usr/bin/X [0x8169029]
6: /usr/bin/X [0x8164425]
7: /usr/bin/X [0x815765e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d41050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

[casseen (bulkkasten)]

I found out that yakuake is ignoring compiz's focus prevention. maybe thats the source of the bug? Meanwhile i use tilda as a replacement till this bug is fixed.

[pompo & khal (khalahan+ubuntu)]

Hi,

We also have this bug on 2 computers. One using ATI open source drivers, and the other with open source nvidia, both with compiz.
This bug occurs while we try to hide Firefox. To reproduce, we try to show/hide it repeatedly. If CPU is working a lot (with flash animations for example), it seems to occur more often.

After re-logging, gnome doesn't work properly (some applets broken until a complete reboot).

/var/log/gdm/*log :
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: /usr/bin/X [0x817e389]
3: /usr/bin/X [0x817ad15]
4: /usr/bin/X(CompositePicture+0x153) [0x8161223]
5: /usr/bin/X [0x81674ff]
6: /usr/bin/X [0x8164425]
7: /usr/bin/X [0x815765e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dbd050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

in syslog :
gdm_slave_xioerror_handler: Fatal X error - Restarting :0

This bug is marked as affecting "linux-restricted-modules-2.6.24 (Ubuntu)", should this be corrected ?

[Abhinay Mukunthan (lexxonnet)]

I've listed it as invalid on nvidia-glx-new, since it most definitely isn't a problem with the nvidia driver. I've experienced it on both nvidia and ati systems(using both the free and proprietary ati drivers and nvidia-glx-new). Furthermore, it has also been reported on an Intel card above.

The only common link is that all of them were using composite at the time. There is also a bug on the xorg bugzilla, which seems to be the same problem, here (https://bugs.freedesktop.org/show_bug.cgi?id=10617). So, I've linked this bug to that. All we can do now is wait I guess :)

[mmalmeida (mmalmeida)]

I have the exact same random crashes:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: /usr/bin/X [0x817e389]
3: /usr/bin/X [0x817ad15]
4: /usr/bin/X(CompositePicture+0x153) [0x8161223]
5: /usr/bin/X [0x81674ff]
6: /usr/bin/X [0x8164425]
7: /usr/bin/X [0x815765e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7de0050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

I am also using Avant Window Navigator, compiz, and Gutsy.

It seems to happen when I'm running Firefox or Amarok (and the above mentioned AWN).

[mmalmeida (mmalmeida)]

I forgot to mention:

Video card: Nvidia Geforce 8600 GTS
Ubuntu 7.10
X Protocol Version 11, Revision 0, Release 1.3

[Adam Porter (alphapapa)]

What video driver and version, and installed how, from where?

On Tue, Apr 22, 2008 at 2:09 PM, wild_oscar <email address hidden> wrote:
> I forgot to mention:
>
> Video card: Nvidia Geforce 8600 GTS
> Ubuntu 7.10
> X Protocol Version 11, Revision 0, Release 1.3
>
>
>
> --
> Xorg crashes with /usr/bin/X(FontFileCompleteXLFD+0x1e1)
> https://bugs.launchpad.net/bugs/165093
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[mmalmeida (mmalmeida)]

Nvidia driver version 100.14.19, installed through Gutsy-updates' official repositories (package nvidia-glx-new).

[lesshaste (clifford-cs)]

I have a similar looking X crash which is intermittent in Hardy but never occurred in Gutsy. I get

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7f5d420]
2: /usr/lib/xorg/modules//libxaa.so [0xb76166dd]
3: /usr/bin/X [0x8172db4]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x815a33a]
5: /usr/bin/X [0x8161cc9]
6: /usr/bin/X [0x815d055]
7: /usr/bin/X [0x81506de]
8: /usr/bin/X(Dispatch+0x2cf) [0x808d8df]
9: /usr/bin/X(main+0x48b) [0x807471b]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7cee450]
11: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

Fatal server error:
Caught signal 11. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch

I am using fglrx and the onboard graphics card is

01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] [1002:5954] (prog-if 00 [VGA controller])

Raphael

[Abhinay Mukunthan (lexxonnet)]

Seems to be the same issue. I have a new laptop with an nvidia card now... and it still happens from time to time, especially when I open the mail component of kontact from the system tray.

[qburn (qburn)]

The same random Xorg crashes on Dell OptiPlex GX280 stations, I got the same backtrace on Gutsy ,

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: /usr/bin/X [0x817e389]
3: /usr/bin/X [0x817ad15]
4: /usr/bin/X(CompositePicture+0x153) [0x8161223]
5: /usr/bin/X [0x81674ff]
6: /usr/bin/X [0x8164425]
7: /usr/bin/X [0x815765e]
8: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
9: /usr/bin/X(main+0x495) [0x8076f05]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d8c050]
11: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04)

Mike

[pongtawat (pongtawat)]

I probably have the same problem. It happens most of the time I try to open Nautilus folder in browse mode. I'm running Ubuntu 8.04 with ATI X1550 and ATI Catalyst 8.5 driver.

If compiz is not enable, there is no problem at all.

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x48402a]
1: /lib/libc.so.6 [0x7f8292334100]
2: /usr/lib/dri/fglrx_dri.so [0x7f828cd98850]
3: /usr/lib/dri/fglrx_dri.so [0x7f828cda77f2]
4: /usr/lib/dri/fglrx_dri.so [0x7f828cdb446f]
5: /usr/lib/dri/fglrx_dri.so [0x7f828cdb7c10]
6: /usr/lib/dri/fglrx_dri.so [0x7f828cdb84cd]
7: /usr/lib/dri/fglrx_dri.so [0x7f828c8d60f1]
8: /usr/lib/dri/fglrx_dri.so [0x7f828cb7d662]
9: /usr/lib/xorg/modules/extensions//libglx.so [0x7f829133775d]
10: /usr/lib/xorg/modules/extensions//libglx.so [0x7f8291304462]
11: /usr/lib/xorg/modules/extensions//libglx.so [0x7f8291303c12]
12: /usr/lib/xorg/modules/extensions//libglx.so [0x7f8291307c6c]
13: /usr/bin/X(Dispatch+0x2ef) [0x44eaaf]
14: /usr/bin/X(main+0x47d) [0x436b9d]
15: /lib/libc.so.6(__libc_start_main+0xf4) [0x7f82923201c4]
16: /usr/bin/X(FontFileCompleteXLFD+0x279) [0x435ed9]

Fatal server error:
Caught signal 8. Server aborting

[avenger (bole-chen)]

I have a similar looking X crash which is intermittent in Hardy but never occurred in Gutsy. I get

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7f0e420]
2: /usr/lib/xorg/modules//libxaa.so [0xb75ad6dd]
3: /usr/bin/X [0x8172e24]
4: /usr/bin/X(CompositeGlyphs+0x9a) [0x815a36a]
5: /usr/bin/X [0x8161d29]
6: /usr/bin/X [0x815d085]
7: /usr/bin/X [0x81506ee]
8: /usr/bin/X(Dispatch+0x2cf) [0x808d8df]
9: /usr/bin/X(main+0x48b) [0x807471b]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7ca3450]
11: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

Fatal server error:
Caught signal 11. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch

my video card is Ati X1300 on Lenovo T60

[Evance Mok (emok-speedburst)]

I was able to reproduce this problem pretty easily using the method described here: https://bugs.launchpad.net/ubuntu/+source/nspluginwrapper/+bug/241145

It *seemed* to only happen with the flashplugin-nonfree package installed.

I added 'Option "XaaNoOffscreenPixmaps"' to my xorg.conf file and I HAVE NOT been able to reproduce this issue. It seems to have solved the issue I was having that looked similar to this.

My configuration:
Hardy (AMD64)
fglrx (latest ubuntu package)
flashplugin-nonfree
compiz enabled

Here's the Xorg.0.log I was getting previously:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x6a) [0x48402a]
1: /lib/libc.so.6 [0x7f8e32203100]
2: /usr/lib/xorg/modules//libxaa.so [0x7f8e2f772c9c]
3: /usr/lib/xorg/modules//libxaa.so [0x7f8e2f772e96]
4: /usr/bin/X [0x527ea2]
5: /usr/bin/X [0x515c3f]
6: /usr/bin/X(Dispatch+0x2ef) [0x44eaaf]
7: /usr/bin/X(main+0x47d) [0x436b9d]
8: /lib/libc.so.6(__libc_start_main+0xf4) [0x7f8e321ef1c4]
9: /usr/bin/X(FontFileCompleteXLFD+0x279) [0x435ed9]

Fatal server error:
Caught signal 11. Server aborting

(II) AIGLX: Suspending AIGLX clients for VT switch

[Evance Mok (emok-speedburst)]

Update to my above post:

Even with that option, I'm still having the issue, although it appears to be less frequent.

[Evance Mok (emok-speedburst)]

In my latest tests, I reverted the xorg.conf back to the previous state without the Xaa options.

I've been testing with flashplugin-nonfree, gnash and swfdec individually and I only see the issue when using flashplugin-nonfree.

Then I followed the directions on this thread near the bottom of the first post: http://ge.ubuntuforums.com/showthread.php?t=772490 with the heading "Flash 10 beta" and have installed the flash 10 plugin (just released on Jul 2?). I've been hammering away at the system, using firefox with up to 60+ instances/tabs of the same flash-loaded sites that I've been using previously to reproduce the issue and I have not had a single occurrence.

Anyone else tried this yet and what are your results?