[Bug 42233] New: wine 2.0 rc 5 apparent regression error in TES 4: oblivion

wine-bugs at winehq.org wine-bugs at winehq.org
Mon Jan 16 21:33:18 CST 2017


https://bugs.winehq.org/show_bug.cgi?id=42233

            Bug ID: 42233
           Summary: wine 2.0 rc 5 apparent regression error in TES 4:
                    oblivion
           Product: Wine-staging
           Version: 2.0-rc5
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: jonathon.n.baker at gmail.com
                CC: erich.e.hoover at wine-staging.com, michael at fds-team.de,
                    sebastian at fds-team.de
      Distribution: ---

Created attachment 56878
  --> https://bugs.winehq.org/attachment.cgi?id=56878
information output by terminal and the wine crash logging tool before and after
program crash

The video game Elder Scrolls 4: Oblivion is installed in a wine prefix which is
shared with a steam installation and several other videogames. 

This prefix is run exclusively with the 64 bit version of wine. 

With the currently set dll overrides and winetricks modifications, and starting 
with a wine version of 2.0 rc2, wine has had no problems running this game. 

However, upon trying to run it after updating to 2.0 rc5, the game launches,
loads the names of the companies and a disclaimer about other engine components
they used, and then crashes prior to reaching the main menu.

I have attached the full output of the wine process when this occurs.

This regression is not present in the current wine-devel version. 

All other video games installed to this prefix still function with no errors.
These games include: Fallout: New Vegas, Bioshock, Mass Effect 1, Mass Effect
2.

I have installed several windows DLLs using winetricks, and several others were
installed by steam during game installation. 

This is a list of installed DLLs (as listed by winetricks and winecfg) and
their override settings (from winecfg), if set:

winegstreamer: disabled
d3dx10: disabled
d3dx11: disabled

d3dx9_43: native
quartz: native

devenum: builtin
dmband: builtin
dmcompos: builtin
dmime: builtin
dmload: builtin
dmscript: builtin
dmstyle: builtin
dmsynth: builtin
dmusic: builtin
dmusic32: builtin
dsound:builtin
dswave: builtin
streamci: builtin

d3dx9:
d3dx9_26
d3dx9_28
d3dx9_31
d3dx9_35
d3dx9_36
d3dx9_39
d3dx9_42
directmusic
directx9
vcrun2008
xact
xact_jun2010
xinput

mwo was toggled a few times with winetricks, but is currently set to default
behavior

all of this was set manually, and no recipes were applied with winetricks

I attempted to record more information about the crash at the direction of a
user on the #winehq irc channel on freenode using the environment variable
setting 'WINEDEBUG=+relay,+tid,+seh' however adding +relay changed program
behavior from crashing to hanging.

At that point, user told me to post bug here

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list