https://bugs.winehq.org/show_bug.cgi?id=39891
--- Comment #37 from Omar Pakker wine@opakker.nl --- I didn't realize there was really a difference between 'RESOLVED' and 'CLOSED' tbh haha. The best I can guess is it'd normally stay on RESOLVED until someone else verifies it then CLOSED? Though that leaves a bit of a weird situation for 'NOTOURBUG' cases imo.
Anyway, if CLOSED (+ NOTOURBUG) is for when it's fixed upstream, I think your change to CLOSED was actually good. As far as I'm aware it has been included in the upstream/kernel xpad driver for a while now. Commit b6fc513.
With a quick search, said commit should have been included since the following releases: - 4.10 (the stable branch at the time) - 4.9.5 (longterm branch) - 4.4.44 (longterm branch)