Winecfg audio tests fail in Maverick

Could you try with the latest Wine and, in case it is still an issue, provide a log? Maybe it is related to https://bugs.launchpad.net/ubuntu/+source/wine1.2/+bug/502375

Same problem using package version 1.2-0ubuntu2. Please could you tell me where to find the audio test logfile?

Thanks

I just updated ia32-libs and wine1.2 for Maverick and tested and it seems to work. Let me know if this is still a problem. Thank you for reporting!

Hi Scott,

I have updated to the latest version of the Wine package and I still have no luck with the audio tests. (I don't have ia32-libs because I am running i386). Please could you let me know how to generate a suitable log file?

$ apt-cache policy wine1.2
wine1.2:
  Installed: 1.2-0ubuntu4
  Candidate: 1.2-0ubuntu4
  Version table:
 *** 1.2-0ubuntu4 0
        500 http://gb.archive.ubuntu.com/ubuntu/ maverick/universe i386 Packages
        100 /var/lib/dpkg/status

Thank you for posting this bug.

Does this occur in newest WINE?

This is an issue with 1.2 in Maverick and needs Scott's reply -- please actually read the bugs

I uninstalled wine1.2, deleted my ~/.wine folder and reinstalled. The bug no longer appears to exist.

leighman thank you for your contribution on this this bug. Yes, Scott is a fabulous resource regarding WINE issues and I am marking this issue Incomplete due to this. However, I feel comfortable contributing in the best that I can and do not appreciate your being presumptuous in thinking I did not read this post. To maintain a respectful atmosphere, please follow the code of conduct - http://www.ubuntu.com/community/conduct/ . Bug reports are handled by humans, the majority of whom are volunteers, so please bear this in mind.

Hi rusivi1,

Please don't be offended by the earlier comment. Your help with triaging is much appreciated - it's important, however, to take note of the subtle details in bug reports. I was actually the one who set the bug status to Invalid. This is because I was the original reporter, no one was able to confirm this report and I have since found that the bug is no longer present in a completely clean installation of the latest Ubuntu wine package. Therefore, the bug was most likely due to some messed up configuration on my own machine (probably my own fault) and nothing to do with the package itself.