This issue is still present in 3.13.92-1.I can confirm that undoing 18_all_displays_transient.patch resolved the problem in 3.12-4 (haven't rebuilt 3.13.92-1 yet).
How comes that this is still not fixed even though the problematic code change is identified?
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
