Hans, I'm glad db4tech fixed your issue, but I would be really astonished that re-saving might have changed anything!
If you have a quick look at the stack information in the log files you posted:
Stack: [0x11a5f000,0x11ab0000], sp=0x11aae830, free space=13e11aae1c0k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libGL.so.1+0x3dd3e]
C [i915_dri.so+0x49486]
C [i915_dri.so+0x49506]
C [i915_dri.so+0x908f3] _mesa_flush+0x23
C [i915_dri.so+0x49d65] intelMakeCurrent+0x45
C [i915_dri.so+0x217a2]
C [libGL.so.1+0x3d30c]
C [libGL.so.1+0x18e62] glXMakeCurrentReadSGI+0x432
C [libGL.so.1+0x18f33] glXMakeCurrent+0x23
C [libj3dcore-ogl.so+0xbd57] Java_javax_media_j3d_NativePipeline_createNewContext+0x155
j javax.media.j3d.NativePipeline.createNewContext(Ljavax/media/j3d/Canvas3D;JJJJZZZZ)J+0
[...]createNewContext and then intelMakeCurrent makes me think more about a driver problem (you can deduce recent history in a program by reading a crash stack upside down, the most recent thing that happened being first cited).
Didn't you update drivers recently?
----------------------------------------
Emmanuel Puybaret, Sweet Home 3D creator
