There is workaround as explained in bug #479213. But then you face issue #479213, which is better for the moment i think.
There is workaround as explained in bug #479213. But then you face issue #479213, which is better for the moment i think.