As you said here, it's a different bug, just something which survived because I almost never use a pad in the gui because it's inefficient (even though it's fun with the autorepeat). It's just a gui bug, when you press the controller button to return to the game, the game thinks your button is still down while it's up, to work around that just press the button again when you'll be ingame, you'll notice that the character won't play its fist animation (if it was button 1), press it a 2nd time and this time you'll have the fist animation, you're back to normal and you can do the double-tap again.
There was still a little bug in my cancel sticks logic, I made it global so that if you play on 1 pad using the d-pad and another using a stick, you would create havoc, the 2nd pad would cancel the 1st pad !
I fixed it here, but it should already be ok for 1 player on your side.
I'll fix the gui problem with the pad later, thanks for your report anyway !
edit : you got new binaries for windows, december 22nd. The gui bug was actually recent, it's because I added something so that the game part can pre-process the gui events to simplify the code and avoid to duplicate things. It pre-processed the buttondown event, but not the buttonup, yeah I might have gone a little too fast on this one ! Anyway 2 new binaries, probably the last ones for 0.92.4 this time, it's for windows only of course.