Ah, I see. Thanks for the clarification. Yes, that sounds like a bug to me.
I'll test with the upstream version and see if the problem exists there (I assume it will - I don't think any of our packaging would cause this), and then forward upstream. Thanks for your report!
