Bug 74760

edit: you have to right click and choose save as to see the screenshot for some reason.

Comment on attachment 93722 [details]
screenshot

Changed mimetype to image/jpeg

Can you provide an apitrace?

Created attachment 93763 [details]
winedbg error log

Created attachment 93767 [details]
intel reg dumper output

Created attachment 93768 [details]
intel bios dump

lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

uname -r 3.11.10-7-desktop

uname -m x86_64 (however it's biarch)

pkg-config --modversion libdrm 2.4.46


hope that's enough. If not would someone please tell me how to do an API trace (what debug libraries do I have to install and what commands to use)

Created attachment 93772 [details]
strace extract

We'll need an apitrace: https://github.com/apitrace/apitrace

There is a trace I've made for bug 60963 ( http://pavel.ondracka.cz/Anno1701.trace ), there is also similar bug for r300g (bug 60965), so this may actually be some shared component.

BTW as a workaround, you can switch to ARB backend instead of glsl in Wine, this helps with r300g.

Hi again!

I made an Apitrace:

apitrace trace wine Anno1701.exe > debug.txt
ERROR: ld.so: object '/usr/bin/../lib/apitrace/wrappers/glxtrace.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object '/usr/bin/../lib/apitrace/wrappers/glxtrace.so' from LD_PRELOAD cannot be preloaded: ignored.
apitrace: loaded into /usr/bin/wineserver
apitrace: loaded into /usr/bin/wine64-preloader
apitrace: loaded into /usr/bin/wine64-preloader
apitrace: loaded into /usr/bin/wine64-preloader
apitrace: loaded into /usr/bin/wine64-preloader
apitrace: loaded into /usr/bin/wine64-preloader
apitrace: loaded into /usr/bin/wine64-preloader
fixme:win:EnumDisplayDevicesW ((null),0,0x33b3b8,0x00000000), stub!
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
err:d3d:wined3d_debug_callback 0x89561d8: "GL_INVALID_VALUE in glPointSize".
err:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1565
err:ntdll:RtlpWaitForCriticalSection section 0x1050c70 "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec)
err:d3d:wined3d_debug_callback 0x84dde08: "GL_INVALID_VALUE in glPointSize".
err:d3d:state_pscale >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glPointSize(...); @ state.c / 1565
err:ntdll:RtlpWaitForCriticalSection section 0x1050c70 "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x1050c70 "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec)

confirmed. With the following regedit entry:
UseGLSL=disabled

the strange colors are gone. Thank you for the tip!

(In reply to comment #11)
> Hi again!
> 
> I made an Apitrace:

Is it a working trace that reproduces the issue? Can you post it for us to try?

(In reply to comment #13)
> (In reply to comment #11)
> > Hi again!
> > 
> > I made an Apitrace:
> 
> Is it a working trace that reproduces the issue? Can you post it for us to
> try?

BTW there is already a trace that reproduces the issue posted in Comment 10.

(In reply to comment #14)
> (In reply to comment #13)
> > (In reply to comment #11)
> > > Hi again!
> > > 
> > > I made an Apitrace:
> > 
> > Is it a working trace that reproduces the issue? Can you post it for us to
> > try?
> 
> BTW there is already a trace that reproduces the issue posted in Comment 10.

That trace just enters the menu and then quits. I didn't see any game play or anything resembling the attached screenshots.

(In reply to comment #15)
> (In reply to comment #14)
> > (In reply to comment #13)
> > > (In reply to comment #11)
> > > > Hi again!
> > > > 
> > > > I made an Apitrace:
> > > 
> > > Is it a working trace that reproduces the issue? Can you post it for us to
> > > try?
> > 
> > BTW there is already a trace that reproduces the issue posted in Comment 10.
> 
> That trace just enters the menu and then quits. I didn't see any game play
> or anything resembling the attached screenshots.

Sorry about not being specific. This bug is reproducible even in the menu, just look at the ships behind the window.

Pavel is correct, the strange colors are already in the menu corrupted. Maybe this bug should be marked a duplicate of that bug. Pavel can you please post a screenshot of the menu, if the screenshot were exactly the same as mine, I would mark this bug as a duplicate of bug 60965.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1415.