When searching at google for this bug it seems that most cases of this error are caused by unicode/non-unicode compliance. They have committed a fix now (dec 2007) so i propose this bug being closed and re-opened if Akshat reports if this bug is still residing in feisty.
When searching at google for this bug it seems that most cases of this error are caused by unicode/non-unicode compliance. They have committed a fix now (dec 2007) so i propose this bug being closed and re-opened if Akshat reports if this bug is still residing in feisty.