https://bugs.winehq.org/show_bug.cgi?id=43566
Bug ID: 43566 Summary: Risen 2 does failes to start Product: Wine-staging Version: 2.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: vindrg@gmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
Created attachment 58975 --> https://bugs.winehq.org/attachment.cgi?id=58975 Risen startup log
I've installed latest wine-staging 2.14 on Kubuntu 16.04, and now I cannot start Risen 2 (Steam version). It just freezes. I see "Banner" title bar on bottom on virtual Wine desktop, mouse cursor disappears, but game does not show up. It does start with wine-devel fine though.
I have attached console output when launching like this: wine ~/.wine/drive_c/Program\ Files\ (x86)/Steam/steamapps/common/Risen\ 2/system/Risen2.exe 2>&1 | tee /tmp/risen_wine.log
Same result with CSMT or virtual desktop enabled or not.
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #1 from Vincas vindrg@gmail.com --- Created attachment 58976 --> https://bugs.winehq.org/attachment.cgi?id=58976 Rise strace output
https://bugs.winehq.org/show_bug.cgi?id=43566
Vincas vindrg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu Hardware|x86 |x86-64
https://bugs.winehq.org/show_bug.cgi?id=43566
Vincas vindrg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Risen 2 does failes to |Risen 2 fails to start |start |
https://bugs.winehq.org/show_bug.cgi?id=43566
Vincas vindrg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vindrg@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=43566
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #2 from Fabian Maurer dark.shadow4@web.de ---
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
You should resolve that.
So, it works fine with wine2.14 but freezes with wine2.14-staging? If so, could you make a regression test to find the staging patch that introduces the issue?
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #3 from Vincas vindrg@gmail.com --- (In reply to Fabian Maurer from comment #2)
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
You should resolve that.
I have installed winbind package, it disappeared. But do I really need that..?
So, it works fine with wine2.14 but freezes with wine2.14-staging?
Yes. Will attach diff of staging vs devel output.
If so, could you make a regression test to find the staging patch that introduces the issue?
Uhm, any hints on how to start..? It involves compiling wine I guess..? Are there .dpkg snapshots of some daily builds maybe?
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #4 from Vincas vindrg@gmail.com --- Created attachment 58979 --> https://bugs.winehq.org/attachment.cgi?id=58979 diff staging.log (not working) against devel.log (working)
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #5 from Fabian Maurer dark.shadow4@web.de ---
I have installed winbind package, it disappeared. But do I really need that..?
I'd recommend it since it can cause issues when it's missing.
Yes. Will attach diff of staging vs devel output.
Ah, so indeed a regression.
Uhm, any hints on how to start..? It involves compiling wine I guess..? Are there .dpkg snapshots of some daily builds maybe?
Yes, you need to compile wine for that. There won't any way around that, since you need to to able to test against any commit.
Is http://store.steampowered.com/app/40390/Risen_2_Dark_Waters/ the right game? There is a demo, and if the demo has the same issue I could do the regression test. I'll look into it later.
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #6 from Vincas vindrg@gmail.com --- (In reply to Fabian Maurer from comment #5)
Is http://store.steampowered.com/app/40390/Risen_2_Dark_Waters/ the right game?
Yeas it's that game.
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- Does the demo work for you, or does it have the same issue? Because on my system in a fresh wineprefix and wine-staging2.14 it works fine.
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #8 from Vincas vindrg@gmail.com --- I had to create new account because I own full game version. Also, created new wine prefix, but game demo does not start as in full version.
It does start when launching with /opt/wine-devel/bin/wine though.
By the way, as of little off-topic, did Risen Demo had decent frame rate on your machine? Because on my GeForce 860M i7-4710HQ system I get only few frame per 1second will all Off/Low settings...
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #9 from Fabian Maurer dark.shadow4@web.de --- So the demo doesn't start for you either? Strange, since it works for me.
I have an R9 285 and get about 25~30 FPS with lowest settings.
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #10 from Vincas vindrg@gmail.com --- Maybe it's something nvidia-related?
Anyway, I could try to build wine myself. I see there is pretty good wiki page for that: https://wiki.winehq.org/Regression_Testing . But how do I distinguish dev vs staging? I don't see it mentioned there.
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #11 from Fabian Maurer dark.shadow4@web.de --- Could be a driver issue, or something else that's different on your system.
You can make a regression test for staging by just getting wine-git and then applying the staging patches on top of it. I use:
cd wine-git ../wine-staging/patches/patchinstall.sh --backend=git-am --force-autoconf --all
https://bugs.winehq.org/show_bug.cgi?id=43566
--- Comment #12 from Vincas vindrg@gmail.com --- I have tried easier path, as I discovered that there are older builds available in repository:
wine-staging: Installed: 2.12.0~xenial Candidate: 2.15.0~xenial Version table: 2.15.0~xenial 500 500 https://dl.winehq.org/wine-builds/ubuntu xenial/main amd64 Packages 2.14.0~xenial 500 500 https://dl.winehq.org/wine-builds/ubuntu xenial/main amd64 Packages 2.13.0~xenial 500 500 https://dl.winehq.org/wine-builds/ubuntu xenial/main amd64 Packages *** 2.12.0~xenial 500 500 https://dl.winehq.org/wine-builds/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ...
Problem is, that with version 2.11 and downwards I cannot even get Steam starded, and 2.12 already has same problems starting Risen 2 as I discovered on 2.14. So.. I have no way to find regression..?
https://bugs.winehq.org/show_bug.cgi?id=43566
Vincas vindrg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME
--- Comment #13 from Vincas vindrg@gmail.com --- I have migrated to Debian Testing, and it woks with 2.17 staging!
Maybe there was something broken on Ubuntu, maybe something with NVidia drivers or like that....
https://bugs.winehq.org/show_bug.cgi?id=43566
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org