xorg-server @1.11.3_0 crashes in Lion 10.7.2 running gschem

[slarew@…]

I was running gschem in the macports version of X11.app when X11.app suddenly crashed. Unfortunately, I can't recall what the exact action I was that I was performing at the time but it was a basic operation in gschem such as inserting a symbol or using a menu. I'm not sure if this is an X11 problem or gschem problem but since the X11.app process crashed and not just gschem, I'm inclined to believe the problem lies in X11.app.

I am running 10.7.2 with Xcode 4.2.1. I have attached the crash log generated by OSX and below is the what was found in Console.app at the time of the crash. I hope it helps.

1/2/12 3:04:41.656 PM org.macports.startx: xinit: XFree86_VT property unexpectedly has 0 items instead of 1
1/2/12 3:04:41.679 PM org.macports.startx: /opt/local/bin/xset:  bad font path element (#8), possible causes are:
1/2/12 3:04:41.679 PM org.macports.startx:     Directory does not exist or has wrong permissions
1/2/12 3:04:41.679 PM org.macports.startx:     Directory missing fonts.dir
1/2/12 3:04:41.679 PM org.macports.startx:     Incorrect font server address or syntax
1/2/12 3:08:18.707 PM org.macports.X11.stub: Xquartz: start_x11_server: (ipc/mig) server died
1/2/12 3:08:18.712 PM org.macports.startx: xinit: connection to X server lost
1/2/12 3:08:18.712 PM com.apple.launchd.peruser.501: ([0x0-0x29a29a].org.macports.X11[10923]) Job appears to have crashed: Segmentation fault: 11
1/2/12 3:08:18.984 PM ReportCrash: Saved crash report for X11.bin[10923] version 2.7.0 (2.7.0) to /Users/***/Library/Logs/DiagnosticReports/X11.bin_2012-01-02-150818_jeeves.crash
1/2/12 3:08:19.000 PM kernel: nstat_lookup_entry failed: 2

[slarew@…]

X11.app crash report

[slarew@…]

Another X11.app crash report due to similar behavior.

[jeremyhu (Jeremy Huddleston Sequoia)]

0   X11.bin                             0x0000000104b68319 damageRegionAppend + 281
1   X11.bin                             0x0000000104b26a77 fbShapes + 135
2   X11.bin                             0x0000000104b269e9 fbTrapezoids + 89
3   X11.bin                             0x0000000104b5fca8 ProcRenderTrapezoids + 392
4   X11.bin                             0x0000000104bb701b Dispatch + 731
}}]

Yes.  If the server crashes, it's the server's fault.  No client input should cause it to crash.

Unfortunately, there's nothing I can do without more info.  If you can tell me what you do to cause the crash, that will help.