| 147 | |
| 148 | |
| 149 | == Troubleshooting == |
| 150 | === Segmentation fault in Ubuntu 11.10 === |
| 151 | If the reconstructor crashes like that (numbers can vary): |
| 152 | |
| 153 | {{{ |
| 154 | $ ./3dbar.sh |
| 155 | ./3dbar.sh: line 17: 2296 Segmentation fault python bin/reconstructor/gui.py |
| 156 | }}} |
| 157 | |
| 158 | the reason can be a bug in the 'python-vtk' package installed in your system. |
| 159 | Unfortunately there is no automated way to fix it - you have to do it manually: |
| 160 | |
| 161 | 1. Find a file named 'wxVTKRenderWindowInteractor.py'. It can be located |
| 162 | in '/usr/share/pyshared/vtk/wx/' directory or in similar location: |
| 163 | |
| 164 | {{{ |
| 165 | $ find / -name 'wxVTKRenderWindowInteractor.py' |
| 166 | }}} |
| 167 | |
| 168 | 2. Edit the file with your favourite ASCII editor. In the example editor 'vim' |
| 169 | is used and it is assumed that the path to the file is |
| 170 | '/usr/share/pyshared/vtk/wx/wxVTKRenderWindowInteractor.py': |
| 171 | |
| 172 | {{{ |
| 173 | $ sudo vim /usr/share/pyshared/vtk/wx/wxVTKRenderWindowInteractor.py |
| 174 | }}} |
| 175 | |
| 176 | 3. Near 350th line of the file find a following line: |
| 177 | |
| 178 | {{{ |
| 179 | d = '_%s_%s' % (d[2:], 'void_p') |
| 180 | }}} |
| 181 | |
| 182 | 4. Add '\0' characters to the line to make it like below: |
| 183 | |
| 184 | {{{ |
| 185 | d = '_%s_%s\0' % (d[2:], 'void_p') |
| 186 | }}} |
| 187 | |
| 188 | 5. Save the modified file. |
| 189 | |
| 190 | |
| 191 | 6. The bug should be fixed for now. Try running 3dBAR again. If this solution |
| 192 | doesn't work - let us know. |