[Bug 39674] New: 3Dmark03, 05, 06 not started "Systen Info Error" (double regression)
https://bugs.winehq.org/show_bug.cgi?id=39674 Bug ID: 39674 Summary: 3Dmark03, 05, 06 not started "Systen Info Error" (double regression) Product: Wine Version: 1.7.55 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Created attachment 52897 --> https://bugs.winehq.org/attachment.cgi?id=52897 how the stop looks Since wine-1.7.55 the Futuremark applications 3DMark03, 3DMark05, 3DMark06 stop working with messages "System Info error" or "unhandled exception". With wine 1.7.54 they are working. Regression test give the follow ~~~ quote ~~~ $ git bisect bad f91a7b2cfe5b44fea333ed70b9fc38a509b7798a is the first bad commit commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a Author: Austin English <austinenglish(a)gmail.com> Date: Wed Nov 4 10:46:50 2015 -0800 fltmgr.sys: Add FltInitializePushLock stub. Signed-off-by: Austin English <austinenglish(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 9a8f22f1f54f0af7b77216ea29b6360699eacb7e 5185e955c2cb2fe5ca9fa65034af095a9137d23a M dlls :040000 040000 a04028464398c6fceebbbe76e03446a3c2b8cb35 637e2081747c7c533f27d2a0f4ab1258d53bf9fa M include ~~~ quote ~~~ Meanwhile there is double regression as I notice in bug 36548. First regression was 1.7.54 working 1.7.54-140-7fbf33f hang at start. This regression reported and bisecting in 36548. commit 8cc5b07e9d0aedffd4251d2e8942cb8368920bf8 Second regression 1.7.54-134-gd4664c1 works but hang on exit 1.7.55 not working with the message. See attached screenshot. This regression I bisecting here. Strange to see this commit as regression. Analysis. Then I found a key difference in logs. Working log contains: ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x9f6048,0x8beb54): stub ---- Non-working ---- fixme:process:GetLogicalProcessorInformationEx (65535,0x0,0x5203e8): stub ---- Note: second argument is ZERO. 3DMark application works in conjunction with Futuremarks SystemInfo (called by OLE?) and I may propose the SystemInfo calls the function but in second case it will not allocate buffer for CPU info. BOOL WINAPI GetLogicalProcessorInformationEx(LOGICAL_PROCESSOR_RELATIONSHIP relationship, PSYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX buffer, PDWORD pBufLen) Why? Because there are new stubs? This procedure should return false if no buffer? Or this procedure should allocate this buffer? -- 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=39674 --- Comment #1 from Sergey Isakov <isakov-sl(a)bk.ru> --- Link to download full versions http://www.futuremark.com/benchmarks/legacy -- 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=39674 --- Comment #2 from Sergey Isakov <isakov-sl(a)bk.ru> --- There is no FIXME( "(%p): stub\n", lock ); from FltInitializePushLock in the log. So the regression test is not true. -- 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=39674 --- Comment #3 from Sergey Isakov <isakov-sl(a)bk.ru> --- About function GetLogicalProcessorInformationEx() MSDN says If the function succeeds, the return value is TRUE and at least one SYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX structure is written to the output buffer. While wine return TRUE and buflen=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.
https://bugs.winehq.org/show_bug.cgi?id=39674 --- Comment #4 from Sergey Isakov <isakov-sl(a)bk.ru> --- What was the commit that changed FALSE to true? -- 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=39674 --- Comment #5 from Sergey Isakov <isakov-sl(a)bk.ru> --- Bisecting fails because this function changed several times and so I went to wrong commit... -- 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=39674 --- Comment #6 from Sergey Isakov <isakov-sl(a)bk.ru> --- Sorry, comments 3,4,5 are wrong. -- 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=39674 --- Comment #7 from Sergey Isakov <isakov-sl(a)bk.ru> --- Now I made regression test on other configuration with 3DMark05. There is simple regression 1.7.54 good -187 good -280 bad -233 good -256 bad -244 bad -238 bad -235 bad -234 bad 1.7.55 bad $ git bisect bad b6710c2a006234ac1a729881e7ca75d34cffb474 is the first bad commit commit b6710c2a006234ac1a729881e7ca75d34cffb474 Author: Austin English <austinenglish(a)gmail.com> Date: Mon Nov 9 00:45:29 2015 -0600 bthprops.cpl: Add stub dll. Signed-off-by: Austin English <austinenglish(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :100755 100755 e1f69e0b3eaa2d89fcc9cbe97144a23b683fddf7 35705f56b3d7bdc8ae7880031d9af63a5d0c4e81 M configure :100644 100644 b9f90c7c84c8a5d2c83973eeff5d827693f361cd c6a8b3e2a6acbd0c6e74a90b94fb31b50b3c684f M configure.ac :040000 040000 ae533e325004f82b24c7631c981d3a49926a6da5 4d09c7919bb1e8260c6236af243f42df1206e3f2 M dlls Why Bluetooth? May be these stubs? +@ stub DllCanUnloadNow +@ stub DllGetClassObject About logs. I saved all intermediate compilation and can repeat test with any of these versions. Double check: 233 works, 234 not works. I see log from 233 contains line fixme:process:GetLogicalProcessorInformationEx (65535,0xcc6050,0x8beb54): stub Next versions have no such line. -- 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=39674 --- Comment #8 from Nikolay Sivov <bunglehead(a)gmail.com> --- Please first verify that commit you found is actually a problem, and not a testing error. When you sure it works before it and breaks on it, post this 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=39674 --- Comment #9 from Sergey Isakov <isakov-sl(a)bk.ru> --- Yes, next step get most recent wine ~~~ $ git describe head wine-1.8-rc1-89-g4a315cd ~~~ Revert this commit ~~~ $ patch -p1 <patch-b6710.txt patching file configure Reversed (or previously applied) patch detected! Assume -R? [n] y Hunk #1 succeeded at 973 with fuzz 2 (offset 9 lines). Hunk #2 succeeded at 17372 with fuzz 1 (offset -93 lines). patching file configure.ac Reversed (or previously applied) patch detected! Assume -R? [n] y Hunk #1 succeeded at 2713 with fuzz 1 (offset -109 lines). The next patch would create the file dlls/bthprops.cpl/Makefile.in, which already exists! Assume -R? [n] y patching file dlls/bthprops.cpl/Makefile.in The next patch would create the file dlls/bthprops.cpl/bthprops.cpl.spec, which already exists! Assume -R? [n] y patching file dlls/bthprops.cpl/bthprops.cpl.spec Hunk #1 FAILED at 1. File dlls/bthprops.cpl/bthprops.cpl.spec is not empty after patch, as expected 1 out of 1 hunk FAILED -- saving rejects to file dlls/bthprops.cpl/bthprops.cpl.spec.rej ~~~ Compile and run. It works!!!! There is again a line in log ~~~ fixme:process:GetLogicalProcessorInformationEx (65535,0xaf6050,0x8beb54): stub ~~~ Full prove! What else I can do for this bug? I don't know a theory how it works. Probably the authors of the dlls/kernel32/process.c may light the question. Namely * Copyright 1996, 1998 Alexandre Julliard -- 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=39674 Sergey Isakov <isakov-sl(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |b6710c2a006234ac1a729881e7c | |a75d34cffb474 -- 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=39674 --- Comment #10 from Sergey Isakov <isakov-sl(a)bk.ru> --- 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. Attempt to make regression test for that hang in bug 36548 seems have no changes for success. Looks like it depends on uninitialized variables or CPU cores load. -- 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=39674 Sergey Isakov <isakov-sl(a)bk.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.futuremark.com/b | |enchmarks/legacy -- 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=39674 --- Comment #11 from Sergey Isakov <isakov-sl(a)bk.ru> --- I have to confirm that reverting commit b6710c2a006234ac1a729881e7ca75d34cffb474 will also resolve the issue with 3DMark03 on second configuration. It is not arbitrary success and not depends on compilation. Wine-1.8-rc2 -- 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=39674 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE Regression SHA1|b6710c2a006234ac1a729881e7c | |a75d34cffb474 | --- Comment #12 from Austin English <austinenglish(a)gmail.com> --- I don't see any mention of -nosysteminfo, which is needed to bypass bug 20296 (which is likely what you're seeing). This works for me in 1.5.54 and 1.8-rc2-41-gc87a78b if -nosysteminfo is used. Without it, I get the error you describe. A +relay doesn't show any references to fltmgr or bthprops. Dupe. *** This bug has been marked as a duplicate of bug 20296 *** -- 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=39674 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #13 from Austin English <austinenglish(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=39674 --- Comment #14 from Sergey Isakov <isakov-sl(a)bk.ru> --- This workaround is also valid for wine-staging-1.8rc2. Looks like Futuremark SystemInfo doesn't like fake Bluetooth.cpl -- 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=39674 --- Comment #15 from Sergey Isakov <isakov-sl(a)bk.ru> --- No, it is not duplicate of 20296. See https://bugs.winehq.org/show_bug.cgi?id=36548#c4 -- 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=39674 --- Comment #16 from Austin English <austinenglish(a)gmail.com> --- (In reply to Sergey Isakov from comment #14)
This workaround is also valid for wine-staging-1.8rc2.
Looks like Futuremark SystemInfo doesn't like fake Bluetooth.cpl
I see no evidence of that here. The previous information in the bug is about fltmgr.sys and bthprops.cpl, not bluetooth.cpl (and that info has changed a few times). There is no reference to bluetooth.cpl in the relay log either. For me, with -nosysteminfo, 3dmark03 launches fine, as it did in 1.7.54. I suspect your regression test is wrong, as you've mentioned it may be timing/load related. Additionally, bluetooth wasn't in Windows when 3DMark03 was released (it came in XP SP2, released in 2004), so I highly doubt 3DMark03 has any knowledge of bluetooth (additionally, why would a d3d benchmark need/use bluetooth). -- 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=39674 --- Comment #17 from Sergey Isakov <isakov-sl(a)bk.ru> --- (In reply to Austin English from comment #16)
(In reply to Sergey Isakov from comment #14)
This workaround is also valid for wine-staging-1.8rc2.
Looks like Futuremark SystemInfo doesn't like fake Bluetooth.cpl
I see no evidence of that here. The previous information in the bug is about fltmgr.sys and bthprops.cpl, not bluetooth.cpl (and that info has changed a few times). There is no reference to bluetooth.cpl in the relay log either.
For me, with -nosysteminfo, 3dmark03 launches fine, as it did in 1.7.54. I suspect your regression test is wrong, as you've mentioned it may be timing/load related.
Additionally, bluetooth wasn't in Windows when 3DMark03 was released (it came in XP SP2, released in 2004), so I highly doubt 3DMark03 has any knowledge of bluetooth (additionally, why would a d3d benchmark need/use bluetooth).
No, I am right. First see the commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a contents ~~~~ +++ b/dlls/bthprops.cpl/bthprops.cpl.spec @@ -0,0 +1,65 @@ +@ stub BluetoothAddressToString +@ stub BluetoothAuthenticateDevice +@ stub BluetoothAuthenticateDeviceEx +@ stub BluetoothAuthenticateMultipleDevices +@ stub BluetoothAuthenticationAgent ~~~ It is Bluetooth Properties Control Panel as I think. Second, I made careful regression test. I saved all intermediate wine-1.7.54-xxx and can check again with any of them. Third, I checked that reverting this commits in wine-1.8rc2 allows me to start 3DMark03, 3DMark05 and 4DMark06 in different installations without the argument -no-systeminfo. Without this argument the application Futuremark SystemInfo is called. To success we need version 428 of the application. The trick is described on this site: - Install 3DMark05. Full installation. - Uninstall followed Futuremark SystemInfo provided with it. - Install Futuremark SystemInfo -4.2.8 $ md5 Futuremark_SystemInfo_v428_installer.msi MD5 (Futuremark_SystemInfo_v428_installer.msi) = 4fdc487ed5948703e63011aa28e05447 Take wine-1.7.54. Now you can start 3DMark05 with SystemInfo. For wine versions >= 1.7.55 you have to revert commit f91a7b2cfe5b44fea333ed70b9fc38a509b7798a Tested several times on several configurations. The bug has no any relation to bug 20296. -- 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=39674 --- Comment #18 from Austin English <austinenglish(a)gmail.com> --- I can't reproduce on 3DMark05 either, works fine here. Please attach a +relay,+seh,+tid trace (start notepad first to reduce logsize, and compress). -- 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=39674 --- Comment #19 from Sergey Isakov <isakov-sl(a)bk.ru> --- (In reply to Austin English from comment #18)
I can't reproduce on 3DMark05 either, works fine here.
Please attach a +relay,+seh,+tid trace (start notepad first to reduce logsize, and compress).
May be this bug related to Fturemark SystemInfo 428. Do you have the same version? I can make such logs a little later with pure wine-hq (git pull), and after revert those bad commit. -- 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=39674 --- Comment #20 from Sergey Isakov <isakov-sl(a)bk.ru> --- Created attachment 53001 --> https://bugs.winehq.org/attachment.cgi?id=53001 Log with wine-1.8rc3, unpacked size 181.7Mb Tested with wine-1.8-rc3. This is full log from start to finish with message attached. -- 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=39674 --- Comment #21 from Sergey Isakov <isakov-sl(a)bk.ru> --- Created attachment 53002 --> https://bugs.winehq.org/attachment.cgi?id=53002 Ended with this message -- 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=39674 --- Comment #22 from Sergey Isakov <isakov-sl(a)bk.ru> --- Created attachment 53003 --> https://bugs.winehq.org/attachment.cgi?id=53003 Full log with wine-1.8-rc3 with reverted the regression commit Unpacked size 809Mb. But this log is not interesting because 3DMark05 is working. Screenshot attached too -- 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=39674 --- Comment #23 from Sergey Isakov <isakov-sl(a)bk.ru> --- Created attachment 53004 --> https://bugs.winehq.org/attachment.cgi?id=53004 With patched wine 3DMark05 works. All conditions are the same. Just changed wine with a small patch: revert commit b6710c2a006234ac1a729881e7ca75d34cffb474 -- 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=39674 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |austinenglish(a)gmail.com Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #24 from Austin English <austinenglish(a)gmail.com> --- (In reply to Sergey Isakov from comment #20)
Created attachment 53001 [details] Log with wine-1.8rc3, unpacked size 181.7Mb
Tested with wine-1.8-rc3. This is full log from start to finish with message attached.
Thanks. The log was clobbered a bit (try using &>> next time), but it looks like it wants: bthprops.cpl.BluetoothFindFirstRadio I'll attach a stub patch in a little bit. I do wonder why you get this but I don't, however.. -- 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=39674 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |b6710c2a006234ac1a729881e7c | |a75d34cffb474 --- Comment #25 from Nikolay Sivov <bunglehead(a)gmail.com> --- Does it work if you disable bthprops.cpl? -- 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=39674 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|3Dmark03, 05, 06 not |3Dmark03, 05, 06 not |started "Systen Info Error" |started "System Info Error" |(double regression) | -- 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=39674 --- Comment #26 from Austin English <austinenglish(a)gmail.com> --- Created attachment 53005 --> https://bugs.winehq.org/attachment.cgi?id=53005 stub Does this help? -- 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=39674 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW --- Comment #27 from Austin English <austinenglish(a)gmail.com> --- I can now reproduce, the comments in the bug were quite confusing.. Download 3DMark03 () and install it. Run wine uninstaller, uninstall FutureMark System Info. Download http://www.futuremark.com/downloads/Futuremark_SystemInfo_v428_installer.msi, install Run 3DMark03 now why 3DMark's system info needs bluetooth information is anyone's guess. FYI, The patch has a bug (forgot to update spec file), but after that, it runs into another stub (BluetoothFindRadioClose). Will update when I have more 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=39674 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #53005|0 |1 is obsolete| | --- Comment #28 from Austin English <austinenglish(a)gmail.com> --- Created attachment 53006 --> https://bugs.winehq.org/attachment.cgi?id=53006 stubs (try 2) This fixes the issue for me. You'll then run into bug 25087 -- 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=39674 --- Comment #29 from Sergey Isakov <isakov-sl(a)bk.ru> --- (In reply to Austin English from comment #28)
Created attachment 53006 [details] stubs (try 2)
This fixes the issue for me. You'll then run into bug 25087
Yes, it works! ~~~ fixme:bthpropscpl:BluetoothFindFirstRadio (0xbbf1f0 0xbbf1dc): stub! fixme:bthpropscpl:BluetoothFindRadioClose (0x0): stub! ~~~ -- 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=39674 --- Comment #30 from Sergey Isakov <isakov-sl(a)bk.ru> --- Can be closed fixed. OT. Tested GPU-Z, no crash, no 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=39674 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man(a)post.com --- Comment #31 from super_man(a)post.com --- (In reply to Austin English from comment #28)
Created attachment 53006 [details] stubs (try 2)
This fixes the issue for me. You'll then run into bug 25087
patching file dlls/bthprops.cpl/Makefile.in patch: **** missing line number at line 13: @@ -1, +1,4 @@ ?? Something wrong with the patch? Can confirm the regression. with 1.8 3dmark03 doent 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=39674 --- Comment #32 from Sergey Isakov <isakov-sl(a)bk.ru> --- Resolved by commit 35f9ee3d97ef81397f4e15b0d7ae48fe443023bb ? -- 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=39674 --- Comment #33 from Sergey Isakov <isakov-sl(a)bk.ru> --- No, patch from comment 28 is needed. Why not commit 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=39674 --- Comment #34 from Austin English <austinenglish(a)gmail.com> --- (In reply to Sergey Isakov from comment #33)
No, patch from comment 28 is needed. Why not commit it?
It needs some fixes and cleanup. It's on my to do list after some other patches are committed. -- 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=39674 super_man(a)post.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de -- 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=39674 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Fixed by SHA1| |05edc1bd789ce8a5c6f4c73e21b | |5e3b2d9720dc6 Resolution|--- |FIXED --- Comment #35 from Austin English <austinenglish(a)gmail.com> --- (In reply to Sergey Isakov from comment #29)
(In reply to Austin English from comment #28)
Created attachment 53006 [details] stubs (try 2)
This fixes the issue for me. You'll then run into bug 25087
Yes, it works! ~~~ fixme:bthpropscpl:BluetoothFindFirstRadio (0xbbf1f0 0xbbf1dc): stub! fixme:bthpropscpl:BluetoothFindRadioClose (0x0): stub! ~~~
https://source.winehq.org/git/wine.git/commitdiff/05edc1bd789ce8a5c6f4c73e21... -- 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=39674 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #36 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.9.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.
participants (1)
-
wine-bugs＠winehq.org