Forums

Well, I just changed it to 1.7.44 and no staging. I don't know why it says staging. But previously I followed this and it said staging: https://appdb.winehq.org/objectManager.php?sClass=version&iId=32123

What's this? What does it mean?

http://www.pasteall.org/58862

The remove Steam overlay didn't help. Here's the new changelog.

 

• [0514/203417:WARNING:raw_channel.cc(218)] Shutting down RawChannel with write buffer nonempty
• [0514/204220:WARNING:raw_channel_win.cc(471)] WriteFile: Pipe not connected. (0xE9)
• [0514/204220:WARNING:channel.cc(320)] RawChannel write error
• wine: Unhandled exception 0x80000003 in thread 42 at address 0x1151a8eb (thread 0042), starting debugger...
• IPC client is in my process, could/should be using an in-process pipe.IPC client is in my process, could/should be using an in-process pipe.Process of pid=002d has terminated

 I wonder if there's not some new Steam compatibility issue going on...

 

Quote from petch

Ooooo. Yeah. I missed that. I hope that is not the case. 

What is this? What does it show?

Lol. If you read what Petch said:

 

 I wonder if there's not some new Steam compatibility issue going on...

Sometimes when Steam updates it's software it breaks Wine. This has happened a few times in the past. Though, I am able to install Steam through POL with Wine 1.7.44, when I tried to quit it crashed. Looks like Steam might be broken for Wine right now. 

So it even could be Steam fault? It shows crashes for me, but otherwise it is running very well so far - I haven't found anything that doesn't work(expect the stuff I was playing around with - I installed Source SDK, but it doesn't work).

Yeah. I mean, it worked, but when I quit it threw an exception just like the one above. Not really sure. 

Maybe we should ask Steam? 

Steam (actually, Valve) does not support Wine, and will not troubleshoot it. This needs to be dealt with through WineHQ. You will need to file a bug report here:

https://bugs.winehq.org/

It is something that is out of our control, unfortunately.

Well, usually when I post something releated to PlayOnLinux in their page, they reject me(Wine) and tells that I must test without PlayOnLinux first. But PlayOnLinux uses Wine and actually does the same, but in GUI, AFAIK. I am not sure if they'll not reject this report!

During the gameplay I all the time get this:

fixme:d3d:wined3d_occlusion_query_ops_get_data 0x60a0a4c8 Wrong thread, returning 1.

What does it mean?

I clicked repait virtual drive and tested again - don't see any changes. Here is the debugger output:

http://pastebin.com/hXVTv2Ei

Edité par adriansnetlis

Yeah. With WineHQ, they require that you test it directly through Wine, not through POL, otherwise they will close your report, unfortunately. 

Do you know what that error means that I posted above? Could it be problem releated? Actually, is it meant about CPU threads or something else?

Lines with fixme can usually be ignored. err lines are ones that normally indicate what is wrong. Besides seeing a bunch of d3d errors (which is usually related to graphics drivers),  I still see that IPC error from Steam, and I still think that it is something that WineHQ will have to patch up. I will do some research and see what I can find out. 

Can you try to switch the Wine version to 1.7.44-staging and see if that works? I just want to check something.

What's the difference between standard version and staging version?

wine-staging is filled with patches that have not made it into regular Wine yet. You can find out more here:

http://www.wine-staging.com/

But you can install 1.7.44-staging from Tools -> Manage Wine Versions

Oh... I will test it right now...

Didn't fix. Here is .log:

http://www.pasteall.org/58885