System Enviroment: -------------------------- Arch: 945gm i386 OSD: Fedora Core release 5 (Bordeaux) Kernel: 2.6.20 Mesa: af807a4696866a4ee08bb2a4e95b9c02011db530 Drm: 833df88d0d63bc96dcc57d0193d133b2a594e1d6 Bug detailed description: -------------------------- ut2004 got the following error: open /dev/[sound/]dsp: No such file or directory Xlib: extension "XiG-SUNDRY-NONSTANDARD" missing on display ":0.0". [driAllocateTexture:636] unable to allocate texture [driAllocateTexture:636] unable to allocate texture ......... ......... [driAllocateTexture:636] unable to allocate texture [driAllocateTexture:636] unable to allocate texture [driAllocateTexture:636] unable to allocate texture Signal: SIGSEGV [segmentation fault] Aborting. Reproduce steps: ---------------- 1.startup X 2.run ut2004 3.click "Instant Action"->"Asault"->"Play"
Created attachment 9538 [details] UT2004.log
Created attachment 9539 [details] xorg.conf
Created attachment 9540 [details] Xorg.0.log
commit 565cd49b5fc7a5bd1e533542888bf322b83b8e56 fixes the segment issue
the bug arised again on mesa commit <7eba12edce871c3db835decbf1a0271acfd3eb68> tested on 945g
Are you sure about that commit? It was just a change to an html file, AFAICT.
Sorry for my fault,the bug was found on Mesa commit <47ad443c55cf07b32bac04b97066cfd3c2aa3554>.
Uh, that commit was a change to the glfbdev.c file: http://gitweb.freedesktop.org/?p=mesa/mesa.git;a=commit;h=47ad443c55cf07b32bac04b97066cfd3c2aa3554
Sorry for that mistake. I just want to point out that this bug happened on the newer commit, but not that the commit caused the bug.
if DefaultDepth value was set to 16 in xorg.conf, then running ut2004 through ssh, Segmentation Fault would arise and X crashes too. it is duplicate of bug #10778
the original segmentation fault has been fixed by Haihao as comment#4
The new bug (X crashes if depth=16, as mentioned in comment#10) has been fixed by Haihao in xf86-video-driver commit 34f362d099d255f8f0bb34e9de30f953ee770163.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.