answered 2010-12-21 15:39:52 +0200
This is indeed a known bug #10466. I don't know a convenient way to work around this at the moment.