BTW, how 'new' is your driver? If you don't compile drivers by hand and load modules to the kernel, chances are you are using at least 6 month old version of Intel driver. Side quote: As Dan pointed out, no project would take responsibility of "open-sourced" intel driver, so don't think seriously that your problem would be sorted out in anything less than 6 months. Cheers, Anurag On Wed, Mar 5, 2008 at 8:48 PM, WJM <wineforum-user@xxxxxxxxxx> wrote: > > > > > This is not a wine bug; wine's merely a way to expose it. > > It is a video driver bug. > > Please go talk to Suse about it. > > Let us know what happens. > > - Dan > > I did not intend to say that it was necessarily a WINE bug and am trying > to find out if others here have similair issues to share ideas and hopefully > get it fixed. > I have found similair issues mentioned in other forums (non SUSE) so it's > a hard one to put the finger on what exactly is causing this. > > So far WINE is the only thing that 'exposes' the problem so thats why I'm > trying to get some help and ideas here and also hope to help other identify > this. > > I will drop a bug report at OpenSUSE and let you know how that goes... > > Cheers & Regards, > > Wj > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20080305/2bcffaaa/attachment.htm
