Bug 801436
| Summary: | Support for xinput2 disabled in wine build | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Oleg Girko <ol+redhat> |
| Component: | wine | Assignee: | Andreas Bierfert <andreas.bierfert> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | andreas.bierfert, araujo.rm, goeran, jmontleo, stefan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | wine-1.5.2-2.fc15 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-02 20:52:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Oleg Girko
2012-03-08 14:31:28 UTC
I can confirm this still occurs in the recent wine 1.5.0-2 update, which incidentally, installed itself over the 1.4-1 version I had rebuilt without the non-sensical "--without-xinput2" parameter. After rebuilding it again myself with "--without-xinput2" parameter removed from "%configure" arguments, wine is working correctly again with games (tested with Mass Effect 3). with 1.4 / 1.5.1 on Fedora 16 UT3 does not work correctly without xinput2 either. You either have to deal with navigating the menus with the keyboard or have the mouse broken in game without it. The fix is simple for fc15 onwards: just remove --without-xinput2 from the spec file and rebuild, as described above. AFAIK xinput2 support in wine has been stable for a while now, and it only is activated if you select the option to capture the mouse in full screen applications. Given how easy it is to fix, it's strange that it hasn't been already. Recently there was another update to the package that didn't include this fix and if you had (like me) rebuilt the previous version, this update has overwritten it. Is it possible to do that on the next update? Or is there a strong reason against it and people who need it will just have to exclude wine-* from yum updates? Best regards. I have enabled this last week with 1.5.2-2 build. However this will need some further testing as this will fix some issues but leave other people with bugs. wine-1.5.2-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/wine-1.5.2-2.fc16 wine-1.5.2-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/wine-1.5.2-2.fc17 wine-1.5.2-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/wine-1.5.2-2.fc15 Thanks! I just downloaded the built RPMs for fc16 and freshened them (i686, although it's a 64 bit system). For now all seems well (can play Mass Effect 3). I'll report back here should I find anything bad. Best regards. Package wine-1.5.2-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wine-1.5.2-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6477/wine-1.5.2-2.fc17 then log in and leave karma (feedback). wine-1.5.2-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. wine-1.5.2-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. wine-1.5.2-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 795147 has been marked as a duplicate of this bug. *** |