Comment 4 for bug 1044559

I just saw this exact behavior while using a 1.8.0 development package on Trusty. Not sure what the correct process to reopen a bug is, but I think this either wasn't fully fixed, or there has been a regression.