[Bug 47133] New: Kyodai Mahjong crashes after update to wine 4.17
https://bugs.winehq.org/show_bug.cgi?id=47133 Bug ID: 47133 Summary: Kyodai Mahjong crashes after update to wine 4.17 Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ZeroBeat(a)gmx.de Distribution: --- Created attachment 64354 --> https://bugs.winehq.org/attachment.cgi?id=64354 backtrace crash report Update to 4.17 (https://www.archlinux.org/packages/multilib/x86_64/wine/) causes Kyodai Mahjongg (rated as gold: https://appdb.winehq.org/objectManager.php?sClass=version&iId=10422) to crash. OS: Arch Linux (attached backtrace) 4.19.38-1-lts nvidia-340xx-lts 340.107-20 BTW: crashed also on 5.0.12-arch1-1-ARCH nvidia 418.56-13 -- 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=47133 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-d3d Summary|Kyodai Mahjong crashes |Kyodai Mahjong crashes |after update to wine 4.17 |after update to wine 4.7 -- 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=47133 pattietreutel <katyaberezyaka(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka(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=47133 --- Comment #1 from Michael <ZeroBeat(a)gmx.de> --- BTW: The issue is driver independent. The same happens, running xf86-video-nouveau. -- 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=47133 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #2 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, I guess you mean upgrade to wine-4.7 ( instead of wine-4.17)
From what version did you upgrade?
Also: looks like the game is free, could you provide exact downloadlink? Thanks and 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=47133 --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Forgot to mention, i downloaded from https://nl.softonic.com/download/kyodai-mahjongg/windows/post-download That one starts and works fine here. Your crash looks like a driver bug but I`m not expert on this; maybe running with LIBGL_ALWAYS_SOFTWARE=1 changes anything? -- 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=47133 --- Comment #4 from Michael <ZeroBeat(a)gmx.de> --- @ Louis, 4.17 is a typo (didn't find a way to edit this). Version is wine 4.7 Your idea (checking update from ... to ...) was really good. I was on vacation and didn't noticed that this update is from 4.5 to 4.7 (skipped 4.6). Now, I went back in Arch history (that can be done easily by Arch packaging system) and noticed that 4.6 caused the issue : 4.5 is running fine (nvidia and nouveau) 4.6 crashed, running both drivers. 4.7 crashed, running both drivers. Update from https://archive.archlinux.org/packages/w/wine/wine-4.5-1-x86_64.pkg.tar.xz to https://archive.archlinux.org/packages/w/wine/wine-4.7-1-x86_64.pkg.tar.xz Games came from here in different versions - none of them is running any longer: http://cynagames.com/kyodown.html LIBGL_ALWAYS_SOFTWARE=1 doesn't fix it. because the issue is not driver (or mesa) related. Tried that on different machines, running different configurations. Workaround: Downgrade to 4.5 and tell pacman to ignore updates (IgnorePkg) until bug is fixed. -- 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=47133 Michael <ZeroBeat(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|4.7 |4.6 -- 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=47133 Michael <ZeroBeat(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|4.6 |4.7 -- 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=47133 Paul Gofman <gofmanp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp(a)gmail.com --- Comment #5 from Paul Gofman <gofmanp(a)gmail.com> --- I used a 'small download' from the game website and could not reproduce the problem, the game is starting just fine. Could you please give the exact reference for the version which is crashing and the output of 'sha1sum <file>', where <file> is the installer? Could you please also attach WINEDEBUG=+d3d8,+d3d,+d3d_shader debug output? -- 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=47133 --- Comment #6 from Michael <ZeroBeat(a)gmx.de> --- @ Paul, this is the first part of your request: https://download.cnet.com/Kyodai-Mahjongg-2006/3000-2111_4-10488892.html 2f877cd6f01cfd25a8fc5e48715602bea03f05f3 kyo2006.exe Now I'm trying to prevent the crash and get the 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=47133 --- Comment #7 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64394 --> https://bugs.winehq.org/attachment.cgi?id=64394 log from WINEDEBUG=+d3d8,+d3d,+d3d_shader -- 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=47133 --- Comment #8 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64395 --> https://bugs.winehq.org/attachment.cgi?id=64395 Screenshot -- 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=47133 --- Comment #9 from Michael <ZeroBeat(a)gmx.de> --- I can do the same on v4.6 or v4.5 if you require additional debug files. -- 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=47133 --- Comment #10 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Michael from comment #7)
Created attachment 64394 [details] log from WINEDEBUG=+d3d8,+d3d,+d3d_shader
I downloaded the referenced installer, sha1sum is the same, but I still can't reproduce the crash and don't see any rendering glitches. I don't see the originally reported crash in the provided log. Does it mean the crash does not happen anymore, or it does not happen with the debug flags enabled, or something else has changed? What did you mean by "I'm trying to prevent the crash and get the log."? Are we debugging the crash or something else? Can you maybe retest with the clean wine prefix with latest Wine, and if the crash is still there, attach the WINEDEBUG=+d3d8,+d3d,+d3d_shader,+seh log from the crashing run. If you see crash dialog, press 'Close', not 'Details', to get the backtrace right in the log output. -- 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=47133 --- Comment #11 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64400 --> https://bugs.winehq.org/attachment.cgi?id=64400 Arch wine pkgbuild Attached the pkgbuild (how wine is compiled on Arch Linux). So we can find out how Arch version differs from your version. -- 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=47133 --- Comment #12 from Michael <ZeroBeat(a)gmx.de> --- I thought that you asked this. The first report (initial report) is from: OS: Arch Linux (attached backtrace) 4.19.38-1-lts nvidia-340xx-lts 340.107-20 The second trace (today) is from: 5.0.13-arch1-1-ARCH nvidia 418.74-1 Unfortunately Arch did an update in the meantime. Now the lts system is on: linux-lts 4.19.41-1 nvidia-340xx-lts 340.107-80 while the other system is on 5.0.13-arch1-1-ARCH nvidia 418.74-1 On both system kmj crashed no longer, but shows the attached screenshot. Also, I think we have only a short time gap (unfortunately), because Arch will provide wine 4.8, kernel 5.1 and latest drivers, soon. Maybe it's a good idea to wait for wine 4.8 and kernel 5.1 before continuing to hunt for the bug. -- 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=47133 --- Comment #13 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64401 --> https://bugs.winehq.org/attachment.cgi?id=64401 WINEDEBUG=+d3d8,+d3d,+d3d_shader,+seh Nevertheless, here are the requested files: log file WINEDEBUG=+d3d8,+d3d,+d3d_shader,+seh wine v 4.7 (fresh install) 5.0.13-arch1-1-ARCH nvidia 418.74-1 Now I'm going back to 4.5 and attach logfile. -- 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=47133 --- Comment #14 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64402 --> https://bugs.winehq.org/attachment.cgi?id=64402 Screenshot wine 4.5 working fine, running v 4.5 -- 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=47133 --- Comment #15 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64403 --> https://bugs.winehq.org/attachment.cgi?id=64403 v 4.5 - WINEDEBUG=+d3d8,+d3d,+d3d_shader,+seh Now, we have a reference (v4.5, running on the same machine, fresh install). -- 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=47133 --- Comment #16 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Michael from comment #12)
On both system kmj crashed no longer, but shows the attached screenshot.
I am sorry, I am getting lost in it. So the original crash you reported is no longer reproducible for you after some updates on the host system, but you have a new problem with some strange display in a widnow (details unknown, whether it hangs, display that at once or after something else etc.). I am not entirely sure and there is still a room for Wine bug here of course, but I've got an impression that it could be something about your host(s) setup. -- 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=47133 --- Comment #17 from Michael <ZeroBeat(a)gmx.de> --- It is possible, that the original issue isn't reproduceable any longer, because of several updates in the meantime. Also it's possible that the issue is related to Arch linux. But I don't think so, because 4.5 is running fine on 4 different systems [different kernel versions, different CPUs (AMD, INTEL), different drivers (nouveau and nvidia)]. I'll try to get the corresponding WINEDUBUG log for the initial crash. -- 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=47133 --- Comment #18 from Michael <ZeroBeat(a)gmx.de> --- Ok, moved back to the beginning (first occurrence of the error). OS: Arch Linux (attached backtrace) 4.19.38-1-lts nvidia-340xx-lts 340.107-20 update from 4.5 to 4.7 Attached backtrace and WINEDEBUG log. Now you should be able to reproduce it. -- 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=47133 --- Comment #19 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64404 --> https://bugs.winehq.org/attachment.cgi?id=64404 4.5 backtrace -- 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=47133 --- Comment #20 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64405 --> https://bugs.winehq.org/attachment.cgi?id=64405 4.7 WINEDEBUG=+d3d8,+d3d,+d3d_shader,+seh -- 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=47133 Michael <ZeroBeat(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #64404|4.5 backtrace |4.7 backtrace description| | -- 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=47133 --- Comment #21 from Michael <ZeroBeat(a)gmx.de> --- It looks like the crash doesn't appear after kernel/driver update (nouveau and/or nvidia). But the game doesn't start any longer. If I have some time, I'll check the diff from 4.5 to 4.6. -- 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=47133 --- Comment #22 from Michael <ZeroBeat(a)gmx.de> --- BTW: The the recommendation frome the debug file: 0046:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. doesn't work. Nouveau driver shows the same picture as the attached screenshots (garbage in left upper corner). -- 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=47133 --- Comment #23 from Michael <ZeroBeat(a)gmx.de> --- Also I noticed some important changes between 4.5 and 4.6: https://source.winehq.org/git/wine.git/commit/7d351e1168b4f41ca43e67f3b038ab... So I'm not sure about a host relationship. -- 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=47133 --- Comment #24 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Michael from comment #20)
Created attachment 64405 [details] 4.7 WINEDEBUG=+d3d8,+d3d,+d3d_shader,+seh
As per this log, your wine prefix / host Wine setup is broken. I realize that you may have see it working with 4.5 and stop working with 4.6, but it may well be related to how you run that, and even if there is some inconsistency introduced in Wine update, I don't see the feasible way to guess what can it be under these conditions. You should test on clean Wine prefixes only, without those registry (or any other) tweaks on. If you are turning some tweak on because the app being tested doesn't run otherwise, you should clearly state that when describing your problem. You probably should fix the gnutls and gstreamer issues first (maybe GL drivers too, I am not sure). Helping with this setup is offtopic here, neither I have enough information about your system to do that. -------- err:winediag:wined3d_adapter_gl_init You are using the backbuffer for offscreen rendering. This is unsupported, and will be removed in a future -------- ------------ 0042:err:winediag:wined3d_dll_init The GLSL shader backend has been disabled. You get to keep all the pieces if it breaks. 0042:trace:d3d:wined3d_dll_init Use of GL Shading Language disabled. ... 0042:trace:d3d:wined3d_caps_gl_ctx_create getting context... 0042:warn:d3d:context_create_wgl_attribs Failed to create a WGL context with wglCreateContextAttribsARB, last error 0. 0042:warn:d3d:wined3d_adapter_gl_init Couldn't create an OpenGL 4.4 context, trying fallback to a lower version. ------------ -------- 0029:err:module:load_builtin_dll failed to load .so lib for builtin L"l3codeca.acm": libmpg123.so.0: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden 0029:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption 0029:err:winediag:gnutls_initialize failed to load libgnutls, no support for pfx import/export 0029:err:module:load_builtin_dll failed to load .so lib for builtin L"mp3dmod.dll": libmpg123.so.0: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden 002e:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. 002e:err:winediag:gnutls_initialize failed to load libgnutls, no support for encryption 002e:trace:seh:raise_exception code=c0000005 flags=0 addr=(nil) ip=00000000 tid=002e 002e:trace:seh:raise_exception info[0]=00000008 002e:trace:seh:raise_exception info[1]=00000000 002e:trace:seh:raise_exception eax=00000000 ebx=f784e000 ecx=0032f580 edx=00000000 esi=f784e000 edi=f7830000 002e:trace:seh:raise_exception ebp=0032f558 esp=0032f54c cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010206 002e:trace:seh:call_stack_handlers calling handler at 0x7bcbd5d0 code=c0000005 flags=0 002e:trace:seh:__regs_RtlUnwind code=c0000005 flags=2 002e:trace:seh:__regs_RtlUnwind eax=00000000 ebx=7bcbd420 ecx=0032f4f4 edx=0032f684 esi=0032f684 edi=7bcbd420 002e:trace:seh:__regs_RtlUnwind ebp=0032f098 esp=0032f078 eip=7bcbd47d cs=0023 ds=002b fs=0063 gs=006b flags=00000202 002e:trace:seh:__regs_RtlUnwind calling handler at 0x7bc96120 code=c0000005 flags=2 002e:trace:seh:__regs_RtlUnwind handler at 0x7bc96120 returned 1 ------------ -- 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=47133 --- Comment #25 from Michael <ZeroBeat(a)gmx.de> --- Thanks for the info. I'll remove the broken prefix and test again. -- 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=47133 --- Comment #26 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 64408 --> https://bugs.winehq.org/attachment.cgi?id=64408 debug log on complete fresh install Here we go again: fresh system, fresh prefix, fresh wine 4.7, fresh driver, fresh installation of kmj, no tweaks. VGA compatible controller: NVIDIA Corporation G86M [GeForce 8600M GS] (rev a1) 5.0.13-arch1-1-ARCH (switrched from lts to latest kernel) nvidia-340xx 340.107-80 Unfortunately, the same crash, running 4.7 -- 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=47133 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #27 from joaopa <jeremielapuree(a)yahoo.fr> --- No one is able to reproduce the bug. No news since almost 2 years. At least, can an administrator close this bug as WORKSFORME? -- 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=47133 --- Comment #28 from Michael <ZeroBeat(a)gmx.de> --- It is a very old came and it looks like nobody play it any longer. It appear on all my systems (Intel and AMD) in combination wit a NVIDA card. $ uname -r 5.10.15-arch1-1 $ pacman -Q | grep nvidia nvidia 460.39-7 nvidia-settings 460.39-1 nvidia-utils 460.39-1 opencl-nvidia 460.39-1 last working wine version for me is $ pacman -Q | wine wine 4.5-1
From time to time I tested a new version of wine, on a fresh install of them game. The screen resolution is still broken and only a part of the game is showing in the left top corner. I set pacman to hold 4.5.1 and that is fine for me, because I only play this game.
You can close this issue. -- 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=47133 --- Comment #29 from joaopa <jeremielapuree(a)yahoo.fr> --- Did you try with the nouveau driver? -- 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=47133 --- Comment #30 from Michael <ZeroBeat(a)gmx.de> --- No, because nouveau is no option for me. All my systems are optimized to perform crypto analyses. Therefore NVIDIA drivers (and NVIDIA GPUs - mostly Ti's), CUDA, OpenCL is mandatory, as well as the latest Linux Kernel and a fast distribution (Arch Linux). $ pacman -Q | grep cuda cuda 11.2.0-3 $ pacman -Q | grep opencl opencl-headers 2:2020.12.18-1 opencl-nvidia 460.39-1 More information here: https://hashcat.net/hashcat/ I'm the developer of hcxtools: https://github.com/ZerBea But anyway, thanks for your effort and your patience. It is just an old game that doesn't work on latest hardware/drivers. -- 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=47133 --- Comment #31 from joaopa <jeremielapuree(a)yahoo.fr> --- Trying Nouveau driver would be useful for debugging purpose. Maybe it is a driver issue and not wine fault. -- 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=47133 --- Comment #32 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 69371 --> https://bugs.winehq.org/attachment.cgi?id=69371 screenshot 6.2.1 broken resolution -- 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=47133 --- Comment #33 from Michael <ZeroBeat(a)gmx.de> --- It looks like the game is too old. -- 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=47133 --- Comment #34 from Michael <ZeroBeat(a)gmx.de> --- fresh installation of wine 6.2.1 removed wine prefix run winecfg -> windows xp environment fresh install of the game -- 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=47133 --- Comment #35 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 69372 --> https://bugs.winehq.org/attachment.cgi?id=69372 debug log 6.2.1 6.2.1 debug log WINEDEBUG=+d3d8,+d3d,+d3d_shader -- 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=47133 --- Comment #36 from Michael <ZeroBeat(a)gmx.de> --- Maybe you have an idea what's going on and I'm simply to stupid to configure wine in a correct way. -- 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=47133 --- Comment #37 from joaopa <jeremielapuree(a)yahoo.fr> --- That's surely a broken driver. But no way to know if you don't want to test Nouveau driver. -- 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=47133 --- Comment #38 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 69379 --> https://bugs.winehq.org/attachment.cgi?id=69379 screensshot wine 4.5 Are you sure? Same system, same kernel, same driver, but now wine 4.5 removed wine prefix fresh install wine 4.5 fresh install game -- 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=47133 --- Comment #39 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 69380 --> https://bugs.winehq.org/attachment.cgi?id=69380 wine 4.5 log Looks like wine 6.x can't handle the driver. -- 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=47133 --- Comment #40 from Michael <ZeroBeat(a)gmx.de> --- Created attachment 69381 --> https://bugs.winehq.org/attachment.cgi?id=69381 wine 4.6 log and exactly that version broke the game same kernel, same driver, fresh install of all (incl. removed wine prefix) -- 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=47133 --- Comment #41 from joaopa <jeremielapuree(a)yahoo.fr> --- Please perform a regression test https://wiki.winehq.org/Regression_Testing -- 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=47133 --- Comment #42 from Michael <ZeroBeat(a)gmx.de> --- Bisecting will take a while.... Are you still sure it's a driver issue? -- 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=47133 --- Comment #43 from Michael <ZeroBeat(a)gmx.de> --- I still assume it is locate near this commit: https://source.winehq.org/git/wine.git/commit/7d351e1168b4f41ca43e67f3b038ab... -- 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=47133 --- Comment #44 from joaopa <jeremielapuree(a)yahoo.fr> --- Your game is a D3D8 one. The pointed commit is about D3D11. It can not be related. Please perform a complete regression test. -- 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=47133 --- Comment #45 from Michael <ZeroBeat(a)gmx.de> --- bisecting is in progress... -- 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=47133 --- Comment #46 from Michael <ZeroBeat(a)gmx.de> --- Bisecting is still in progress. Unfortunately there are several commits to skip: winebuild: /usr/bin/ld failed with status 1 winegcc: ../../tools/winebuild/winebuild failed make[1]: *** [Makefile:628: crypt32.dll.so] Error 2 make[1]: Leaving directory '/home/zerobeat/temp/wine-git/dlls/crypt32' make: *** [Makefile:8553: dlls/crypt32] Error 2 -- 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=47133 --- Comment #47 from Michael <ZeroBeat(a)gmx.de> --- looks like some dependencies changed. Now hunting for them... -- 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=47133 --- Comment #48 from Michael <ZeroBeat(a)gmx.de> --- Very interesting. Sooner or later, your recommendation https://wiki.winehq.org/Regression_Testing will lead to this error winebuild: /usr/bin/ld failed with status 1 winegcc: ../../tools/winebuild/winebuild failed make[1]: *** [Makefile:628: crypt32.dll.so] Error 2 make[1]: Leaving directory '/home/zerobeat/temp/wine-git/dlls/crypt32' make: *** [Makefile:8553: dlls/crypt32] Error 2 If I set git head (checkout -b ...) to the same commit, everything compiles fine and "Wine build complete." If it is ok for you, I leave your recommendation and use git checkout -b instead. It will take a little bit longer, but doesn't lead to that ugly error. -- 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=47133 --- Comment #49 from Michael <ZeroBeat(a)gmx.de> --- We can close this this issue, because I found a solution. The compiler ERROR pointed me into the right direction and I was able to fix the issue which was related to wine prefix. The wine prefix from the compiled git version is working fine in combination with wine 6.2 supplied by Arch Linux package system. Thanks for your effort. -- 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=47133 --- Comment #50 from joaopa <jeremielapuree(a)yahoo.fr> --- You can close your own bug yourself. This one is surely INVALID (bad wineprefix). -- 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=47133 --- Comment #51 from Michael <ZeroBeat(a)gmx.de> --- You're absolutely right. Unfortunately the INVALID wine prefix is created by wine itself. I tested this during walking through the commits and created a "let me say special user defined wine prefix". Additional the resolution highly depend on xorg config as well as detecting the main video device (in case of presence of more than one video devices). Again, thanks for your effort. -- 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=47133 Michael <ZeroBeat(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #52 from Michael <ZeroBeat(a)gmx.de> --- Fixed by modifying the (by wine itself created) wine prefix. -- 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=47133 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID CC| |z.figura12(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=47133 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #53 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Closing INVALID. -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla