[Bug 38411] New: Infinite wait for start
https://bugs.winehq.org/show_bug.cgi?id=38411 Bug ID: 38411 Summary: Infinite wait for start Product: Wine Version: 1.7.40 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru err:ntdll:RtlpWaitForCriticalSection section 0x9f0060 "heap.c: HEAP.critSection" wait timed out in thread 0063, blocked by 005d, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7bc9801c "loader.c: loader_section" wait timed out in thread 0050, blocked by 0063, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7bc9801c "loader.c: loader_section" wait timed out in thread 0051, blocked by 0063, retrying (60 sec) What is the reason to wait 60sec again and again if we have emulated hardware? -- 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=38411 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|ntdll |-unknown --- Comment #1 from Austin English <austinenglish(a)gmail.com> --- What application? How to reproduce 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=38411 --- Comment #2 from Sergey Isakov <isakov-sl(a)bk.ru> --- (In reply to Austin English from comment #1)
What application? How to reproduce the bug?
3DMark05 with FuturemarkSystemInfo 4.2.8 The bug is happen every second start. OSX 10.9.5 AMD Radeon 6670 if it does matter. May be I have to make more tracing? -- 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=38411 --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- (In reply to Sergey Isakov from comment #2)
(In reply to Austin English from comment #1)
What application? How to reproduce the bug?
3DMark05 with FuturemarkSystemInfo 4.2.8 The bug is happen every second start.
OSX 10.9.5 AMD Radeon 6670 if it does matter.
May be I have to make more tracing?
Attaching the full terminal output is always a good start. In the case of a deadlock, you need to run winedbg then get a list of the threads, see: http://wiki.winehq.org/Backtraces in short: (in 1st terminal) wine foo.exe (from now on in a separate terminal) winedbg bt all and copy/paste the bt all output into a text file and attach here (you'll need to get the deadlock info again, as the thread ids will be different). -- 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=38411 --- Comment #4 from Sergey Isakov <isakov-sl(a)bk.ru> --- I see only --- $ winedbg 'xterm-256color': unknown terminal type. --- This is MacOS, not linux. This time the hang appear at exit. I attached full 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=38411 --- Comment #5 from Sergey Isakov <isakov-sl(a)bk.ru> --- Created attachment 51266 --> https://bugs.winehq.org/attachment.cgi?id=51266 log when 3DMark hang at exit -- 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=38411 --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- (In reply to Sergey Isakov from comment #4)
I see only
--- $ winedbg 'xterm-256color': unknown terminal type. ---
This is MacOS, not linux.
The instructions are not OS specific, so I don't see how that matters. That is a configuration issue.
This time the hang appear at exit. I attached full log.
DbgPrint says: (null)(IRQL 00): Driver compiled at 17:01:51 on Sep 11 2010 fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPUZ(IRQL 00): Created device: \Device\GPUZ fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPUZ(IRQL 00): Created link: \??\GPUZ -> \Device\GPUZ fixme:ntoskrnl:IoRegisterShutdownNotification stub: 0x1124b8 wine: Unhandled page fault on read access to 0xffffffff at address 0x541b9c (thread 0062), starting debugger... Looks like your crash is GPU-Z. Try installing 3dmark05 by itself in a clean 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=38411 --- Comment #7 from Sergey Isakov <isakov-sl(a)bk.ru> --- GPU-Z is .dll from FutureMark SystemInfo according to this instructions https://appdb.winehq.org/objectManager.php?sClass=version&iId=7133 -- 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=38411 --- Comment #8 from Austin English <austinenglish(a)gmail.com> --- (In reply to Sergey Isakov from comment #7)
GPU-Z is .dll from FutureMark SystemInfo according to this instructions https://appdb.winehq.org/objectManager.php?sClass=version&iId=7133
Does not installing SystemInfo avoid the 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=38411 --- Comment #9 from Sergey Isakov <isakov-sl(a)bk.ru> --- 3DMark installed old version of the SystemInfo that crashes immediately. New version 4.2.8 must be installed instead of native to have an ability to start 3dmark as a chance 1:2. Anyway I found a bug 20296 and it looks to be similar. -- 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=38411 --- Comment #10 from Sergey Isakov <isakov-sl(a)bk.ru> --- I installed latest SystemInfo 4.3.6 and got immediate crash fixme:ntdll:NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: (null)(IRQL 00): Driver compiled at 17:01:51 on Sep 11 2010 fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPUZ(IRQL 00): Created device: \Device\GPUZ fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: GPUZ(IRQL 00): Created link: \??\GPUZ -> \Device\GPUZ fixme:ntoskrnl:IoRegisterShutdownNotification stub: 0x112638 wine: Unhandled page fault on read access to 0xffffffff at address 0x541b9c (thread 0067), starting debugger... fixme:ntdll:NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030 fixme:wbemprox:enum_class_object_Next timeout not supported fixme:ddraw:ddrawformat_from_wined3dformat Unhandled wined3d format 0. wine: Unhandled page fault on write access to 0x00000000 at address 0x438b2f3d (thread 004c), starting debugger... Application tried to create a window, but no driver could be loaded. The explorer process failed to start. err:ole:CoUninitialize Mismatched CoUninitialize fixme:win:LockWindowUpdate (0x0), partial stub! err:ole:CoReleaseMarshalData IMarshal::ReleaseMarshalData failed with error 0x8001011d -- 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=38411 --- Comment #11 from Sergey Isakov <isakov-sl(a)bk.ru> --- Wine-1.7.41 Still same problem --- fixme:ntoskrnl:IoRegisterShutdownNotification stub: 0x1124b8 wine: Unhandled page fault on read access to 0xffffffff at address 0x541b9c (thread 0063), starting debugger... fixme:ntoskrnl:KeGetCurrentIrql stub! DbgPrint says: (null)(IRQL 00): Driver compiled at 17:01:51 on Sep 11 2010 ---- I may confirm that working version of Futuremark SystemInfo is 4.2.8. Latest 4.3.6 just crashes with "unhandled exception". Don't know if it is wine problem. But I think on real Windows it works. -- 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=38411 --- Comment #12 from Sergey Isakov <isakov-sl(a)bk.ru> --- Waiting finished if I press "Windows" button. -- 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=38411 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Infinite wait for start |3DMark05 deadlocks 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=38411 --- Comment #13 from Artem S. Tashkinov <t.artem(a)mailcity.com> --- Most likely it's a dupe of bug 35041. Secondly Wine doesn't support loading Windows [kernel] drivers so 3DMark must be run with -nosysteminfo. Most likely this bug is 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.
https://bugs.winehq.org/show_bug.cgi?id=38411 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW URL| |http://filehippo.com/downlo | |ad_3dmark05/ CC| |focht(a)gmx.net Component|-unknown |wmi&wbemprox Summary|3DMark05 deadlocks on start |3DMark05 v1.30 crashes | |during system info scan | |(needs support for | |'Win32_Process' WMI class | |'WorkingSetSize' property) Ever confirmed|0 |1 --- Comment #14 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, please stick to the rules that is *one* problem per bug. You're mixing entirely different issues here (also dupes). The "deadlocks" and/or "hangs" are likely the result of a broken WINEPREFIX. There are several failures in the logs indicating this. One for example: --- snip --- fixme:ole:CoCreateInstance no instance created for interface {9c6b4cb0-23f8-49cc-a3ed-45a55000a6d2} of class {a65b8071-3bfe-4213-9a5b-491da4461ca7}, hres is 0x80040155 --- snip --- (broken DxDiag provider COM server registration) Also mixing old Wine version versions: --- snip --- fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled fixme:wbemprox:enum_class_object_Next timeout not supported err:wbemprox:wql_error syntax error, unexpected TK_ID, expecting TK_SELECT --- snip --- (was fixed a long time ago) I installed the app in a clean 32-bit WINEPREFIX and found only one problem among others (dupes) worth to look at: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Futuremark/3DMark05 $ WINEDEBUG=+tid,+seh,+relay,+wbemprox wine ./3DMark05.exe >>log.txt 2>&1 ... 0026:trace:wbemprox:enum_class_object_Next 0x178a78, 2000, 1, 0x32ebd0, 0x32ebcc 0026:fixme:wbemprox:enum_class_object_Next timeout not supported 0026:trace:wbemprox:create_class_object L"Win32_Process", 0x32ebd0 ... 0026:trace:wbemprox:class_object_Get 0x1cf8f38, L"Name", 00000000, 0x32ebb4, (nil), (nil) ... 0026:trace:wbemprox:class_object_Get 0x1cf8f38, L"ProcessId", 00000000, 0x32ebb4, (nil), (nil) ... 0026:Call oleaut32.SysAllocString(0032eb30 L"WorkingSetSize") ret=1003c4bd 0026:Ret oleaut32.SysAllocString() retval=00213d34 ret=1003c4bd 0026:Call oleaut32.VariantInit(0032ebac) ret=10035a59 0026:Ret oleaut32.VariantInit() retval=0032ebac ret=10035a59 0026:trace:wbemprox:class_object_Get 0x1cf8f38, L"WorkingSetSize", 00000000, 0x32ebac, (nil), (nil) 0026:Call KERNEL32.InterlockedDecrement(0070b1c0) ret=1001a05c 0026:Ret KERNEL32.InterlockedDecrement() retval=00000000 ret=1001a05c 0026:Call oleaut32.SysFreeString(00213d34 L"WorkingSetSize") ret=10019f13 0026:Ret oleaut32.SysFreeString() retval=00000000 ret=10019f13 0026:Call msvcr80.??3(a)YAXPAX@Z(0070b1b8) ret=1001a073 0026:Call ntdll.RtlFreeHeap(00700000,00000000,0070b1b8) ret=7ebb412c 0026:Ret ntdll.RtlFreeHeap() retval=00000001 ret=7ebb412c 0026:Ret msvcr80.??3(a)YAXPAX@Z() retval=00000001 ret=1001a073 0026:Call ntdll._atoi64(00000000) ret=1003363d 0026:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7bc94381 ip=7bc94381 tid=0026 0026:trace:seh:raise_exception info[0]=00000000 0026:trace:seh:raise_exception info[1]=00000000 0026:trace:seh:raise_exception eax=00000000 ebx=00000000 ecx=00000000 edx=00000004 esi=0032ebd8 edi=0032eba4 0026:trace:seh:raise_exception ebp=0032eb98 esp=0032eb80 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00210202 ... 0026:Call msvcr71._CxxThrowException(00000000,00000000) ret=00414428 0026:Call KERNEL32.RaiseException(e06d7363,00000001,00000003,0032e494) ret=7dc7b905 0026:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b845669 ip=7b845669 tid=0026 0026:trace:seh:raise_exception info[0]=19930520 0026:trace:seh:raise_exception info[1]=00000000 0026:trace:seh:raise_exception info[2]=00000000 0026:trace:seh:raise_exception eax=7b832505 ebx=00000000 ecx=0000000c edx=0032e3e4 esi=0032e490 edi=0032e450 0026:trace:seh:raise_exception ebp=0032e428 esp=0032e3c4 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00200202 ... Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x7b845669). ... Backtrace: =>0 0x7b845669 RaiseException+0x81(code=<couldn't compute location>, flags=<couldn't compute location>, nbargs=<couldn't compute location>, args=<couldn't compute location>) [/home/focht/projects/wine/wine.repo/src/dlls/kernel32/except.c:84] in kernel32 (0x0032e428) 1 0x7bc7c8be relay_call+0x39() in ntdll (0x0032e468) 2 0x7b830399 in kernel32 (+0x10398) (0x0032e4a8) 3 0x7dc7b905 _CxxThrowException+0x47(object=<couldn't compute location>, type=<couldn't compute location>) [/home/focht/projects/wine/wine.repo/src/dlls/msvcr71/../msvcrt/cpp.c:1152] in msvcr71 (0x0032e4a8) 4 0x7bc7c8be relay_call+0x39() in ntdll (0x0032e4e0) 5 0x7dc7450d in msvcr71 (+0x450c) (0x0032f9c8) 6 0x00414428 in 3dmark05 (+0x14427) (0x0032f9c8) 7 0x00404da6 in 3dmark05 (+0x4da5) (0x0032fd78) 8 0x7c172fb6 in mfc71 (+0x32fb5) (0x0032fe30) ... Modules: Module Address Debug info Name (200 modules) PE 330000- 35c000 Deferred exporter PE 400000- 6f9000 Export 3dmark05 PE 10000000-10070000 Deferred si3 ... Threads: process tid prio (all id:s are in hex) ... 00000025 (D) C:\Program Files\Futuremark\3DMark05\3DMark05.exe 00000032 0 00000031 0 00000026 0 <== --- snip --- MSDN: https://msdn.microsoft.com/en-us/library/aa394372%28v=vs.85%29.aspx --- quote --- WorkingSetSize Data type: uint64 Access type: Read-only Qualifiers: Units ("Bytes") Amount of memory in bytes that a process needs to execute efficiently—for an operating system that uses page-based memory management. If the system does not have enough memory (less than the working set size), thrashing occurs. If the size of the working set is not known, use NULL or 0 (zero). If working set data is provided, you can monitor the information to understand the changing memory requirements of a process. For more information about using uint64 values in scripts, see Scripting in WMI. --- quote --- Source: https://source.winehq.org/git/wine.git/blob/96b5d9aa973dade6d93b504ee19c536c... $ sha1sum 3DMark05_v130_installer.exe 94b2e30fb45ef08fb40fdb823e1528bf0255922c 3DMark05_v130_installer.exe $ du -sh 3DMark05_v130_installer.exe 287M 3DMark05_v130_installer.exe $ wine --version wine-1.7.45-146-gaf55ae1 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=38411 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |927400be6318ff65bb8b99f6c59 | |faeb1ca075e9f Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #15 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, this is fixed by commit https://source.winehq.org/git/wine.git/commitdiff/927400be6318ff65bb8b99f6c5... Thanks Hans 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=38411 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.7.46. -- 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=38411 --- Comment #17 from Sergey Isakov <isakov-sl(a)bk.ru> --- No, this fix didn't resolve the hang on start. It appears in 1.7.54 again. See new opened bug 39674. -- 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=38411 --- Comment #18 from Anastasius Focht <focht(a)gmx.net> --- Hello Sergey, --- quote --- No, this fix didn't resolve the hang on start. --- quote --- --- quote --- First regression correspond to bug 38411 wrongly closed. This is strange that the hang on start was "cured" by that fix and reappeared in version 1.7.54. --- quote --- There is no "wrong close" here. Please understand how the development process works. Regressions caused by other changes have nothing to do with this specific issue and should not be mixed in here. The cause of the crash was clearly traced to missing functionality (see my comment #14) and has been fixed. 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=38411 --- Comment #19 from Sergey Isakov <isakov-sl(a)bk.ru> --- This is one of the reason to wrong behavior. Imagine a car that broke its wheel jumping on small stone. You tell that the stone is reason. I tell that the wheel was bad reliability... New changes in wine causes same bug again. New stone fragment on the road and new breakage. OK, you are right, we should clean up roads. -- 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=38411 --- Comment #20 from Sergey Isakov <isakov-sl(a)bk.ru> --- I can't start the game with wine-4.2. Looks like the same 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=38411 Sergey Isakov <isakov-sl(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|http://filehippo.com/downlo |https://benchmarks.ul.com/l |ad_3dmark05/ |egacy-benchmarks -- 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=38411 Sergey Isakov <isakov-sl(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|CLOSED |REOPENED URL|https://benchmarks.ul.com/l |http://filehippo.com/downlo |egacy-benchmarks |ad_3dmark05/ --- Comment #21 from Sergey Isakov <isakov-sl(a)bk.ru> --- The game hangs at start with wine-4.2. I updated official download link. -- 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=38411 Sergey Isakov <isakov-sl(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|http://filehippo.com/downlo |https://benchmarks.ul.com/l |ad_3dmark05/ |egacy-benchmarks -- 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=38411 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REOPENED |RESOLVED CC| |joseph.kucia(a)gmail.com --- Comment #22 from Józef Kucia <joseph.kucia(a)gmail.com> --- Please don't reopen this bug again. It was explained in the comment #18 that this 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=38411 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #23 from Józef Kucia <joseph.kucia(a)gmail.com> --- Closing -- 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=38411 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|https://benchmarks.ul.com/l |https://web.archive.org/web |egacy-benchmarks |/20211120180200/http://file | |s.3dnews.org/pub/bench/3DMa | |rk05_v130_installer.exe --- Comment #24 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, adding stable download link via Internet Archive for documentation. https://web.archive.org/web/20211120180200/http://files.3dnews.org/pub/bench... https://www.virustotal.com/gui/file/e6175d58b0f24443d38196d5e6ccb40e52c0e912... $ sha1sum 3DMark05_v130_installer.exe 94b2e30fb45ef08fb40fdb823e1528bf0255922c 3DMark05_v130_installer.exe $ du -sh 3DMark05_v130_installer.exe 287M 3DMark05_v130_installer.exe 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla