Hi I'm using Ubuntu 11.04 with ATI driver 11.5 (HD 5850), from time to time I've got WUs who end up erroring, here's the Stderr output :

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
Type error: (null) expected, got nil
Error evaluating 'constants': Expected constant 'wedge' to be a number
 
Error evaluating 'area': bad argument #1 to '?' (table expected, got nil) 
Error evaluating 'background': bad argument #1 to '?' (table expected, got nil) 
Type error: (null) expected, got nil
Error evaluating 'streams': Expected 'streams' to be a table 
Error reading astronomy parameters from file 'astronomy_parameters.txt'
  Trying old parameters file
Error reading number_parameters
16:45:47 (5278): called boinc_finish

</stderr_txt>
]]>

Having an error on one WU isn't really a big deal, the problem is that my PC completly froze and I have to reboot it manualy wich is a lot more anoying.
An idea of ​​where this might come from?

Hi I'm using Ubuntu 11.04 with ATI driver 11.5 (HD 5850), from time to time I've got WUs who end up erroring, here's the Stderr output :

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
Type error: (null) expected, got nil
Error evaluating 'constants': Expected constant 'wedge' to be a number
 
Error evaluating 'area': bad argument #1 to '?' (table expected, got nil) 
Error evaluating 'background': bad argument #1 to '?' (table expected, got nil) 
Type error: (null) expected, got nil
Error evaluating 'streams': Expected 'streams' to be a table 
Error reading astronomy parameters from file 'astronomy_parameters.txt'
  Trying old parameters file
Error reading number_parameters
16:45:47 (5278): called boinc_finish

</stderr_txt>
]]>

Having an error on one WU isn't really a big deal, the problem is that my PC completly froze and I have to reboot it manualy wich is a lot more anoying.

Don't think this would be related to that.

An idea of ​​where this might come from?

This would happen if the parameter file that it tries to open is completely blank. Perhaps the workunit's download did not work correctly or something like that and BOINC decided to run it anyway.