Hmm, this is probably not the same bug. What Thorsten reported is a real failure. Mine is just an undesired warning. (Not sure if they have a common cause) Thanks.