This is now fixed by revision rev#68058.