Sound configuration error on wine 1.3.1

Bebado · Post by **Bebado** » Sat Aug 21, 2010 1:43 pm

Hi all.

So i compiled the recently released wine 1.3.1, and i'm in a predicament related to the sound configuration, that never happened in previous wine versions. Whenever i try to configure sound, using winecfg, wine crashes, also running applications just end with the same exact crash.

Should i fill a bug report?

Here is a debug log for additional information.

Bebado · Post by **Bebado** » Sat Aug 21, 2010 1:56 pm

Let me translate the second line in the debug log, that somehow is in portuguese.

It is readable as:

simple.c:173: snd_mixer_selem_get_name: Asserção `elem' falhou.

I think the translation to english should be somewhat like this:

simple.c:173: snd_mixer_selem_get_name: `elem' assertion failed.

Bebado · Post by **Bebado** » Sun Aug 22, 2010 6:55 am

Sorry for the three posts in a row, but i just confirmed it isn't just a problem related to my compilation. I downloaded the wine 1.3.1 binaries from PlayOnLinux and the the bug i described also ocurrs.

I'll be definitively fill a bug report when i have the spare time to do it, though i'm yet to see someone complaining about a similar error...

James McKenzie · Post by **James McKenzie** » Sun Aug 22, 2010 11:10 pm

Bebado wrote:

Hi all.

So i compiled the recently released wine 1.3.1, and i'm in a predicament related to the sound configuration, that never happened in previous wine versions. Whenever i try to configure sound, using winecfg, wine crashes, also running applications just end with the same exact crash.

Should i fill a bug report?

Have you disabled PulseAudio? If you can please try.

James McKenzie

Bebado · Post by **Bebado** » Mon Aug 23, 2010 4:12 am

Hi James.

Yes, i disabled pulseaudio, and got the same crash. Might i add it only happens with alsa, if i select any other sound driver (or, obviously, disable sound) it doesn't crash. Though i can't do it within winecfg, because in any scenario, it crashes when i select the audio tab.

So i guess it's something related with alsa. And let me reiterate, it does NOT happen in wine 1.3.0 or in the stable 1.2.

Post by **dimesio** » Mon Aug 23, 2010 6:38 am

Bebado wrote: So i guess it's something related with alsa. And let me reiterate, it does NOT happen in wine 1.3.0 or in the stable 1.2.

Check to see if a bug has already been filed, and if not, please run a regression test and file one.

Bebado · Post by **Bebado** » Mon Aug 23, 2010 7:59 pm

A very poor search made me lost an entire afternoon conducting regression tests when the error and the "bad" commit were already identified... my fault entirely

. Well, at least i learned how to make a regression test.

For those who are affected by this particular bug, you can follow further developments in http://bugs.winehq.org/show_bug.cgi?id=23902 .

The patch published there by the original author of the 'bad' commit apparently solved my crashes.

James McKenzie · Post by **James McKenzie** » Mon Aug 23, 2010 9:56 pm

Bebado wrote:

A very poor search made me lost an entire afternoon conducting regression tests when the error and the "bad" commit were already identified... my fault entirely [Evil or Very Mad]. Well, at least i learned how to make a regression test.

For those who are affected by this particular bug, you can follow further developments in http://bugs.winehq.org/show_bug.cgi?id=23902 .

The patch published there by the original author of the 'bad' commit apparently solved my crashes.

If you can, please go in and advise by adding a comment and VOTING for
the bug. Read through all of the comments and then add your system
configuration and the fact that the patch 'fixes' you.

It looks like there is more work to be done.

James McKenzie