Ares

No Internal Error window using wine

Bug #896079 reported by pd
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
New
Low
Unassigned

Bug Description

I am using wine (1.2.2) to run Yuri's Revenge with Ares in Linux inside a virtualized desktop, which allows me to play "windowed" while the game thinks it is fullscreen.

When an Internal Error occurs, I cannot see the message box. Hence, I cannot click "OK" and no except.txt file will be generated.

I am aware that this is a problem with wine, not Ares. Still, I would consider it rather easy to provide a little workaround.

I would suggest some kind of command line argument (e.g. "-wine", or "-skiperrormsg") that will skip showing the Internal Error message and write the except.txt right away.

##### STEPS TO REPRODUCE #####
1. Run YR with Ares using wine 1.2.2 in a virtual desktop window.
2. Cause an Internal Error, or wait for one to occur...

Revision history for this message
DCoder DCoder (dcoder1337) wrote :

The same happens on some versions of Windows - testers complained about it and we never found the reason.

Can't you still hit Enter to dismiss the msgbox?

Revision history for this message
pd (pdmail) wrote :

I have tried that, but that isn't possible.

Either wine doesn't know the window even exists (ALT+TABbing to it doesn't work, but I'm not sure whether those virtual wine desktops even support that), or it simply fails gaining focus.

Revision history for this message
Renegade (renegade) wrote :

As suggested in the connected thread at the forums just now, maybe someone should test with wine 1.3 (the current development version) before we screw around with Ares for this.

It's entirely possible this was fixed a long time ago - we won't know without a test.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.