- Wine-bugs - list.winehq.org

[Bug 54670] New: 16-bit applications fail in wow64 mode
by WineHQ Bugzilla 11 Nov '25

11 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=54670 Bug ID: 54670 Summary: 16-bit applications fail in wow64 mode Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, Installer, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian $ wineserver -k ; rm -rf ~/.wine ; WINE=/opt/oldwownew/wine-8.0/bin/wine winetricks -q icodecs ------------------------------------------------------ Executing load_icodecs Executing cabextract -q -d /home/austin/.wine/dosdevices/c:/windows/temp/codinstl/ /home/austin/.cache/winetricks/icodecs/codinstl.exe Executing cd /home/austin/.wine/dosdevices/c:/windows/temp/codinstl/ Executing /opt/oldwownew/wine-8.0/bin/wine setup.exe /s 0284:err:environ:init_peb starting L"C:\\windows\\syswow64\\winevdm.exe" in experimental wow64 mode 0284:fixme:wow:wow64_NtSetLdtEntries 0107 02d0323f 0100f338 0000 00000000 00000000: stub 0284:err:module:LdrInitializeThunk "krnl386.exe16" failed to initialize, aborting 0284:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\syswow64\\winevdm.exe" failed, status c0000005 ------------------------------------------------------ -- 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.

1 19

[Bug 58698] New: Application goes into an infinite loop under new wow64 but works okay under old wow64
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58698 Bug ID: 58698 Summary: Application goes into an infinite loop under new wow64 but works okay under old wow64 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: dkk089(a)gmail.com Distribution: --- Created attachment 79297 --> http://bugs.winehq.org/attachment.cgi?id=79297 WINEDEBUG=+virtual under "new wow64" Application goes into an infinite loop under new wow64 but works okay under old wow64 I have an application that enters an infinite loop under "new wow64" but works okay with "old wow64". Running under actual 64-bit Windows is okay too. The problem seems to be caused by application logic which calls VirtualAlloc() repeatedly in order to (presumably) find out the maximum available amount of memory that the application is able to allocate. The first hint that this might be somehow related to memory were the error messages reported when running under "old wow64" : 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x74010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 74000000 Running the application with WINEDEBUG=+virtual showed the NtAllocateVirtualMemory calls that are made by the application, starting with a size of 0x7fffffff, exploring a number of different sizes, and then eventually settling on 0x701f0000 : 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 7fffffff 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x80010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 80000000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 3fffffff 2000 00000004 01a0:trace:virtual:map_view got mem in reserved area 0x11050000-0x51050000 01a0:trace:virtual:dump_view View: 0x11050000 - 0x5104ffff (valloc) 01a0:trace:virtual:dump_view 0x11050000 - 0x5104ffff --rw- 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff 0x11050000 00000000 8000 -- snip : successful calls after that with sizes 0x5fffffff , 0x6fffffff -- 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 77ffffff 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x78010000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 78000000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 -- snip : goes on to try sizes starting with 0x70 ... -- 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 701f0001 2000 00000004 01a0:err:virtual:map_view anon mmap error Cannot allocate memory, size 0x70201000, unix_prot 0 01a0:err:virtual:allocate_virtual_memory out of memory for allocation, base (nil) size 701f1000 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 01a0:trace:virtual:NtAllocateVirtualMemory 0xffffffff (nil) 701f0000 2000 00000004 01a0:trace:virtual:map_view got mem with anon mmap 0x80000000-0xf01f0000 01a0:trace:virtual:dump_view View: 0x80000000 - 0xf01effff (valloc) 01a0:trace:virtual:dump_view 0x80000000 - 0xf01effff --rw- 01a0:trace:virtual:NtFreeVirtualMemory 0xffffffff (nil) 00000000 8000 The application makes the same calls under "new wow64", but since none of those calls ever fail, it seems to get confused, reaches size=0, and then gets stuck on that size : 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 7fffffff 2000 00000004 016c:trace:virtual:map_view got mem with map_free_area 0x7fff0000-0xffff0000 016c:trace:virtual:dump_view View: 0x7fff0000 - 0xfffeffff (valloc) 016c:trace:virtual:dump_view 0x7fff0000 - 0xfffeffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x7fff0000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 3fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x51050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x5104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x5104ffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x11050000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 1fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x31050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x3104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x3104ffff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x11050000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 0fffffff 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x11050000-0x21050000 016c:trace:virtual:dump_view View: 0x11050000 - 0x2104ffff (valloc) 016c:trace:virtual:dump_view 0x11050000 - 0x2104ffff --rw- -- snip : repeated calls with size right-shifted by 1 -- 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 0000000f 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000007 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000003 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000001 2000 00000004 016c:trace:virtual:map_view got mem in reserved area 0x3750000-0x3751000 016c:trace:virtual:dump_view View: 0x3750000 - 0x3750fff (valloc) 016c:trace:virtual:dump_view 0x3750000 - 0x3750fff --rw- 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff 0x3750000 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 016c:trace:virtual:NtAllocateVirtualMemory 0xffffffffffffffff (nil) 00000000 2000 00000004 016c:trace:virtual:NtFreeVirtualMemory 0xffffffffffffffff (nil) 00000000 8000 It then loops on the call with size=0 indefinitely and keeps running until I kill the wineserver. Unfortunately, this is a proprietary legacy application so I can't share it, however I'll be more than glad to accept pointers on which debug channels to activate, any other further debugging steps, or changes to the code that might fix this. Thanks in advance. -- 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.

1 5

[Bug 54925] New: World of Warcraft WotLK Classic crashes on receiving inputs very frequently
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=54925 Bug ID: 54925 Summary: World of Warcraft WotLK Classic crashes on receiving inputs very frequently Product: Wine Version: 8.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chagatai(a)bitigchi.xyz Distribution: --- Created attachment 74446 --> https://bugs.winehq.org/attachment.cgi?id=74446 wine debug log After logging in and selecting a character the game seems to run as normal without issues. If I don't do anything and just leave the game as is without inputs it runs for quite a while without issue. But without fail, if I start making inputs the game crashes within a minute or two. Most of the debug log is just this one line: 010c:err:sync:RtlLeaveCriticalSection section 0000000000FD26C0 (null) is not acquired And when the application stops responding it's: 01d4:err:sync:RtlpWaitForCriticalSection section 0000000000FD26F0 (null) wait timed out in thread 01d4, blocked by 0000, retrying (60 sec) At which point the application stops responding and I'm forced to terminate 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.

1 3

[Bug 54508] New: psapi:psapi_main - The 64-bit test_EnumProcessModulesEx() gets unexpected snapshot counts on Windows 7 and 11
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=54508 Bug ID: 54508 Summary: psapi:psapi_main - The 64-bit test_EnumProcessModulesEx() gets unexpected snapshot counts on Windows 7 and 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: psapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com psapi:psapi_main - The 64-bit test_EnumProcessModulesEx() gets unexpected snapshot counts on Windows 7 and 11: w7pro64: psapi_main.c:483: Test failed: pcs-6432: Wrong count 23 in C:\Windows\SysWOW64 psapi_main.c:488: Test failed: pcs-6432: Wrong count 2 in C:\Windows\system32 w11pro64: psapi_main.c:488: Test failed: pcs-6432: Wrong count 0 in C:\Windows\system32 See https://test.winehq.org/data/patterns.html#psapi:psapi_main These failures don't happen on Windows 8 to Windows 10! These tests and failures were introduced in the following commit: commit e38455a2181ab5ce0bf842f2c9a638b3ee9b538c Author: Eric Pouech <eric.pouech(a)gmail.com> AuthorDate: Tue Feb 14 11:06:57 2023 +0100 psapi/tests: Test directory of enumerated loaded modules. Showing that Wine incorrectly reports, for a Wow64 process, the system DLLs from within the wow64 directory while they should be from system32. Signed-off-by: Eric Pouech <eric.pouech(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.

1 3

[Bug 54436] New: wine-staging-8.0 regression (not working): Command & Conquer 3: Tiberium Wars Kane's Wrath
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=54436 Bug ID: 54436 Summary: wine-staging-8.0 regression (not working): Command & Conquer 3: Tiberium Wars Kane's Wrath Product: Wine-staging Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73981 --> https://bugs.winehq.org/attachment.cgi?id=73981 wine-staging-8.0: left is fine, right is broken With wine-staging-7.0 "Command & Conquer 3: Tiberium Wars Kane's Wrath" was working fine. In wine-8.0 and wine-staging-8.0 it's broken. With wine-staging-8.0 the menu looks broken. See attached screenshot. (left is fine, right is broken) With wine-8.0 the menu loads, but starting a skirmish game crashes the application. There's an error dialog window saying: Direct3D error 0x8007000e (E_OUTOFMEMORY) -- 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.

1 33

[Bug 58129] New: shlwapi::PathCombineW does not manage path starting with dots
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58129 Bug ID: 58129 Summary: shlwapi::PathCombineW does not manage path starting with dots Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shlwapi Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Created attachment 78395 --> http://bugs.winehq.org/attachment.cgi?id=78395 sample app Inspired by https://bugs.winehq.org/show_bug.cgi?id=4309 and https://jira.reactos.org/browse/CORE-20129 Use this simple NSI script : Section System::Call 'shlwapi::PathCombineW(w.r1,w "C:\", w "...xx")' MessageBox MB_OK $1 SectionEnd Shows "C:.xx" in Wine while it shows "C:\...xx" in Windows -- 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.

1 4

[Bug 58841] New: unable to compile rsaenh, wine compilation fails
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58841 Bug ID: 58841 Summary: unable to compile rsaenh, wine compilation fails Product: Wine Version: 10.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: rsaenh Assignee: wine-bugs(a)winehq.org Reporter: infyquest(a)gmail.com Distribution: --- This is error that comes, when I try to compile wine - it fails while compiling rsaenh. The built it using the below one: ../wine-iq-devel/configure --enable-win64 Below is the error: gcc -m64 -c -o dlls/rsaenh/implglue.o ../wine-iq-devel/dlls/rsaenh/implglue.c -Idlls/rsaenh -I../wine-iq-devel/dlls/rsaenh \ -Iinclude -I../wine-iq-devel/include -I../wine-iq-devel/include/msvcrt \ -I../wine-iq-devel/libs/tomcrypt/src/headers -D_UCRT -D__WINESRC__ -DLTC_NO_PROTOTYPES \ -DLTC_SOURCE -Wall -pipe -fcf-protection=none -fvisibility=hidden -fno-stack-protector \ -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Winit-self \ -Wlogical-op -Wno-packed-not-aligned -Wpointer-arith -Wshift-overflow=2 -Wstrict-prototypes \ -Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wno-misleading-indentation \ -gdwarf-4 -fPIC -fasynchronous-unwind-tables -D_WIN32 -fno-builtin -fshort-wchar -Wno-format \ -mabi=ms -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 In file included from ../wine-iq-devel/dlls/rsaenh/implglue.c:32: ../wine-iq-devel/dlls/rsaenh/implglue.h:32:5: error: unknown type name ‘symmetric_key’ 32 | symmetric_key key; | ^~~~~~~~~~~~~ ../wine-iq-devel/dlls/rsaenh/implglue.h:43:5: error: unknown type name ‘hash_state’ 43 | hash_state state; | ^~~~~~~~~~ -- 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.

1 3

[Bug 58642] New: foobar2000 crashes on launch
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58642 Bug ID: 58642 Summary: foobar2000 crashes on launch Product: Wine Version: 10.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: just4steam778(a)gmail.com Distribution: ArchLinux Created attachment 79204 --> http://bugs.winehq.org/attachment.cgi?id=79204 Log foobar2000 crashes on launch when the system is set to Windows 10 or 11. foobar2000 2.24.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.

1 6

[Bug 58904] New: MS works 8.0
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58904 Bug ID: 58904 Summary: MS works 8.0 Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lars_martin4(a)hotmail.com Distribution: --- Created attachment 79585 --> http://bugs.winehq.org/attachment.cgi?id=79585 need reboot after reboot larsmartinhambro(a)ti0108q160-5220:/run/media/larsmartinhambro/WORKS8/MSWorks$ wine Autorun.exe 002c:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0070:err:environ:init_peb starting L"C:\\Program Files (x86)\\HDD Health\\HDDHealthService.exe" in experimental wow64 mode 0070:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented! 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0024:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0168:err:environ:init_peb starting L"D:\\MSWorks\\Autorun.exe" in experimental wow64 mode 0170:err:environ:init_peb starting L"D:\\MSWorks\\Install.exe" in experimental wow64 mode larsmartinhambro(a)ti0108q160-5220:/run/media/larsmartinhambro/WORKS8/MSWorks$ 0170:fixme:winediag:loader_init wine-staging 10.15 is a testing version containing experimental patches. 0170:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0170:fixme:wtsapi:WTSEnumerateSessionsW 00000000 0x00000000 0x00000001 0012F240 0012F270 semi-stub. 0178:err:environ:init_peb starting L"D:\\MSWorks\\Redist\\mdac\\mdac_typ.exe" in experimental wow64 mode 0188:err:environ:init_peb starting L"C:\\windows\\syswow64\\winevdm.exe" in experimental wow64 mode 0188:fixme:wow:wow64_NtSetLdtEntries 0107 0488323f 0000f39a 0000 00000000 00000000: stub 0188:err:module:loader_init "krnl386.exe16" failed to initialize, aborting 0188:err:module:loader_init Initializing dlls for L"C:\\windows\\syswow64\\winevdm.exe" failed, status c0000005 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 4d02c (device=4 access=3 func=40b method=0) -- 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.

1 2

[Bug 58843] New: black screen for opening movies when playing GTA SA, GTA 3
by WineHQ Bugzilla 10 Nov '25

10 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58843 Bug ID: 58843 Summary: black screen for opening movies when playing GTA SA, GTA 3 Product: Wine Version: 10.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: erwiniosef(a)gmail.com Distribution: --- Created attachment 79507 --> http://bugs.winehq.org/attachment.cgi?id=79507 GTA: SA backtrace Movies run fine with 10.16 but not on wine 10.17, tested with a clean prefix. Note I run GTA: SA with [Silent Patch](https://www.pcgamingwiki.com/wiki/Grand_Theft_Auto:_San_Andreas#Sile…, but I'm pretty sure it doesn't work with the game in vanilla. -- 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.

1 3