Known issues area on main wiki page

Robert Reif reif at earthlink.net
Tue Mar 21 06:43:46 CST 2006


Tom Spear (Dustin Booker, Dustin Navea) wrote:

> Jesse Allen wrote:
>
>> On 3/20/06, Mike McCormack <mike at codeweavers.com> wrote:
>>  
>>
>>> Dimi Paun wrote:
>>>    
>>>
>>>> On Mon, 2006-03-20 at 22:28 -0600, Tom Spear (Dustin Booker, Dustin
>>>> Navea) wrote:
>>>>
>>>>      
>>>>
>>>>> clicking on the audio tab to check out bug 4051 first? Please!
>>>>>         
>>>>
>>>> How about we fix the problem instead? :)
>>>>       
>>>
>>> The best way to fix it is probably to rearrange the code so that the
>>> Audio tab shows, then there's a [Detect] button that the user can click
>>> to run the autodetect code that might crash.  At least then the user 
>>> can
>>> set their Wine Audio settings manually.
>>>
>>> Mike
>>>
>>>
>>>     
>>
>>
>>
>> This is not enough, as when I click the audio tab, it will lock up in
>> the kernel.  I already identified where it happens and patch the
>> kernel myself.  I told the ALSA devs, but they haven't looked at why
>> certain register usage causes a lockup.  So it remains in the stable
>> kernel who knows who else hits it.
>>
>> Jesse
>>
>>   
>
> Which is why I agree with the ideas from Mike and Dimi AND Segin..  
> Why not put an autodetect button, have the exception handler catch the 
> crash if arts decides to die, and then still have a popup dialog for 
> when arts is manually selected that tells users it is buggy and not 
> recommended to use?  That doesn't fix your specific problem Jesse, I 
> know, but at least it keeps winecfg open when you click on the audio tab.
>
> Tom
>
>
>
The reason I added the probe of all drivers in winecfg was so that the 
broken and marginal drivers would get used and hopefully fixed.  Moving 
the problem will just create different bugs: [BUG xxx] winecfg crashes 
when autodetect button pressed or [BUG yyy] winecfg crashes when driver 
xyz selected.




More information about the wine-devel mailing list