Red Hat Bugzilla – Bug 541986
Wine -- winecfg crashes clicking the Audio tab when wine-{alsa,pulseaudio,oss} are installed
Last modified: 2010-07-22 22:49:22 EDT
Description of problem: The winecfg component of Wine in x86_64 installations of Wine crashes when the Audio tab is clicked and any of the audio controllers (drivers) are installed (wine-alsa, wine-pulseaudio, wine-oss), wine-openal does not cause this (but apparently it is not a "driver" as such). When launching winecfg from the console there is output from apparently random memory addresses, but not a formal backtrace as such. Version-Release number of selected component (if applicable): wine-core-1.1.32 wine-common-1.1.32 wine-alsa-1.1.32 || wine-pulseaudio-1.1.32 || wine-oss-1.1.32 How reproducible: Always Steps to Reproduce: 1. Install wine-common, wine-core and any of the audio controllers. 2. Open winecfg to try to setup an audio device. 3. See the Windows-like dialog box appear of winedbg entering an infinite loop. Actual results: The winecfg tool crashes when trying to setup an audio device for Wine. Expected results: To be able to configure an audio device for Wine.
This is a duplicate of #522941 -- first section. Also, from Comment 3 there: This is a bug in 64bit wine. See http://bugs.winehq.org/show_bug.cgi?id=19316. To run the 32bit winecfg type 'wine32 winecfg' BUT, based on comments I read on the winehq link ("Wine compiled as 64-bit is highly experiential and won't run anything other then 64-bit code."), I decided to 'yum remove wine-*.x86_64' and would recommend the same to anyone having this problem and not explicitly using 64-bit windows programs. Now winecfg works correctly without having to use wine32.
I was experiencing this problem and running 'wine32 winecfg' worked in version 1.1.29. However, doing so in 1.1.38 doesn't run winecfg at all and my windows app (Pokerstars) does not run either. This started at 1.1.36 and continues with version 1.1.38 so some broader problem is present.
*** Bug 585423 has been marked as a duplicate of this bug. ***
*** Bug 591711 has been marked as a duplicate of this bug. ***
wine-1.2.0-0.4.rc4.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/wine-1.2.0-0.4.rc4.fc12
wine-1.2.0-0.4.rc4.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/wine-1.2.0-0.4.rc4.fc13
wine-1.2.0-0.4.rc4.fc13 has been pushed to the Fedora 13 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: http://admin.fedoraproject.org/updates/wine-1.2.0-0.4.rc4.fc13
This does seem to be fixed with wine-1.2.0-0.4.rc4.fc13. Thanks.
wine-1.2.0-0.6.rc6.fc13 has been pushed to the Fedora 13 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: http://admin.fedoraproject.org/updates/wine-1.2.0-0.6.rc6.fc13
wine-1.2.0-0.7.rc7.fc13 has been pushed to the Fedora 13 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: http://admin.fedoraproject.org/updates/wine-1.2.0-0.7.rc7.fc13
wine-1.2.0-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
wine-1.2.0-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.