Description of problem: Wine 1.3.6 added system cursors as a feature. This works... if you have libXcursor.i686 installed on a 64-bit system. Version-Release number of selected component (if applicable): wine-1.3.6-1.fc14.x86_64 How reproducible: Always Steps to Reproduce: 1. Load a fresh F14 system. 2. Run winecfg. Actual results: White Windows XP cursor Expected results: Black Fedora cursor Additional info: yum install libXcursor.i686 fixes this. Add a depends on libXcursor since wine dlopen()s this?
Thanks for reporting. Will be fixed with the next push.
wine-1.3.8-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/wine-1.3.8-1.fc14
wine-1.3.8-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/wine-1.3.8-1.fc13
wine-1.3.8-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update wine'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/wine-1.3.8-1.fc14
wine-1.3.8-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
wine-1.3.8-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
I am currently running the latest(1.3.9) testing version with WOW. I have the libXcursor.i686 installed, thus I have no problem with the cursor. Is this bug for x86_64 straight builds, WOW builds, or both? I could not find libXcursor.i686 to be a dependency for either wine.x86_64 nor wow. I have a few programs that depend on libXcursor.i686 so I could not remove it and test without it.
The problem should be fixed by the added deps in wine-core: rpm -q wine-core wine-core-1.3.9-1.fc14.x86_64 wine-core-1.3.9-1.fc14.i686 rpm -q --requires wine-core | grep cursor 12:libXcursor(x86-64) 80:libXcursor(x86-32)
I checked. I got the same thing.