This bug -- or something remarkably similar to it -- has reappeared in 1.17.2 (latest X package in Fedora 22).
This bug -- or something remarkably similar to it -- has reappeared in 1.17.2 (latest X package in Fedora 22).