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@winehq.org Reporter: jonathon.n.baker@gmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@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
https://bugs.winehq.org/show_bug.cgi?id=42233
jonathon.n.baker@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Mint Keywords| |regression
https://bugs.winehq.org/show_bug.cgi?id=42233
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz@gmail.com
--- Comment #1 from fjfrackiewicz@gmail.com --- (In reply to jonathon.n.baker from comment #0)
Created attachment 56878 [details] 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.
Hi,
Can you run a regression test? https://wiki.winehq.org/Regression_Testing
https://bugs.winehq.org/show_bug.cgi?id=42233
--- Comment #2 from Michael Müller michael@fds-team.de --- The regression test instructions won't help here as they do not contain information about Wine Staging.
I tried to reproduce the issue using the CD version and was unable to do so (with and without overrides). Could you try to install the game in a fresh wine prefix to make sure that no further steps are required to trigger the bug (installed plugins etc.)? Just prepend WINEPREFIX="$HOME/.wine-regression" before each Wine invocation and install steam + oblivion.
https://bugs.winehq.org/show_bug.cgi?id=42233
--- Comment #3 from jonathon.n.baker@gmail.com --- I have installed steam and oblivion in a fresh wine prefix. I initially tried running it with just what steam installed with oblivion, and the same crash as previously reported happened before loading the main menu. I then tried disabling gstreamer, adding quartz, and adding directx9 v43 via winetricks in that order, with tests in between, and the crash was reproducible in every situation. The only plugins installed to oblivion are the official DLC files. Command invocation was "WINEPREFIX="$HOME/.wine-regression" wine64 'C:\Program Files (x86)\Steam\Steam.exe'"
https://bugs.winehq.org/show_bug.cgi?id=42233
--- Comment #4 from jonathon.n.baker@gmail.com --- the current devel version is also able to run the game in this prefix with no problem
https://bugs.winehq.org/show_bug.cgi?id=42233
--- Comment #5 from jonathon.n.baker@gmail.com --- Oh, I just noticed that I didn't mention this. The version of devel installed through the package manager in my distribution does not exhibit this crash, but the version from winehq-staging does.
https://bugs.winehq.org/show_bug.cgi?id=42233
--- Comment #6 from Sebastian Lackner sebastian@fds-team.de --- I also tried to reproduce this issue, but everything works fine here. It would be useful to know some more details about your setup to narrow down the root cause:
* After creating the fresh prefix, did you change any settings? For example, switch to a different Windows version or enable virtual desktop mode? And how exactly did you install Steam into the fresh prefix? If you used winetricks or some other scripts it is important to know because they sometimes also apply other tweaks. It is unlikely, but they could make a difference for this bug.
* Which DLCs did you have installed during your tests? If there is any way to install DLCs manually or to disable them, could you please test if the regression is really related to Oblivion, or to one of the addons?
* Wine Staging 2.0-rc5 contained a patch which could behave different depending on the window manager. Which one do you use? If you have multiple installed, does it make a difference?
If you have any other idea what might be unusual about your Wine setup, such information might also help. Thanks!
https://bugs.winehq.org/show_bug.cgi?id=42233
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #7 from winetest@luukku.com ---
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.
This is soemthing that wine doesn't usually support.
Also the list of native overrides is long like a hunger year.
You need to start from fresh wineprefix.
https://bugs.winehq.org/show_bug.cgi?id=42233
--- Comment #8 from jonathon.n.baker@gmail.com --- Sebastian, I did not change any settings aside from what I listed. It is presenting a windows xp environment without a virtual desktop, as per default. Once I created the new prefix I downloaded the steam.exe runtime from valve's website and called WINEPREFIX='path-to-new-prefix' wine64 steam.exe, which installed steam, then I signed in and installed oblivion there.
I have the standard "Game of the Year DLC" pack installed, which comes standard with oblivion purchase on steam and includes all of the DLC that was available. I tried uninstalling it and launching without it but the crash still occurred in the same spot, so I do not believe that whatever this bug is is related to the DLC.
My DE is cinnamon, and I believe it uses muffin for the window manager, which is a fork of mutter. I do not have multiple window managers installed to test with.
I do not believe there is anything non-standard about my setup.....I listed the steps I took to install wine-staging and the steps I took when setting up my main prefix and the testing prefix in the initial bug report and this comment chain.
Please let me know what additional tests or information you want.
https://bugs.winehq.org/show_bug.cgi?id=42233
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #9 from joaopa jeremielapuree@yahoo.fr --- Still a bug with wine-5.10?