I'm still getting that error with 1.0.9-1...not sure if you'd even looked at it for this update, but thought I'd give a heads up in case you had.