a user submitted the following bug report:
I'm unable to reproduce this issue in F20/x86-64 (and previously on
F19/x86-64). Can someone still using i686 give a try?
BTW, this issue seems to have been reported upstream and they are unwilling
to find the bug, blaming gcc 4.8.