| 1 | = Troubleshooting = |
| 2 | [[PageOutline(2-4,, inline)]] |
| 3 | |
| 4 | == Segmentation fault in Ubuntu 11.10 == |
| 5 | If the reconstructor crashes like that (numbers can vary): |
| 6 | |
| 7 | {{{ |
| 8 | $ ./3dbar.sh |
| 9 | ./3dbar.sh: line 17: 2296 Segmentation fault python bin/reconstructor/gui.py |
| 10 | }}} |
| 11 | |
| 12 | the reason can be a bug in the 'python-vtk' package installed in your system. |
| 13 | Unfortunately there is no automated way to fix it - you have to do it manually: |
| 14 | |
| 15 | 1. Find a file named 'wxVTKRenderWindowInteractor.py'. It can be located |
| 16 | in '/usr/share/pyshared/vtk/wx/' directory or in similar location: |
| 17 | |
| 18 | {{{ |
| 19 | $ find / -name 'wxVTKRenderWindowInteractor.py' |
| 20 | }}} |
| 21 | |
| 22 | 2. Edit the file with your favourite ASCII editor. In the example editor 'vim' |
| 23 | is used and it is assumed that the path to the file is |
| 24 | '/usr/share/pyshared/vtk/wx/wxVTKRenderWindowInteractor.py': |
| 25 | |
| 26 | {{{ |
| 27 | $ sudo vim /usr/share/pyshared/vtk/wx/wxVTKRenderWindowInteractor.py |
| 28 | }}} |
| 29 | |
| 30 | 3. Near 350th line of the file find a following line: |
| 31 | |
| 32 | {{{ |
| 33 | d = '_%s_%s' % (d[2:], 'void_p') |
| 34 | }}} |
| 35 | |
| 36 | 4. Add '\0' characters to the line to make it like below: |
| 37 | |
| 38 | {{{ |
| 39 | d = '_%s_%s\0' % (d[2:], 'void_p') |
| 40 | }}} |
| 41 | |
| 42 | 5. Save the modified file. |
| 43 | |
| 44 | |
| 45 | 6. The bug should be fixed for now. Try running 3dBAR again. If this solution |
| 46 | doesn't work - let us know. |