Looks like it was bug 278052 that broke this (for the current situation, this bug may have been something else from start...)
Looks like it was bug 278052 that broke this (for the current situation, this bug may have been something else from start...)