Comment # 4 on bug 1171893 from Robin Roevens

Thanks. I pulled the new image today, and this issue indeed seems fixed.