I'm getting an immediate seg fault when starting blender on fedora core 8.
I tried this to narrow it down a bit more:
This was with the fedora 8 blender package (I also tried
blender from blender.org, see below)
[root@zuul bin]# mv blender.bin blender.bin.real
[root@zuul bin]# vi blender.bin
[root@zuul bin]# cat blender.bin
#!/bin/sh
gdb blender.bin.real
And by the means was able to get a backtrace:
(gdb) bt
#0 0x00dfcf12 in ?? () from /usr/lib/dri/unichrome_dri.so
#1 0x00e92b70 in ?? () from /usr/lib/dri/unichrome_dri.so
#2 0x00e93cb2 in ?? () from /usr/lib/dri/unichrome_dri.so
#3 0x00e8ad8f in ?? () from /usr/lib/dri/unichrome_dri.so
#4 0x00df0430 in ?? () from /usr/lib/dri/unichrome_dri.so
#5 0x00e8b2ee in ?? () from /usr/lib/dri/unichrome_dri.so
#6 0x00e8391c in ?? () from /usr/lib/dri/unichrome_dri.so
#7 0x00e7f0a8 in ?? () from /usr/lib/dri/unichrome_dri.so
#8 0x00e7f1fc in ?? () from /usr/lib/dri/unichrome_dri.so
#9 0x00e824d8 in ?? () from /usr/lib/dri/unichrome_dri.so
#10 0x00f14033 in ?? () from /usr/lib/dri/unichrome_dri.so
#11 0x081b77a4 in BIF_ThemeColorShadeAlpha ()
#12 0x08187edd in ?? ()
#13 0x00000021 in ?? ()
#14 0x00000000 in ?? ()
(gdb)
I also tried the blender from blender.org for python 2.5
and got essentially the same back trace, but with a little
more info:
[scameron@zuul software]$ cd blender-2.45-linux-glibc236-py25-i386
[scameron@zuul blender-2.45-linux-glibc236-py25-i386]$ ls
blender copyright.txt release_240.txt release_244.txt
blender.html GPL-license.txt release_241.txt release_245.txt
blenderplayer plugins release_242.txt
BlenderQuickStart.pdf Python-license.txt release_243.txt
[scameron@zuul blender-2.45-linux-glibc236-py25-i386]$ gdb ./blender
[ ...snip... ]
(gdb) bt
#0 0x00dfcf12 in ?? () from /usr/lib/dri/unichrome_dri.so
#1 0x00e92b70 in ?? () from /usr/lib/dri/unichrome_dri.so
#2 0x00e93cb2 in ?? () from /usr/lib/dri/unichrome_dri.so
#3 0x00e8ad8f in ?? () from /usr/lib/dri/unichrome_dri.so
#4 0x00df0430 in ?? () from /usr/lib/dri/unichrome_dri.so
#5 0x00e8b2ee in ?? () from /usr/lib/dri/unichrome_dri.so
#6 0x00e8391c in ?? () from /usr/lib/dri/unichrome_dri.so
#7 0x00e7f0a8 in ?? () from /usr/lib/dri/unichrome_dri.so
#8 0x00e7f1fc in ?? () from /usr/lib/dri/unichrome_dri.so
#9 0x00e824d8 in ?? () from /usr/lib/dri/unichrome_dri.so
#10 0x00f14033 in ?? () from /usr/lib/dri/unichrome_dri.so
#11 0x081f1cd0 in BIF_ThemeColorShadeAlpha ()
#12 0x082ce924 in draw_object ()
#13 0x081919f7 in drawview3dspace ()
#14 0x081b7fed in scrarea_do_windraw ()
#15 0x081c1b09 in screenmain ()
#16 0x081865a6 in main ()
(gdb)
:
[scameron@zuul ~]$ rpm -qf /usr/lib/dri/unichrome_dri.so
mesa-libGL-7.0.1-7.fc8
Maybe it's a mesa-libGL problem?
-- steve
Description
Description
Event Timeline
Comment Actions
This is a generic request to test your bug report and see if it is still an issue in 2.5alpha2 if so please let me know by making a comment in this report ie 'also in 2.5alpha2' and I will add it to the 2.5 bug list.