There's nothing to fix for 5.5.z regarding this bug. This problem has been fixed in current 5.5, the symptoms now showing are in fact a different bug (bug #1272266), which should be resolved for 5.5.z. I'm closing this one with wontfix.