http://bugs.winehq.org/show_bug.cgi?id=29384
Bug #: 29384 Summary: Voobly fails to launch Age of Empires II multiplayer game (DirectPlay) Product: Wine Version: 1.3.35 Platform: x86-64 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: lapommegolden@gmail.com Classification: Unclassified
Instead of entering AOE II's brown multiplayer game screen, game will now be automatically aborted & cancelled unrated instead.
http://bugs.winehq.org/show_bug.cgi?id=29384
PommeGolden lapommegolden@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=29384
PommeGolden lapommegolden@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.voobly.com/updat | |es/voobly-v2.1.50.1.exe
http://bugs.winehq.org/show_bug.cgi?id=29384
PommeGolden lapommegolden@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
http://bugs.winehq.org/show_bug.cgi?id=29384
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Voobly fails to launch Age |Voobly fails to launch Age |of Empires II multiplayer |of Empires II multiplayer |game (DirectPlay) |game
--- Comment #1 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-19 10:24:54 CST --- Where is the regression test results? Known working Wine version? Console output?
http://bugs.winehq.org/show_bug.cgi?id=29384
PommeGolden lapommegolden@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.35 |1.3.34
http://bugs.winehq.org/show_bug.cgi?id=29384
PommeGolden lapommegolden@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dmitry@baikal.ru Component|-unknown |ntdll Regression SHA1| |332eee40530f698c74f16d27c98 | |33ccccb25bfa2
--- Comment #2 from PommeGolden lapommegolden@gmail.com 2011-12-22 06:32:44 CST --- Bisect shows:
332eee40530f698c74f16d27c9833ccccb25bfa2 is the first bad commit commit 332eee40530f698c74f16d27c9833ccccb25bfa2 Author: Dmitry Timoshkov dmitry@baikal.ru Date: Fri Dec 16 14:45:23 2011 +0800
ntdll: Replace WRITE by WRITECOPY protection on an image section as Windows does.
:040000 040000 6b4077045c511f828f963770587e2cd937fadf4d 5e0dcc47f88b8c88c55ef98366e51046ced41fcf M dlls
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #3 from PommeGolden lapommegolden@gmail.com 2011-12-22 06:40:08 CST --- Created attachment 38071 --> http://bugs.winehq.org/attachment.cgi?id=38071 wine log 1.3.35
Wine log running 1.3.35
Wine 1.3.34 & before does not have this problem.
You need to install "directplay" (native dlls) from winetricks to get AOE II's multiplayer to work.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #4 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-22 06:45:15 CST --- How can I test it with freely downloadable/demo stuff?
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #5 from PommeGolden lapommegolden@gmail.com 2011-12-22 06:57:48 CST --- (In reply to comment #4)
How can I test it with freely downloadable/demo stuff?
Not sure. Maybe "Age of Empires: Rise of Rome Trial"? I think AOE II trial is not supported by Voobly..
http://www.voobly.com/games/category/6 http://www.microsoft.com/games/aoeexpansion/downloads.htm
You can launch/host a multiplayer game even with only 1 player.
http://bugs.winehq.org/show_bug.cgi?id=29384
PommeGolden lapommegolden@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lapommegolden@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #6 from PommeGolden lapommegolden@gmail.com 2011-12-22 08:20:28 CST --- (In reply to comment #2)
Bisect shows:
332eee40530f698c74f16d27c9833ccccb25bfa2 is the first bad commit commit 332eee40530f698c74f16d27c9833ccccb25bfa2 Author: Dmitry Timoshkov dmitry@baikal.ru Date: Fri Dec 16 14:45:23 2011 +0800
ntdll: Replace WRITE by WRITECOPY protection on an image section as Windowsdoes.
:040000 040000 6b4077045c511f828f963770587e2cd937fadf4d 5e0dcc47f88b8c88c55ef98366e51046ced41fcf M dlls
Reverted the said commit from the latest GIT master does do away the problem:
http://source.winehq.org/git/wine.git/commit/332eee40530f698c74f16d27c9833cc... http://source.winehq.org/git/wine.git/snapshot/27e3e1a89b01bb91480c047cbf95b...
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #7 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-26 02:34:53 CST --- Is this it? http://download.microsoft.com/download/aoeaok/Trial/1.0/WIN98/EN-US/AoE2demo... Does it exhibit the same problem?
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #8 from PommeGolden lapommegolden@gmail.com 2011-12-26 07:29:25 CST --- (In reply to comment #7)
Is this it? http://download.microsoft.com/download/aoeaok/Trial/1.0/WIN98/EN-US/AoE2demo... Does it exhibit the same problem?
I can't seem to be able to even host/join a AOE1 Demo (whether it is with the Rise of Rome expansion or not) game room with free voobly membership (Can't be selected directly from Voobly Game Browser's "Game List" on the right hand side)
So at the moment, I can only confirm the full version of these games are affected by this regression:
- Age of Empires II: Age of Kings - Age of Empires II: The Conquerors
I suppose some other, if not all, games supported by Voobly will probably demonstrate the same problem http://www.voobly.com/welcome/index/games/games_box/All-Games
Voobly's wine AppDB entry: http://appdb.winehq.org/objectManager.php?sClass=application&iId=10361
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #9 from PommeGolden lapommegolden@gmail.com 2011-12-26 07:30:45 CST --- Created attachment 38119 --> http://bugs.winehq.org/attachment.cgi?id=38119 Games that can be launched directly with free Voobly membership
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #10 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-26 08:47:11 CST --- (In reply to comment #9)
Created attachment 38119 [details] Games that can be launched directly with free Voobly membership
Can you please try to figure out which one can be used to replicate the regression?
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #11 from PommeGolden lapommegolden@gmail.com 2011-12-26 21:15:42 CST --- (In reply to comment #10)
(In reply to comment #9)
Created attachment 38119 [details] Games that can be launched directly with free Voobly membership
Can you please try to figure out which one can be used to replicate the regression?
- Age of Empires II: Age of Kings (Full version) - Age of Empires II: The Conquerors (Full version)
I don't have other games, and I don't think the games themselves are the focus of this bug.
I believe something is failing when trying to spawn a new fullscreen window (AOE II's brown multiplayer game screen) which is fixed at 640x480..
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #12 from PommeGolden lapommegolden@gmail.com 2011-12-26 21:19:48 CST --- Created attachment 38127 --> http://bugs.winehq.org/attachment.cgi?id=38127 The expected AOE II brown multiplayer screen (1.3.34 or before, or with the commit reverted)
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #13 from PommeGolden lapommegolden@gmail.com 2011-12-26 21:24:47 CST --- Created attachment 38128 --> http://bugs.winehq.org/attachment.cgi?id=38128 Screenshot showing Voobly having detected AOE II failed to launch after the countdown (1.3.35)
"<Game was not rated - reason: game was not finished>"
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #14 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-26 21:35:21 CST --- (In reply to comment #11)
Can you please try to figure out which one can be used to replicate the regression?
- Age of Empires II: Age of Kings (Full version)
- Age of Empires II: The Conquerors (Full version)
I don't have other games, and I don't think the games themselves are the focus of this bug.
I believe something is failing when trying to spawn a new fullscreen window (AOE II's brown multiplayer game screen) which is fixed at 640x480..
I'm asking because I need something to reproduce and debug the problem. Debugging remotely is hardly possible in this case.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #15 from PommeGolden lapommegolden@gmail.com 2011-12-26 22:04:32 CST --- (In reply to comment #14)
(In reply to comment #11)
Can you please try to figure out which one can be used to replicate the regression?
- Age of Empires II: Age of Kings (Full version)
- Age of Empires II: The Conquerors (Full version)
I don't have other games, and I don't think the games themselves are the focus of this bug.
I believe something is failing when trying to spawn a new fullscreen window (AOE II's brown multiplayer game screen) which is fixed at 640x480..
I'm asking because I need something to reproduce and debug the problem. Debugging remotely is hardly possible in this case.
OK, i seem to have figured out how to fool Voobly into thinking AOE II Trial as the full version.. good enough for testing this bug.... Will post exact steps soon...
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #16 from PommeGolden lapommegolden@gmail.com 2011-12-26 23:57:35 CST --- EXACT STEPS TO INSTALL FAKE AOE II FOR THE PURPOSE OF TESTING THIS REGRESSION: (Good enough for testing this bug. You won't be actually play with other Voobly players with this fake AOE II since you don't have the real game data & have the wrong game version.) ============================
1. Download & install AOE II Trial: - http://download.microsoft.com/download/aoeaok/Trial/1.0/WIN98/EN-US/AoE2demo... OR - http://download.cnet.com/Age-of-Empires-II-Trial-Version/3000-2099_4-1072553...
2. Launch AOE II Trial (/drive_c/Program Files/Microsoft Games/Age of Empires II Trial/EMPIRES2.exe) & ACCEPT to the EULA (needed to create those registry keys needed later). Close AOE II Trial.
You may need to change DirectDrawRenderer to gdi if opengl renderer fails for some reason on some platforms (which is another bug)... http://wiki.winehq.org/UsefulRegistryKeys
3. Download & install Voobly: http://www.voobly.com/updates/voobly-v2.1.50.1.exe 4. Install "Directplay" (native DLL overrides) from winetricks to get AOE2's multiplayer to work 5. (Optional) Install "ie6" from winetricks to get Voobly's embedded internet browser to work
6. Modify AOE II Trial's registry version number from "2.0" to "2.0a"
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Age of Empires II Trial] "Version"="2.0a" [HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Age of Empires\2.0] "Version"="2.0a" [HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Games\Age of Empires II Trial] "Version"="2.0a"
7. Launch & login into Voobly (Requries free Voobly membership) (/drive_c/Program Files/Voobly/voobly.exe)
8. Double click the following game lounge from Voobly's "Game List" on Voobly's "Game Browser"'s right hand side - Age of Empires II: Age of Kings - CS/DM/RM (XX/XXX)
Voobly will now try to establish connection to the "lounge". This may take 2-3 seconds to a minute if Voobly's server is slow (not Wine problem).
9. Voobly will now download its needed updates. Just install all those updates when prompted. 10. Completely close (including Wine System Tray) & restart Voobly after installing those updates. Ignore all those error messages. 11. Press YES to run the "Game diagonostics tool" when Voobly's "Game Detection Error" message pops up 12. Press BEGIN SCAN 13. Press OK, and then press APPPLY FIX 14. Locate AOE II's EXE when Voobly complains it can't find the EXE (/drive_c/Program Files/Microsoft Games/Age of Empires II Trial/EMPIRES2.exe) 15. Press BEGIN SCAN 16. "Game Diagnostics" will display something like this if you follow the steps correctly. Redo Step 6 if the game version number is still wrong.
"Updating SOFTWARE\Microsoft\DirectPlay\Applications\Age of Empires II CommandLine => lobby CurrentDirectory => c:\program files\microsoft games\age of empires ii trial File => Empires2.ICD Guid => {FB69A260-5031-11d3-A2D4-006097BA6550} Launcher => Empires2.Exe Path => c:\program files\microsoft games\age of empires ii trial Fix was applied successfully!"
17. Completely close (including Wine System Tray) & restart Voobly.
18. Launch & login into Voobly. Double click the following game lounge from Voobly's "Game List" on Voobly's "Game Browser"'s right hand side
Age of Empires II: Age of Kings - CS/DM/RM (XX/XXX)
19. Try to host a game by pressing "Quick Host" on the top "toolbar" (the third button) 20. Press the LAUNCH button (green) on the left (next to Settings) 21. The 6-second Launch countdown will now begins. 22. Press YES when "Unsecure Game Installation" message pops up (Voobly's anti-cheat function). 23. Voobly will now try to launch AOE II, Wine will try to spawn another fullscreen window, & enter AOE II's brown multiplayer screen (which is broken in Wine 1.3.35 & the focus of this bug)
- Wine 1.3.33 & before: You should be able to enter AOE II's brown multiplayer screen even with this fake AOE II full version (see attachment: http://bugs.winehq.org/attachment.cgi?id=38127) - Wine 1.3.34: AOE II will now crash shortly after entering fullscreen if your DirectDrawRenderer is set to gdi (gdi regression which has already been fixed in 1.3.35) - In Wine 1.3.35, nothing will really happen after the countdown.
24. In Wine 1.3.35, after detecting AOE II failed to launch (around 10 seconds after the launch countdown ends), Voobly will display the following message depending on your game settings (regardless when you have the real AOE II full version or not) <Game was not rated - reason: ratings were turned off> OR <Game was not rated - reason: game was not finished>
http://bugs.winehq.org/show_bug.cgi?id=29384
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #17 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-28 01:08:36 CST --- Many thanks for your efforts, now I'm able to reproduce the problem.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #18 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-29 02:49:37 CST --- Created attachment 38156 --> http://bugs.winehq.org/attachment.cgi?id=38156 Hack to make Voobly work
It looks like Voobly checks the old protection returned by VirtualProtect and refuses to run if the protection is PAGE_EXECUTE_WRITECOPY instead of PAGE_EXECUTE_READWRITE. This behaviour corresponds to a todo_wine test in kernel32/tests/loader.c and kernel32/tests/virtual.c where Windows changes the WRITECOPY to READWRITE protection when it detects a page write.
Unfortunately Wine is not an OS, and I don't know a proper way to fix this.
I'm attaching a hack which makes Voobly work, but that's just a hack.
http://bugs.winehq.org/show_bug.cgi?id=29384
VooblyAgeonMac rdomingor@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rdomingor@hotmail.com
--- Comment #19 from VooblyAgeonMac rdomingor@hotmail.com 2012-11-20 16:48:02 CST --- Hi! Good afternoon!
I have a mac computer and the same problem with voobly and age of empires the conquerors
I have installed the age of empires II gold edition with conquerors I have installed the patch 1.0c after this, I was installing the voobly, and this open perfectly, and can make a room or join to others room
the problem is when I try to launch the voobly make the countdown 6...4...2..and after show the message of starting...but the game can't open...the voobly only show the message of "Game was not rated Reason: ratings were turned off" or "Game was not rated Reason: game was not finished"
I was reading about the anti-hack system, and I read your explanation about how to launch..and your hack, but im new in wine, but I don't know where I must put your hack or what i need to do to make work voobly with age.
Please, can you help me? I love the age of empires II and I have weeks reading and searching in google, bing, yahoo, many post and nothing to play with voobly, then I found this post and your holy and blessed solution, but I dont know what do with your http://bugs.winehq.org/attachment.cgi?id=38156 atachment, I need to save like a file and put in some folder? or i need to copy the code and paste inside a file?
please, can you help me with this? Thanks for read my long petition
http://bugs.winehq.org/show_bug.cgi?id=29384
Brandon Corujo haku08879@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |haku08879@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=29384
JT jmorris237@my.stlcc.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jmorris237@my.stlcc.edu
--- Comment #20 from JT jmorris237@my.stlcc.edu 2013-08-11 16:30:48 CDT --- hello. the patch given here wont apply to current versions of wine tested wine1.6 it gives hunk failed error when trying to apply the patch. i am also in touch with the devs of voobly to try and address the issue outlined in this topic.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #21 from Dmitry Timoshkov dmitry@baikal.ru 2013-08-12 22:22:54 CDT --- (In reply to comment #20)
hello. the patch given here wont apply to current versions of wine tested wine1.6 it gives hunk failed error when trying to apply the patch. i am also in touch with the devs of voobly to try and address the issue outlined in this topic.
The chunk of the being changed code in the hack attached to this bug is identical to current Wine, it shouldn't be too hard to make the changes manually if really desired.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #22 from JT jmorris237@my.stlcc.edu 2013-08-13 12:23:43 CDT --- whatever we could do to make this work again would be much appreciated.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #23 from JT jmorris237@my.stlcc.edu 2013-08-13 16:57:32 CDT --- i am not the best with wine/linux so i am not sure what i need to do
http://bugs.winehq.org/show_bug.cgi?id=29384
Ryan yash94d@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yash94d@gmail.com
--- Comment #24 from Ryan yash94d@gmail.com 2013-08-24 11:52:23 CDT --- hello, i have wine installed (1.6) but encountering the same error. voobly fails to launch the game any fix?
http://bugs.winehq.org/show_bug.cgi?id=29384
oiaohm oiaohm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |oiaohm@gmail.com
--- Comment #25 from oiaohm oiaohm@gmail.com 2013-10-16 20:45:34 CDT --- http://appdb.winehq.org/objectManager.php?sClass=application&iId=10361
Please Voobly users do update the Appdb page/pages. No one has submitted that the hack exists or even associated this bug on the appdb page. It would be useful to know what versions of wine the Voobly hack works with. Just in case there is now other bugs.
Yes "Show Apps affected by this bug" is Zero. Really it should be at least 2.
This is not my or the developers responsibility I don't use Voobly for 1. Developers should be able to click Show Apps and have a list to test their patches with "Show Apps affected by this bug".
I really wonder if policy should be made that bug will not be worked on unless it is associated with at least 1 application and if its not associated with one application closed not associated with application. Then maybe people submitting bug reports would wake up that its critical.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #26 from Austin English austinenglish@gmail.com 2013-10-16 20:50:26 CDT --- (In reply to comment #25)
I really wonder if policy should be made that bug will not be worked on unless it is associated with at least 1 application and if its not associated with one application closed not associated with application. Then maybe people submitting bug reports would wake up that its critical.
There is no 'policy' on what bugs are worked on. Contributors are volunteers, free to work on whatever interests them.
http://bugs.winehq.org/show_bug.cgi?id=29384
kevinkore3@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kevinkore3@yahoo.com
--- Comment #27 from kevinkore3@yahoo.com 2013-10-25 20:51:03 CDT --- Could somebody please give instructions to make voobly age of empires 2 multiplayer work that a noob can understand? Thanks :)
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #28 from kevinkore3@yahoo.com 2013-10-25 20:51:20 CDT --- Could somebody please give instructions to make voobly age of empires 2 multiplayer work that a noob can understand? Thanks :)
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #29 from JT jmorris237@my.stlcc.edu 2013-10-28 11:37:18 CDT --- (In reply to comment #25)
http://appdb.winehq.org/objectManager.php?sClass=application&iId=10361
Please Voobly users do update the Appdb page/pages. No one has submitted that the hack exists or even associated this bug on the appdb page. It would be useful to know what versions of wine the Voobly hack works with. Just in case there is now other bugs.
Yes "Show Apps affected by this bug" is Zero. Really it should be at least 2.
This is not my or the developers responsibility I don't use Voobly for 1. Developers should be able to click Show Apps and have a list to test their patches with "Show Apps affected by this bug".
I really wonder if policy should be made that bug will not be worked on unless it is associated with at least 1 application and if its not associated with one application closed not associated with application. Then maybe people submitting bug reports would wake up that its critical.
doesnt help when they REJECT the applications
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #30 from JT jmorris237@my.stlcc.edu 2013-10-28 13:27:37 CDT --- just to to update this:
whenever trying to launch aoc on voobly we are now getting the following error:
The Program AGE2_X1.ICD has encountered a serious problem and needs to close.
Details:
Unhandled exception: illegal instruction in 32-bit code (0x00616ae3). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00616ae3 ESP:0033fe84 EBP:7bc5076a EFLAGS:00010217( R- -- I -A-P-C) EAX:7ffdf000 EBX:7ffdf000 ECX:7b8604ab EDX:0033feb8 ESI:7ffdf000 EDI:7b85f22c Stack dump: 0x0033fe84: 00616ae1 00000000 00000000 00000000 0x0033fe94: 00000000 00000000 00000000 00000000 0x0033fea4: 00000000 0033fed0 7bcbdff4 fff6b494 0x0033feb4: 00110ab8 0033fed8 7bc791c0 00000000 0x0033fec4: 00000000 00000000 7bc791c0 7ffdf000 0x0033fed4: 7bcbdff4 0033ffa8 7bc7c1cd 7b860440 Backtrace: =>0 0x00616ae3 in age2_x1.icd (+0x216ae3) (0x7bc5076a) 1 0xe4830006 (0xd88ac381) 0x00616ae3: popl %esi Modules: Module Address Debug info Name (80 modules) PE 400000- 7a4000 Export age2_x1.icd ELF 7b800000-7ba5b000 Deferred kernel32<elf> -PE 7b810000-7ba5b000 \ kernel32 ELF 7bc00000-7bcda000 Deferred ntdll<elf> -PE 7bc10000-7bcda000 \ ntdll ELF 7bf00000-7bf04000 Deferred <wine-loader> ELF 7dd07000-7dd3d000 Deferred uxtheme<elf> -PE 7dd10000-7dd3d000 \ uxtheme ELF 7dd3d000-7dd44000 Deferred libxfixes.so.3 ELF 7dd44000-7dd4f000 Deferred libxcursor.so.1 ELF 7dd4f000-7dd5f000 Deferred libxi.so.6 ELF 7dd5f000-7dd63000 Deferred libxcomposite.so.1 ELF 7dd63000-7dd6e000 Deferred libxrandr.so.2 ELF 7dd6e000-7dd78000 Deferred libxrender.so.1 ELF 7dd78000-7dd7e000 Deferred libxxf86vm.so.1 ELF 7dd7e000-7dd82000 Deferred libxinerama.so.1 ELF 7dd82000-7dd89000 Deferred libxdmcp.so.6 ELF 7dd89000-7dd8d000 Deferred libxau.so.6 ELF 7dd8d000-7ddaf000 Deferred libxcb.so.1 ELF 7ddaf000-7ddb5000 Deferred libuuid.so.1 ELF 7ddb5000-7ddcf000 Deferred libice.so.6 ELF 7ddcf000-7df06000 Deferred libx11.so.6 ELF 7df06000-7df18000 Deferred libxext.so.6 ELF 7df18000-7df21000 Deferred libsm.so.6 ELF 7df39000-7dfcb000 Deferred winex11<elf> -PE 7df40000-7dfcb000 \ winex11 ELF 7e02d000-7e055000 Deferred libexpat.so.1 ELF 7e055000-7e08e000 Deferred libfontconfig.so.1 ELF 7e08e000-7e0a7000 Deferred libz.so.1 ELF 7e0a7000-7e142000 Deferred libfreetype.so.6 ELF 7e142000-7e168000 Deferred iphlpapi<elf> -PE 7e150000-7e168000 \ iphlpapi ELF 7e168000-7e19e000 Deferred ws2_32<elf> -PE 7e170000-7e19e000 \ ws2_32 ELF 7e19e000-7e1ba000 Deferred wsock32<elf> -PE 7e1a0000-7e1ba000 \ wsock32 ELF 7e1ba000-7e1de000 Deferred imm32<elf> -PE 7e1c0000-7e1de000 \ imm32 ELF 7e1de000-7e2ec000 Deferred opengl32<elf> -PE 7e200000-7e2ec000 \ opengl32 ELF 7e2ec000-7e42d000 Deferred wined3d<elf> -PE 7e300000-7e42d000 \ wined3d ELF 7e42d000-7e4a2000 Deferred ddraw<elf> -PE 7e430000-7e4a2000 \ ddraw ELF 7e4a2000-7e4ea000 Deferred dsound<elf> -PE 7e4b0000-7e4ea000 \ dsound ELF 7e4ea000-7e52e000 Deferred dplayx<elf> -PE 7e4f0000-7e52e000 \ dplayx ELF 7e52e000-7e636000 Deferred comctl32<elf> -PE 7e540000-7e636000 \ comctl32 ELF 7e636000-7e661000 Deferred msacm32<elf> -PE 7e640000-7e661000 \ msacm32 ELF 7e661000-7e6e2000 Deferred rpcrt4<elf> -PE 7e670000-7e6e2000 \ rpcrt4 ELF 7e6e2000-7e81e000 Deferred ole32<elf> -PE 7e700000-7e81e000 \ ole32 ELF 7e81e000-7e88d000 Deferred advapi32<elf> -PE 7e830000-7e88d000 \ advapi32 ELF 7e88d000-7e9ab000 Deferred gdi32<elf> -PE 7e8a0000-7e9ab000 \ gdi32 ELF 7e9ab000-7eb06000 Deferred user32<elf> -PE 7e9c0000-7eb06000 \ user32 ELF 7eb06000-7ebc0000 Deferred winmm<elf> -PE 7eb10000-7ebc0000 \ winmm ELF 7ebc0000-7ebec000 Deferred msvfw32<elf> -PE 7ebd0000-7ebec000 \ msvfw32 ELF 7ebec000-7ec06000 Deferred version<elf> -PE 7ebf0000-7ec06000 \ version ELF 7ec06000-7ec13000 Deferred libnss_files.so.2 ELF 7ec13000-7ec2c000 Deferred libnsl.so.1 ELF 7efb4000-7eff7000 Deferred libm.so.6 ELF 7eff7000-7f000000 Deferred librt.so.1 ELF f7372000-f7525000 Deferred libc.so.6 ELF f7525000-f752a000 Deferred libdl.so.2 ELF f752b000-f7546000 Deferred libpthread.so.0 ELF f7548000-f7554000 Deferred libnss_nis.so.2 ELF f7554000-f755d000 Deferred libnss_compat.so.2 ELF f755e000-f7714000 Dwarf libwine.so.1 ELF f7716000-f7738000 Deferred ld-linux.so.2 ELF f7738000-f7739000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 0000000e services.exe 00000024 0 00000023 0 0000001c 0 00000010 0 0000000f 0 0000001a winedevice.exe 00000022 0 0000001f 0 0000001e 0 0000001b 0 00000020 plugplay.exe 00000026 0 00000025 0 00000021 0 00000027 explorer.exe 00000029 0 00000028 0 0000004f voobly.exe 00000067 0 0000002e 0 00000045 0 00000044 0 00000011 0 0000004b 0 00000048 0 00000031 0 0000004a 0 00000035 0 0000002c 0 0000002a 0 00000013 0 00000019 15 00000043 0 00000061 0 00000060 0 0000005f 0 0000005e 0 0000005d 0 0000005c -1 0000005b 0 0000005a 0 00000059 0 00000058 0 00000057 0 00000056 0 00000055 0 00000054 0 00000053 0 00000052 0 00000051 0 00000050 0 00000062 (D) C:\Program Files (x86)\Microsoft Games\Age of Empires II\age2_x1\AGE2_X1.ICD 0000003d 0 <== System information: Wine build: wine-1.6 Platform: i386 (WOW64) Host system: Linux Host version: 3.8.0-31-generic
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #31 from oiaohm oiaohm@gmail.com 2013-10-28 21:15:30 CDT --- Austin English --There is no 'policy' on what bugs are worked on. Contributors are volunteers, free to work on whatever interests them.--
And how will the new volunteers find there way to the bug if it not associated with the effected application. The answer is they don't easily.
Basically you have a person who is interested in X game/program where should they get a easy list of the open issues they may wish to work on. The appdb of course. Guess what is the problem here. Not associated no list for them.
This is why I say consider policy on this. By being policy it will get done.
I am not saying volunteers are not free to work on what interests them. I am just saying working on not associated is should basically be forbin. Simple fix associate application then you can work on it. Being associated might find a developer better suited to fix the problem as well.
JT --doesnt help when they REJECT the applications-- There has not been a comment in the http://forum.winehq.org about this. Or a bug in the bugzilla linked to the appdb. The forum moderator does have appdb approval rights. General issues the forum exists to sort out. Yes failing to create bug or appdb entries is general issues.
This is why I am so much for getting strict about this. I am guessing there are other problems and people are just not speaking up.
Issues cannot be fixed if everyone keeps on disregarding the problem. Another reason why bugzilla may be needed to be strict.
Not associated also makes my life hard doing support. New users have gone to the appdb and don't find out about the solutions either.
Yes I am sounding annoyed because this does annoy me and I want to know what is going wrong. I should not have be here yelling.
JT by your comment I should have heard from you in the forum or irc. Basically don't sweep problems under carpet. Sooner or latter someone looks under carpet and is pissed off.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #32 from kevinkore3@yahoo.com 2013-10-29 23:21:45 CDT --- I am new to WINE, so some part of my statement is probably flawed, but if the forum moderator does have control over the AppDB and the forums, and he doesn't like an app for whatever reason and won't approve it for whatever reason, then he isn't going to allow a complaint about him not accepting the app on the forum because posts need approval. Basically, he controls the AppDB and forums, so if you have a problem in the AppDB because your app won't get accepted he isn't going to help you out on the forums because he knows that it will probably turn out into nothing out for him. If we had a separate moderator for the AppDB and the forums, then our complaints would have a much better chance of being heard. I have submitted a new version of Voobly and it has not been accepted. It is mathematically quite unlikely that all these users have, for some reason, decided to not submit anything about Voobly, which they are spending so much time working on. It is much more likely that the moderator has a grudge on Voobly and will not accept new versions. Maybe he owns GameRanger or something, I wouldn't know, but he won't accept new versions of Voobly or complaints.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #33 from oiaohm oiaohm@gmail.com 2013-10-30 01:12:10 CDT --- kevinkore3 --I am new to WINE, so some part of my statement is probably flawed, but if the forum moderator does have control over the AppDB and the forums, and he doesn't like an app for whatever reason and won't approve it for whatever reason, then he isn't going to allow a complaint about him not accepting the app on the forum because posts need approval.-- Moderator of the forum is only 1 of the moderators of the appdb. Moderator of the forums and appdb can in fact approve something one of the other appdb moderators has rejected.
The moderator of the forum in fact has limitations. The moderator of the forum cannot delete posts. Lock but cannot delete. To delete this has to be approved by the website admin. It could be as simple as the fact that some information in the new entry is wrong.
No one has asked the question. If they had asked the question it would be in the forum record for everyone to see.
Now if the moderator does something stupid there is the wine-users mailing list.
http://www.winehq.org/mailman/listinfo/wine-users
Like how do we as a group find out that a moderator is doing the wrong thing if no one complains.
Yes the moderator of the forum if he likes it or not has to accept complaints and issues about appdb. This is the way the system is set up.
Maybe we need to update the appdb somehow to make this clear.
Posts on the forum require login yes. Interesting enough moderator of forum cannot delete you account either. Yes he can report you for review of account but then questions about why will happen.
kevinkore3 the systems in place a very solid. The thing is they have to be used.
Basically I want to know if it is a grudge by some maintainer on the appdb. If so they go by by. But todo this I need users to speak up and tell us what they have done.
Basically if your appdb stuff is not going through in 48 hours you should be complaining in the forum or wine-users mailing list. To find out what is wrong.
http://appdb.winehq.org/objectManager.php?sClass=application&iId=10361
Notice this application has no application level maintainers. No one has stepped up for roll. So its possible the reports are stuck in backlog.
kevinkore3 basically something is going wrong here and it need to be fixed yesterday. All the systems are in place to counter all the faults you have raised. But those systems can only work if users use them.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #34 from kevinkore3@yahoo.com 2013-10-30 20:08:45 CDT --- OK so they did accept it, but it probably took over 48 hours, maybe 1/2 a week. Thanks for the advice though anyway.
http://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #35 from JT jmorris237@my.stlcc.edu 2013-10-31 09:20:25 CDT --- i was accepted as a maintainer for voobly and have made a few updates. i have associated this bug with voobly so the appdb should be updated now.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #36 from JT jmorris237@my.stlcc.edu --- this is still not working with the newest version of wine. we did however get it to work with playonlinux using wine 1.3.34 we would still like to get this working with the newest version.
https://bugs.winehq.org/show_bug.cgi?id=29384
K1773R K1773R@darkgamex.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |K1773R@darkgamex.ch
https://bugs.winehq.org/show_bug.cgi?id=29384
Michael Müller michael@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |michael@fds-team.de
--- Comment #37 from Michael Müller michael@fds-team.de --- Created attachment 49657 --> https://bugs.winehq.org/attachment.cgi?id=49657 ntdll: Change WRITECOPY memory protection to WRITE on first write access
Hi,
I wrote a patch which correctly changes the WRITECOPY memory protection to WRITE when the first write occurs on a page. To achieve this every page with WRITECOPY protection does not really gain write permission, so that a segfault occurs on the first write access. The signal handler will now detect this case, change the protection to WRITE and will continue the execution of the program. This fixes Voobly and the according wine tests which were marked as todo.
The only downside of this patch is that Wine installs the signal handler quite late as it expects a connection to the wine server. This is not sufficient for our case since Wine also uses WRITECOPY for it's internal dlls leading to a crash. In order to overcome this problem, I setup a temporarily signal handler when Wine is done with setting up the virtual memory management. Currently the patch only contains such a signal handler for i386 so that this patch will only affect 32 bit software.
Regards, Michael
https://bugs.winehq.org/show_bug.cgi?id=29384
Luke Bratch l_bratch@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |l_bratch@yahoo.co.uk
https://bugs.winehq.org/show_bug.cgi?id=29384
mikachu@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mikachu@gmail.com
--- Comment #38 from mikachu@gmail.com --- (In reply to Michael Müller from comment #37)
Created attachment 49657 [details] ntdll: Change WRITECOPY memory protection to WRITE on first write access
Hi,
I wrote a patch which correctly changes the WRITECOPY memory protection to WRITE when the first write occurs on a page.
If this is the same patch as is included in the compholio patchset (which it appears to be by visual inspection), it breaks steam startup. Sometimes it simply doesn't start, sometimes it does this forever,
err:ntdll:RtlpWaitForCriticalSection section 0x7bcd2ea0 "wine-1.7.27-r1/work/wine-1.7.27/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0058, blocked by 0043, retrying (60 sec)
with one of these repeated every minute.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #39 from Michael Müller michael@fds-team.de --- Hi,
thanks for pointing out this issue. I was able to track down the problem and fix it.
The problem was caused by the way how the unloading of builtin dlls is handled. In order to emulate the WRITECOPY protection correctly, we need remove the WRITE permission from the page and change the protection flags when we get an exception for an invalid write operation on such a page. In order to accomplish this, we have to get the current protection flags from Wines virtual memory management. This is usually no problem, since the required information is set when a page is allocated and will only be removed if a page is freed.
However, there is one exception: builtin dlls. Wine does not allocate the memory using its own memory functions, but uses dlopen / dlcose to take care of this. In order to provide the usual memory functions for these memory areas, Wine still keeps track of stuff like memory protection flags, but the deallocation of the memory is detached from the usual memory functions. For some reason Wine deleted the required memory management information _before_ unloading the builtin dll using dlclose. The destructor of the dll now tried to write to a WRITECOPY page (which was/is part of the dll), but the exception handler was unable to determine the protection flags of the page and thinks it is just a usual page fault and crashes.
In order to solve this problem, I simply swapped the order of deleting the memory management information and unloading the dll using dlclose. Now Steam runs without problems. Moreover I fixed a possible multithreading issue. The updated patch is available at:
https://github.com/compholio/wine-compholio/tree/master/patches/ntdll-WRITEC...
https://bugs.winehq.org/show_bug.cgi?id=29384
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #40 from Michael Müller michael@fds-team.de --- Hi,
my patch revealed some other bugs in Wine. In some places the memory is directly passed to syscalls resulting in an EFAULT error instead of an exception causing Wine to crash. This is not introduced by my patch but also happens using the PAGE_GUARD protection and the GetTokenInformation function. I can provide some test code if someone is interested, but Sebastian Lackner will send some patches to wine-devel to fix the known problems.
However, there might be still more places in Wine which could be affected by this bug, so we decided to change the patch to require the environmental variable COMPHOLIO_WRITECOPY to be set to 1 in order to enable my changes. We are going to remove this again after we are sure that it will not break further applications.
Regards, Michael
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #41 from JT jmorris237@my.stlcc.edu --- does this mean there would be some patches in the next version of wine?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #42 from Sebastian Lackner sebastian@fds-team.de --- @JT: As the patch requires some significant changes in all parts of Wine, it is unlikely that this fix will be already included in the next Wine version. If you want to test it, you can use the Wine-Compholio staging tree builds:
https://github.com/compholio/wine-compholio https://github.com/compholio/wine-compholio/wiki/Installation
Don't forget to run /opt/wine-compholio/bin/wine instead of "wine" after installing, and set the environment variable before running Voobly.
export COMPHOLIO_WRITECOPY=1 cd /path/to/the/program /opt/wine-compholio/bin/wine program.exe
What the next wine version most likely will include is the first set of patches, to fix unrelated issues, which were discovered by adding this patchset. Those issues are all completely unrelated, but are much more difficult to reproduce without the patchset, and noone noticed them yet.
[1/4] http://source.winehq.org/patches/data/106864 [2/4] http://source.winehq.org/patches/data/106865 [3/4] http://source.winehq.org/patches/data/106866 [4/4] http://source.winehq.org/patches/data/106867
At all other people affected by this problem: Please do us a favor and test the patchset (with COMPHOLIO_WRITECOPY=1) with all other Wine programs you have installed - if you notice additional regressions introduced by this patchset, please report them to us, so we can fix those unrelated issues, and hopefully will be able to get the main patchset upstream soon.
Regards, Sebastian
https://bugs.winehq.org/show_bug.cgi?id=29384
Richard Molitor richmolitor@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |richmolitor@aol.com
--- Comment #43 from Richard Molitor richmolitor@aol.com --- Hi, I installed the wine-compholio on Arch (64bit). Singleplayer works fine (performance is a lot better than with wine 1.7)
I have the same problem when launching a Game on voobly, though: It just crashes out and returns to the voobly lobby, even when I run it with COMPHOLIO_WRITECOPY=1 set in the shell.
The console output at the time of the crash is: fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
I did install the "directplay" library using winetricks for the system wine (1.7). Can wine-staging use the same one, or do I need to install it separately again?
Are there any further steps required for 64bit that I missed?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #44 from Richard Molitor richmolitor@aol.com --- Hi again, going trough the code at [1] I found that the name of the environment variable was changed.
When using export STAGING_WRITECOPY=1
Everything works like a charm for me. Thanks a lot for this patch! :-)
[1] https://github.com/wine-compholio/wine-staging/blob/master/patches/ntdll-WRI...
https://bugs.winehq.org/show_bug.cgi?id=29384
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
https://bugs.winehq.org/show_bug.cgi?id=29384
Michael Müller michael@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |STAGED Staged patchset| |https://github.com/wine-com | |pholio/wine-staging/tree/ma | |ster/patches/ntdll-WRITECOP | |Y
https://bugs.winehq.org/show_bug.cgi?id=29384
ipenguin67@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ipenguin67@yahoo.com
--- Comment #45 from ipenguin67@yahoo.com --- Has this fix been implemented as of the latest release (1.9.6) or does it still need to be manually applied? I'm still running into the "<Game was not rated - reason: game was not finished>" issue, but with SWGB.
https://bugs.winehq.org/show_bug.cgi?id=29384
afarah@inf.ufrgs.br changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |afarah@inf.ufrgs.br
--- Comment #46 from afarah@inf.ufrgs.br --- Exporting STAGING_WRITECOPY=1 used to work as of 1.6.2. I'm using Wine 1.9.24 and this is not working anymore - I'm getting the same errors as the others (Game doesn't launch). COMPHOLIO_WRITECOPY=1 didn't work either.
I tried launching the game using the native launcher instead of Voobly and it loads the menus, but when one tries to start a game it does not start.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #47 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to afarah from comment #46)
Exporting STAGING_WRITECOPY=1 used to work as of 1.6.2. I'm using Wine 1.9.24 and this is not working anymore - I'm getting the same errors as the others (Game doesn't launch). COMPHOLIO_WRITECOPY=1 didn't work either.
That's because the patch is still only in staging and Wine staging 1.9.24 never happened. Try with staging 2.0-rc1.
https://bugs.winehq.org/show_bug.cgi?id=29384
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Staged patchset|https://github.com/wine-com |https://github.com/wine-sta |pholio/wine-staging/tree/ma |ging/wine-staging/tree/mast |ster/patches/ntdll-WRITECOP |er/patches/ntdll-WRITECOPY |Y | Summary|Voobly fails to launch Age |Multiple applications |of Empires II multiplayer |expect correct handling of |game |WRITECOPY memory protection | |(Voobly fails to launch Age | |of Empires II, MSYS2)
--- Comment #48 from Anastasius Focht focht@gmx.net --- Hello folks,
likely still present, updating fields.
Refining summary to be more generic to avoid bug 35561 being a duplicate (rechristened for different issue).
Regards
https://bugs.winehq.org/show_bug.cgi?id=29384
zzzzzyzz@hacari.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz@hacari.org
https://bugs.winehq.org/show_bug.cgi?id=29384
Andrey andrey.gursky@e-mail.ua changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrey.gursky@e-mail.ua
https://bugs.winehq.org/show_bug.cgi?id=29384
alasky@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alasky@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=29384
MS wallvan@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wallvan@hotmail.com
--- Comment #49 from MS wallvan@hotmail.com --- Finally ! I solved icd error ! I used wine 5.1 staging with play on mac 2. You need to install play on mac 2 app then click settings go to click the wine button then click setup wine make sure selected windows 10 then you will see general settings button which is left side of ''wine'' button click this and make sure to select wine 5.1 staging or higher. well, go to wine button again and click control panel click program add/remove icon then click installl from cd rom button (install) If you have .iso file you can use this or use your cd rom. Make ''clean'' setup for age of empires and the conquerors then make the same again for voobly.exe program (you can download client from voobly.com) wine---control panel----program add/remove icon-----click install-----voobly.exe(setup voobly)
all done ! voobly will find true dll files or patches for you, voobly will make restart 2-3 times, follow the voobly's instructions then restart voobly again and restart the windows on play on mac 2 (setting----wine button----restart windows)
you can test with 1 player go host on voobly then start the game If you will see brown screen you done it ! You able to play multiplayer or watching recording game on voobly.
Probably you can get this error:
1. dpwsockx.dll or dplayx.dll not founded: You need to ''clean'' setup and make sure voobly found the age2_x1.exe in the ''true'' setup folder location (c:programfiles/microsofrt games/age of empires II/age2_x1)
2. you can get age2_x1.icd serious error If you do ''clean'' setup with cd rom or .iso file, you will solve it. You need to use program add/remove icon on play on mac 2 If you do that manually, maybe regedit files won't fixed so you get the icd error again.
If you have different problem or you can't solved, so join the forum and hit this topic up !
I'm ready !
Thanks !
https://bugs.winehq.org/show_bug.cgi?id=29384
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.voobly.com/updat |https://web.archive.org/web |es/voobly-v2.1.50.1.exe |/20111009064045/http://www. | |voobly.com/updates/voobly-v | |2.1.50.1.exe
--- Comment #50 from Anastasius Focht focht@gmx.net --- Hello folks,
adding stable download link via Internet Archive for documentation.
https://web.archive.org/web/20111009064045/http://www.voobly.com/updates/voo...
https://www.virustotal.com/gui/file/ffb6cf32f31a6a662e54ac41c46796a52e67c2d8...
$ sha1sum voobly-v2.1.50.1.exe 814eabbced72c3c9198c78cb169bed0b948acf31 voobly-v2.1.50.1.exe
$ du -sh voobly-v2.1.50.1.exe 8.9M voobly-v2.1.50.1.exe
$ wine --version wine-7.0-rc5
Regards
https://bugs.winehq.org/show_bug.cgi?id=29384
Joel Holdsworth joel@airwebreathe.org.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joel@airwebreathe.org.uk
https://bugs.winehq.org/show_bug.cgi?id=29384
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |398063392@qq.com
--- Comment #51 from Fabian Maurer dark.shadow4@web.de --- *** Bug 53835 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=29384
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |other@jan-feld.de
--- Comment #52 from Fabian Maurer dark.shadow4@web.de --- *** Bug 46374 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=29384
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #53 from Fabian Maurer dark.shadow4@web.de --- I tested the cef sample before cef had their wine workaround for this comitted: https://cef-builds.spotifycdn.com/index.html#windows64:109.1.16 (Sample Application)
I tried wine-staging-8.19 with "STAGING_WRITECOPY=1 wine cefclient" but it still crashes. Is patchset incomplete? I bisected chromium/cef and the commit that makes it work under wine is this: https://github.com/v8/v8/commit/1bc56d2843b22414d13f93ca11ce656b055baaf3 So, STAGING_WRITECOPY=1 should help, no?
Btw, starting with STAGING_WRITECOPY=1 is extremely slow, even just "winecfg". It used to be better.
https://bugs.winehq.org/show_bug.cgi?id=29384
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #54 from Zeb Figura z.figura12@gmail.com --- (In reply to Fabian Maurer from comment #53)
I tested the cef sample before cef had their wine workaround for this comitted: https://cef-builds.spotifycdn.com/index.html#windows64:109.1.16 (Sample Application)
I tried wine-staging-8.19 with "STAGING_WRITECOPY=1 wine cefclient" but it still crashes. Is patchset incomplete? I bisected chromium/cef and the commit that makes it work under wine is this: https://github.com/v8/v8/commit/1bc56d2843b22414d13f93ca11ce656b055baaf3 So, STAGING_WRITECOPY=1 should help, no?
Btw, starting with STAGING_WRITECOPY=1 is extremely slow, even just "winecfg". It used to be better.
It may have broken at some point in the past few years.
https://bugs.winehq.org/show_bug.cgi?id=29384
Ker noa blue-t@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t@web.de
https://bugs.winehq.org/show_bug.cgi?id=29384
Liz Fong-Jones elizabeth@ctyalcove.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |elizabeth@ctyalcove.org
https://bugs.winehq.org/show_bug.cgi?id=29384
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |naworldw@gmail.com
--- Comment #55 from Fabian Maurer dark.shadow4@web.de --- *** Bug 56057 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #56 from Fabian Maurer dark.shadow4@web.de --- Created attachment 75727 --> https://bugs.winehq.org/attachment.cgi?id=75727 Basic hack that helps for chromium issues
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #57 from Ker noa blue-t@web.de --- Wine-Staging has https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-WRITE... , where is the difference of the larger patch there and your hack?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #58 from Fabian Maurer dark.shadow4@web.de ---
Wine-Staging has https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll- WRITECOPY , where is the difference of the larger patch there and your hack?
See my previous comments, the staging hack has issues and doesn't work for me.
https://bugs.winehq.org/show_bug.cgi?id=29384
zurohki@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zurohki@gmail.com
--- Comment #59 from zurohki@gmail.com --- The hack in #c56 makes the latest Battle.net client work properly.
https://bugs.winehq.org/show_bug.cgi?id=29384
chris@novazur.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chris@novazur.fr
--- Comment #60 from chris@novazur.fr --- (In reply to Peter from comment #59)
The hack in #c56 makes the latest Battle.net client work properly.
Indeed ! Worked for me too.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #61 from realbug naworldw@gmail.com --- https://bugs.winehq.org/show_bug.cgi?id=56057 I made a bug issue, but I came here in duplicate. Does anyone know what to do with the application?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #62 from Ker noa blue-t@web.de --- The wine-staging patch doesn't fix Battle.net, does it fix the other applications mentioned or should we remove the "staged status" of this bug?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #63 from realbug naworldw@gmail.com --- (In reply to Fabian Maurer from comment #56)
Created attachment 75727 [details] Basic hack that helps for chromium issues
How do I apply this hack? I don't know anything about programming..
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #64 from chris@novazur.fr --- (In reply to realbug from comment #63)
How do I apply this hack? I don't know anything about programming..
To patch wine, you have to compile it. And if you don't know anything about that, just forget it.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #65 from realbug naworldw@gmail.com --- (In reply to chris from comment #64)
(In reply to realbug from comment #63)
How do I apply this hack? I don't know anything about programming..
To patch wine, you have to compile it. And if you don't know anything about that, just forget it.
Is there a possibility that this patch will be applied to the official or beta version?
https://bugs.winehq.org/show_bug.cgi?id=29384
infinity0@pwned.gg changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |infinity0@pwned.gg
--- Comment #66 from infinity0@pwned.gg --- (In reply to chris from comment #60)
(In reply to Peter from comment #59)
The hack in #c56 makes the latest Battle.net client work properly.
Indeed ! Worked for me too.
Works for me too with current Battle.net.14766, applied on top of wine 9.5 with all staging patches. I need it to upgrade to the latest StarCraft II version 5.0.13.
The wine-staging Debian packages don't provide source code for the actual Debian packaging part, so here is some quick instructions on building 32+64-bit wine-staging from scratch:
outside chroot: $ wget "https://dl.winehq.org/wine/source/9.x/wine-9.5.tar.xz" $ tar xf wine-9.5.tar.xz $ cd wine-9.5 $ /path/to/wine-staging/staging/patchinstall.py -a $ wget "https://bugs.winehq.org/attachment.cgi?id=75727&action=diff&context=..." $ patch -p1 < "attachment.cgi?id=75727&action=diff&context=patch&collapsed=&headers=1&format=raw"
inside 32-bit chroot, with wine-9.5 directory bind-mounted inside: $ sudo apt-get build-dep wine-development $ ./configure --prefix=/opt/wine-local --bindir=/opt/wine-local/bin32 $ make -j12 $ make DESTDIR=lol -j12 install # make install needs to build some stuff first
back outside chroot: $ sudo make -j12 install
inside 64-bit chroot, with wine-9.5 directory bind-mounted inside: $ sudo apt-get build-dep wine-development $ ./configure --prefix=/opt/wine-local --libdir=/opt/wine-local/lib64 $ make -j12 $ make DESTDIR=lol -j12 install # make install needs to build some stuff first
back outside chroot: $ sudo make -j12 install $ sudo ln -s /opt/wine-local/bin{32,}/wine $ sudo ln -s /opt/wine-local/bin{32,}/wine-preloader
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #67 from infinity0@pwned.gg --- $ ./configure --prefix=/opt/wine-local --libdir=/opt/wine-local/lib64
er, this should also have --enable-win64
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #68 from realbug naworldw@gmail.com --- (In reply to infinity0 from comment #67)
$ ./configure --prefix=/opt/wine-local --libdir=/opt/wine-local/lib64
er, this should also have --enable-win64
Eventually I failed to build... I think it would be better to wait for this to merge into staging.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #69 from infinity0@pwned.gg --- (In reply to realbug from comment #68)
(In reply to infinity0 from comment #67)
$ ./configure --prefix=/opt/wine-local --libdir=/opt/wine-local/lib64
er, this should also have --enable-win64
Eventually I failed to build... I think it would be better to wait for this to merge into staging.
Possibly you didn't install the build-dependencies correctly. My instructions above are a shortcut that only works on Debian systems and I don't know the full details of how to do it on non-Debian systems. (It also skips the details of creating the relevant chroots.)
In any case, I've told the wine-staging guys about that additional patch and they said they would test and merge it soon:
https://github.com/wine-staging/wine-staging/pull/87
https://bugs.winehq.org/show_bug.cgi?id=29384
Zhiyi Zhang zzhang@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS|MacOS |Linux Assignee|wine-bugs@winehq.org |zzhang@codeweavers.com CC| |zzhang@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #70 from Zhiyi Zhang zzhang@codeweavers.com --- Taking this over to implement it properly with Linux 6.7 userfaultfd.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #71 from Zhiyi Zhang zzhang@codeweavers.com --- Created attachment 76284 --> https://bugs.winehq.org/attachment.cgi?id=76284 A totally untested WIP patch
https://bugs.winehq.org/show_bug.cgi?id=29384
testator@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |testator@protonmail.ch
--- Comment #72 from testator@protonmail.ch --- I tested your totally untested WIP patch Mr Zhang. It was tested using a WoW64 build of git master at time of writing. On several different flavours of CEF apps attempting to launch results in a crash with the message. 0024:err:virtual:userfaultfd_writeprotect ioctl(UFFDIO_REGISTER) failed. Invalid argument.
Considering vanilla wine segfaults, an error message with this patch is an improvement in my case.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #73 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to testator from comment #72)
I tested your totally untested WIP patch Mr Zhang. It was tested using a WoW64 build of git master at time of writing. On several different flavours of CEF apps attempting to launch results in a crash with the message. 0024:err:virtual:userfaultfd_writeprotect ioctl(UFFDIO_REGISTER) failed. Invalid argument.
Considering vanilla wine segfaults, an error message with this patch is an improvement in my case.
What Linux kernel version are you using? The minimum requirement is 6.7. Could you send me a link to the program you used to test?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #74 from testator@protonmail.ch --- I was using linux-6.8.2-gentoo and the program I tested was https://downloader.battle.net/download/getInstaller?os=win&installer=Bat... . I've got userfaultfd enabled in kernel and am using a WoW64 userland in 64 bit only musl. Other windows apps with the same winebuild launch just fine and run. It is only WRITECOPY ones that crash like that. The error message is just spammed regardless of what I launch though.
https://bugs.winehq.org/show_bug.cgi?id=29384
Kimball kdt3rd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kdt3rd@gmail.com
--- Comment #75 from Kimball kdt3rd@gmail.com --- Zhiyi Zhang - that patch seems to work fine for me for the Battle.net Application - still need other components of wine-staging, just did -W ntdll-WRITECOPY and used your patch instead. Thanks!
https://bugs.winehq.org/show_bug.cgi?id=29384
Zhiyi Zhang zzhang@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #76284|0 |1 is obsolete| |
--- Comment #76 from Zhiyi Zhang zzhang@codeweavers.com --- Created attachment 76288 --> https://bugs.winehq.org/attachment.cgi?id=76288 WIP patch 20240407
With this version of the patch, CEF applications should start to work.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #77 from Kimball kdt3rd@gmail.com --- in set_page_vprot_bits I presume you mean to pass TRUE, not page_size to set_page_writecopy
https://bugs.winehq.org/show_bug.cgi?id=29384
Zhiyi Zhang zzhang@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #76288|0 |1 is obsolete| |
--- Comment #78 from Zhiyi Zhang zzhang@codeweavers.com --- Created attachment 76290 --> https://bugs.winehq.org/attachment.cgi?id=76290 WIP patch 20240407-2
cleanup
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #79 from testator@protonmail.ch --- Created attachment 76294 --> https://bugs.winehq.org/attachment.cgi?id=76294 WoW64-musl-CEFsegfault-trace.log
I took kimball's advice and tried wine-staging-9.6 without the staged ntdll-writecopy patches but with WIP patch 20240407-2. Here is the results https://pastebin.com/Lc0VEHt8 . Still segfaulting but this time without the error message, most likely related to using WoW64.
I tried installing battle.net again with WINEDEBUG=all with said staging and WIP patch and it displays the window without segfault and gets stuck at "downloading new files.... (5%)" I got a 422MB tracelog from that which I don't think is appropriate to upload but searching through it for function names and warnings from the patch turns up nothing. So I grepped VPROT and found the last used instance of it. Small snippet here https://pastebin.com/WDpVMEF5 .
Finally I tried a simpler CEF app, JagexLauncher.exe available after installing https://cdn.jagex.com/Jagex%20Launcher%20Installer.exe, on an old prefix using WINEDEBUG=ALL and wine segfaults with a huge tracelog. I tried grepping through the log for relevant function names from the patch to no avail. Without WINEDEBUG=ALL it also segfaults. Here's a snippet of the last 2MB from the segfault from the CEF app as attached to this comment.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #80 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to testator from comment #79)
Created attachment 76294 [details] WoW64-musl-CEFsegfault-trace.log
Please upload a WINEDEBUG=warn+virtual,fixme+virtual,err+virtual log when running Battle.net-Setup.exe with my latest patch. And did you get segfaults when applying Fabian's hack from comment #56?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #81 from testator@protonmail.ch --- Here's the battlenetinstall with err+warn+fixme on staging-9.6 with WIP patch 20240407-2 https://pastebin.com/q2PPMbJW . It segfaults without showing the battlenet screen. I tried that hack in #56 you mentioned, it segfaults in the exact same way as in the pastebin for err+warn+fixme. In the previous trace from the generic CEF app it segfaults then unwinds at ntdll.longjmp according to the snippet posted. Perhaps that is enough info to track what's causing the segfault down now? It has to do with WoW64 i'd imagine since Kimball said it was working on their setup which probably isn't WoW64 because if it is then its a musl libc thing involving stack sizes probably.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #82 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to testator from comment #81)
It segfaults without showing the battlenet screen. I tried that hack in #56 you mentioned, it segfaults in the exact same way
This suggests that the segfault is not from the PAGE_WRITECOPY support and it's a different bug. I tried the experimental wow build with my patch and it's running fine.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #83 from testator@protonmail.ch --- Strangely when running with the vanilla writecopy implementation with the staging-9.6 patchset, without the staged writecopy or experimental userfaultfd that is, it gets to the battlenet installation gui, asks for the language, and then says "45% done updating" then freezes forever. Here's a log of that https://pastebin.com/WuZhXCgi . Should I file a seperate bug for this behaivor after your patch is merged? If your patch gets merged then it will segfault for me instead of making it that far. Along with several currently working CEF apps that I use that will segfault with this patchset under 9.6.
https://bugs.winehq.org/show_bug.cgi?id=29384
Qwerty Chouskie asdfghrbljzmkd@outlook.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |asdfghrbljzmkd@outlook.com
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #84 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to testator from comment #83)
Strangely when running with the vanilla writecopy implementation with the staging-9.6 patchset, without the staged writecopy or experimental userfaultfd that is, it gets to the battlenet installation gui, asks for the language, and then says "45% done updating" then freezes forever. Here's a log of that https://pastebin.com/WuZhXCgi . Should I file a seperate bug for this behaivor after your patch is merged? If your patch gets merged then it will segfault for me instead of making it that far. Along with several currently working CEF apps that I use that will segfault with this patchset under 9.6.
Let me get this straight. Battle.net installer succeeds when running on wine-staging-9.6 without any of the ntdll_WRITECOPY staging patches, the hack in #56, and my userfaultfd WIP patch. However, it gets segfaults when you run wine-staging-9.6 with any one of them, is that correct? What about upstream wine?
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #85 from testator@protonmail.ch --- Yes strange as it sounds you have that correct. I ran battle.net with a fresh prefix under wine-vanilla-9.6 without any patches and it did the same thing as without staged writecopy or without the userfaultfd writecopy. That is the langauge selection screen appears, after selecting language it hangs forever at "downloading battle.net update 45%" no segfaults.
I had a hunch about something. I compiled wine-staging-9.6 with the userfaultfd patch again but this time with far less aggresive optimization flags, e.g no lto or -O3. It results in battle.net launching in staging-9.6 with userfaultfd to the same thing as vanilla wine, language select followed by stuck at 45% forever. Maybe i'm just an idiot at installing battle.net in a fresh prefix but preinstalled doesn't work either with strange dll import errors. I'm going to take a wild guess here and say since it works for you and kimball its a musl libc thing. There's something to bisect between wine 9.2 and 9.3 since other CEF apps didn't have this issue at that time. I've been sticking to 9.2 hoping upstream would randomly fix it but here we are....
And this is definitely not your bug? Sorry for the confusion and the spam.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #86 from Kimball kdt3rd@gmail.com --- The new implementation does seem to reliably work for me, including re-installing battle.net (although admittedly I hadn't done a fresh prefix). I do however have a few other changes of things I haven't decided are important - I am noticing that there seems to be a whole slew of sub-processes (or perhaps threads?) spinning out, triggering creation of lots of vulkan contexts which is why I started looking thinking that was the crash you're experiencing, but those seem to be using wintrust to validate the various dlls when I run a trace, as they are emitting errors around crypt asn being unable to find a decoder for a message type that wintrust clearly registers in DllRegisterServer (although I can't see that registration actually running at the moment). That however I believe is orthogonal to this, it just is very slow to start up, and I believe does occasionally hang during startup after login (which is what I was trying to find).
So I may have changed behavior than running a pure vanilla setup, however, this patch does seem to run fine, including installing battle.net (including the beta version)
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #87 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to testator from comment #85)
I compiled wine-staging-9.6 with the userfaultfd patch again but this time with far less aggresive optimization flags, e.g no lto or -O3. It results in battle.net launching in staging-9.6 with userfaultfd to the same thing as vanilla wine
It's possible that wine compiled with LTO or -O3 can cause segfault. It's not a well-tested config. Wine doesn't officially support LTO. Also, there are some compilers in the past that have bugs even -Og so it's also possible with -O3. Anyway, your result suggests the userfaultfd patch is not at fault here.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #88 from Zhiyi Zhang zzhang@codeweavers.com --- (In reply to Kimball from comment #86)
The new implementation does seem to reliably work for me, including re-installing battle.net (although admittedly I hadn't done a fresh prefix). I do however have a few other changes of things I haven't decided are important - I am noticing that there seems to be a whole slew of sub-processes (or perhaps threads?)
It's possible that with a working PAGE_WRITECOPY support, some processes that were previously crashing can now go further.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #89 from infinity0@pwned.gg --- (In reply to Zhiyi Zhang from comment #84)
(In reply to testator from comment #83)
Strangely when running with the vanilla writecopy implementation with the staging-9.6 patchset, without the staged writecopy or experimental userfaultfd that is, it gets to the battlenet installation gui, asks for the language, and then says "45% done updating" then freezes forever. Here's a log of that https://pastebin.com/WuZhXCgi . Should I file a seperate bug for this behaivor after your patch is merged? If your patch gets merged then it will segfault for me instead of making it that far. Along with several currently working CEF apps that I use that will segfault with this patchset under 9.6.
Let me get this straight. Battle.net installer succeeds when running on wine-staging-9.6 without any of the ntdll_WRITECOPY staging patches, the hack in #56, and my userfaultfd WIP patch. However, it gets segfaults when you run wine-staging-9.6 with any one of them, is that correct? What about upstream wine?
Just chiming in for the record to avoid any misunderstanding - my understanding is that the hack in #56 is meant to be applied together with the ntdll_WRITECOPY staging patches. At least that's what I successfully tested in comment #66, i.e. wine-staging-9.5 + #56 hack.
In other words, applying #56 by itself onto wine-vanilla isn't supposed to work.
--- Comment #90 from chris@novazur.fr --- (In reply to realbug from comment #65)
Is there a possibility that this patch will be applied to the official or beta version?
The patch seems to be included in wine-staging-9.7.
https://bugs.winehq.org/show_bug.cgi?id=29384
--- Comment #91 from Fabian Maurer dark.shadow4@web.de --- (In reply to infinity0 from comment #89)
Just chiming in for the record to avoid any misunderstanding - my understanding is that the hack in #56 is meant to be applied together with the ntdll_WRITECOPY staging patches. At least that's what I successfully tested in comment #66, i.e. wine-staging-9.5 + #56 hack.
In other words, applying #56 by itself onto wine-vanilla isn't supposed to work.
The hack/patch is supposed to work against vanilla wine. Of course there might be other issues at play, leading it to only work with or without other staging patches.
https://bugs.winehq.org/show_bug.cgi?id=29384
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cedric.dewijs@eclipso.eu
--- Comment #92 from Fabian Maurer dark.shadow4@web.de --- *** Bug 56772 has been marked as a duplicate of this bug. ***
-
wine-bugs＠winehq.org -
WineHQ Bugzilla