http://bugs.winehq.org/show_bug.cgi?id=58371
--- Comment #8 from Rafał Mużyło galtgendo@o2.pl --- Hmm...
On one hand, the responder seems to be going over last week or so through a minor meltdown alike to one of my own extended hissfits.
On the other, the report looked somewhat lacking (and any reporter should read either a project-specific document or a more generic one, just so they (roughly) known what info is relevant and how can they provide it; also that GE version besides being a mini-fork, looks also quite a bit out of date).
Though given this specific bug, getting good info might be tricky. It's not a crasher, just a possible input handling bug. It might be processing the input, it might be input focus - it *seems* 'keyboard' is the debug channel you should look at. Does the problem still happen if you assign the function to a different key ?
(also, there's still a chance it's something specific to the reporter's hardware setup)
I'd say it's a coin toss if this will be something interesting or not - if it actually pops up *exactly* 4 times on each press (and isn't a hardware problem), it would be a bit too consistent for a simple timing bug...