[Bug 50765] New: the hunter call of the wild crash on start
https://bugs.winehq.org/show_bug.cgi?id=50765 Bug ID: 50765 Summary: the hunter call of the wild crash on start Product: Wine-staging Version: 6.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jg.staffel(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 69556 --> https://bugs.winehq.org/attachment.cgi?id=69556 The log of the crash, created by the game. Since wine-staging 6.2 and 6.3 "The hunter call of the wild crash" crashes during startup. No any errors in terminal with WINEDEBUG=warn+dll+error, including no dxvk errors. This bug tested also with a clean Wine directory with the same result (winetricks corefonts msxml6 d3dx11_43 winhttp wininet xact vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2017 tahoma dxvk). I am attaching the log of the crash, created by the game. Wine-staging 5.22 works perfectly. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 alpir <jg.staffel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jg.staffel(a)gmail.com -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 alpir <jg.staffel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|the hunter call of the wild |theHunter call of the wild |crash on start |crash on start -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 alpir <jg.staffel(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Gentoo -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Does this also happen with upstream wine (non-staging)? Also, please test in a clean (new) wineprefix, I doubt it's necessary to install so many native components. Always attach default (no WINEDEBUG set) wine output as well, see: <https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal_output.29.3F> -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 --- Comment #2 from alpir <jg.staffel(a)gmail.com> --- I created a new prefix. I only installed corefonts d3dx11_43 tahoma vcrun2015. I installed app-emulation/wine-vanilla-6.3-r1:6.3::gentoo USE="X alsa faudio fontconfig gecko jpeg lcms mono mp3 nls openal opengl perl png pulseaudio realtime run-exes sdl ssl threads truetype udev udisks unwind usb vkd3d vulkan xcomposite xml -capi -cups -custom-cflags -dos -gphoto2 -gsm -gssapi -gstreamer -kerberos -ldap -mingw -netapi -odbc -opencl -osmesa -oss -pcap -prelink -samba -scanner (-selinux) -test -v4l -xinerama" ABI_X86="32 64 (-x32)" The same result with wine-staging-6.3 and new profile, log attached. With wine-vanilla-6.3 the game hang on first screen, log attached. This logs received with WINEDEBUG=warn+dll+error. Also i attached log with wine-staging-6.3, old profile and WINEDEBUG=info. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 --- Comment #3 from alpir <jg.staffel(a)gmail.com> --- Created attachment 69573 --> https://bugs.winehq.org/attachment.cgi?id=69573 wine-staging-6.3 and new profile log -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 --- Comment #4 from alpir <jg.staffel(a)gmail.com> --- Created attachment 69574 --> https://bugs.winehq.org/attachment.cgi?id=69574 wine-vanilla-6.3 and new profile log -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 --- Comment #5 from alpir <jg.staffel(a)gmail.com> --- Created attachment 69575 --> https://bugs.winehq.org/attachment.cgi?id=69575 wine-staging-6.3 and old profile, WINEDEBUG=info -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #6 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with the current wine (wine-9.0-rc5) And lease test in a fresh wine prefix without any dll overrides and vanilla wine (not staging) -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 alpir <tsebrenko(a)ya.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED Resolution|--- |WORKSFORME --- Comment #7 from alpir <tsebrenko(a)ya.ru> --- With wine-staging-8 - there is no problem at all. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 --- Comment #8 from joaopa <jeremielapuree(a)yahoo.fr> --- And with vanilla wine? -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be Status|CLOSED |RESOLVED --- Comment #9 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Bug reporters must not close bugs themselves. They should mark them 'resolved' instead. Administrators will close bugs when appropriate. Regards. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #10 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #9)
Bug reporters must not close bugs themselves. They should mark them 'resolved' instead. Administrators will close bugs when appropriate.
That's only really a problem for FIXED status; I don't think we care otherwise, especially not enough to unclose bugs. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 --- Comment #11 from Austin English <austinenglish(a)gmail.com> --- (In reply to Zeb Figura from comment #10)
(In reply to Olivier F. R. Dierick from comment #9)
Bug reporters must not close bugs themselves. They should mark them 'resolved' instead. Administrators will close bugs when appropriate.
That's only really a problem for FIXED status; I don't think we care otherwise, especially not enough to unclose bugs.
Also 'NOTOURBUG' (which should be closed when the bug is fixed in the upstream/downstream project). For the rest (INVALID/WONTFIX/DUPLICATE/ABANDONED), it doesn't matter. They can be closed at the same time as resolution, or later by someone else. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=50765 alpir <tsebrenko(a)ya.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|tsebrenko(a)ya.ru | -- 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.
participants (1)
-
WineHQ Bugzilla