http://bugs.winehq.org/show_bug.cgi?id=32205
Bug #: 32205 Summary: YoukuDesktop error in initializing Product: Wine Version: 1.5.17 Platform: x86 URL: http://desktop.youku.com/youkuclient/youkuclient_setup .exe OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: fracting@gmail.com Classification: Unclassified
Created attachment 42480 --> http://bugs.winehq.org/attachment.cgi?id=42480 Log: start youkudesktop
YoukuDesktop is a download manager and player for www.youku.com's video.
Steps to reproduce: 1. install Youku Client:
$ wine youkuclient_setup.exe
The installer will ask you to install flash, click "yes"/"确定"
2. start youku desktop: $ cd ~/.wine/drive_c/Program\ Files/YouKu/YoukuClient $ wine YoukuDesktop.exe
Expect result: Start youku client Actual result: An error window pupup with message "初始化错误, 是否重试?", means "error in initializing, would you like to retry?" in English.
http://bugs.winehq.org/show_bug.cgi?id=32205
Jactry Zeng jactry92@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jactry92@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32205
lizhenbo litimetal@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |litimetal@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #1 from lizhenbo litimetal@gmail.com --- I didn't meet this problem in wine 1.7.11 Maybe the installer has been changed? c828f87a32a4d7092a0da76da0855d6dce1b32cb youkuclient_setup.exe
http://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #2 from Qian Hong fracting@gmail.com --- (In reply to lizhenbo from comment #1)
I didn't meet this problem in wine 1.7.11 Maybe the installer has been changed? c828f87a32a4d7092a0da76da0855d6dce1b32cb youkuclient_setup.exe
Thanks for testing.
The installer has been updated. My old version is dd2a100df052619b6d8500644f313fcc3844e704 youkuclient_setup.exe
I'm doubting that this bug is related to winsock so I retest with today's git (wine-1.7.16-238-g2b390f0) with Bruno's ws2_32 patch committed, but it still present.
http://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #3 from Bruno Jesus 00cpxxx@gmail.com --- It has a winsock problem yes, but it may not be the cause. To test please try Erich's patches from bug https://github.com/compholio/wine-compholio-daily/tree/master/patches/09-Tra...
http://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #4 from Qian Hong fracting@gmail.com --- (In reply to Bruno Jesus from comment #3)
It has a winsock problem yes, but it may not be the cause. To test please try Erich's patches from bug https://github.com/compholio/wine-compholio-daily/tree/master/patches/09- TransmitFile
Thanks Bruno, Erich's patches doesn't help here.
http://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #5 from Qian Hong fracting@gmail.com --- Created attachment 48191 --> http://bugs.winehq.org/attachment.cgi?id=48191 Log: +tid,+winsock log with Erich's patch
I've attached a +tid,+winsock log with Erich's patch, but I guess even if it is a winsock bug it is not related to what Erich tries to fix.
The below part of log seems interesting: 0026:trace:winsock:WSASocketW created 017c 0026:trace:winsock:WS2_AcceptEx (178, 17c, 0xcb525c, 0, 144, 144, 0x33f730, 0xcb5220) 0026:trace:winsock:WSAStringToAddressA ("0.0.0.0", 2, (nil), 0x33f644, 0x33f6cc) 0026:trace:winsock:WSASocketW af=2 type=2 protocol=17 protocol_info=(nil) group=0 flags=0x1 0026:trace:winsock:WSASocketW created 0180 0026:trace:winsock:WS_setsockopt socket: 0180, level 0xffff, name 0x4, ptr 0x33f8e8, len 4 0026:trace:winsock:WS_bind socket 0180, ptr 0x33f914 { family AF_INET, address 0.0.0.0, port 4466 }, length 16 0026:trace:winsock:WS_setsockopt socket: 0180, level 0xffff, name 0x1002, ptr 0x33f90c, len 4 0026:trace:winsock:WS_setsockopt socket: 0180, level 0xffff, name 0x1001, ptr 0x33f910, len 4 0026:trace:winsock:WSAStringToAddressA ("224.0.0.100", 17, (nil), 0x33f78c, 0x33f814) 0026:trace:winsock:WSAStringToAddressA ("224.0.0.100", 2, (nil), 0x33f7a0, 0x33f828) 0026:trace:winsock:WS_setsockopt socket: 0180, level 0xffff, name 0x20, ptr 0x33f974, len 4 0026:trace:winsock:WS_setsockopt socket: 0180, level 0x0, name 0xc, ptr 0x33f958, len 8 0026:trace:winsock:WS_setsockopt socket: 0180, level 0x0, name 0xa, ptr 0x33f950, len 1 0026:trace:winsock:WS_setsockopt socket: 0180, level 0x0, name 0xb, ptr 0x33f948, len 4 0026:trace:winsock:WSAStringToAddressA ("0.0.0.0", 2, (nil), 0x33f674, 0x33f6fc) 0026:trace:winsock:WSASocketW af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1 0026:trace:winsock:WSASocketW created 0184 0026:trace:winsock:WS_setsockopt socket: 0184, level 0xffff, name 0x4, ptr 0x33f8fc, len 4 0026:trace:winsock:WS_setsockopt socket: 0184, level 0xffff, name 0x8, ptr 0x33f8f8, len 4 0026:trace:winsock:WS_bind socket 0184, ptr 0x33f914 { family AF_INET, address 0.0.0.0, port 4466 }, length 16 0026:trace:winsock:WS_listen socket 0184, backlog 2147483647 0026:trace:iphlpapi:GetAdaptersInfo pAdapterInfo 0x33c6d8, pOutBufLen 0x33c6c8 0026:trace:iphlpapi:AllocateAndGetIpForwardTableFromStack table 0x33c54c, bOrder 0, heap 0x110000, flags 0x00000000 0026:trace:iphlpapi:AllocateAndGetIpForwardTableFromStack returning ret 0 table 0x178e18 0026:trace:iphlpapi:GetAdaptersInfo returning 0 0026:trace:winsock:WSAStringToAddressA ("", 2, (nil), 0x33c528, 0x33c5b0) sm exited,Error: Unknown error^M 0026:trace:winsock:WS_closesocket socket 0180 0026:trace:winsock:WS_closesocket socket 0184 0026:trace:winsock:WS_closesocket socket 0174 0026:trace:winsock:WS_closesocket socket 0178
http://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #6 from Bruno Jesus 00cpxxx@gmail.com --- Qian, please attach a screenshot of the error screen just to be sure I reached the same point in my test.
http://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #7 from Qian Hong fracting@gmail.com --- Created attachment 48195 --> http://bugs.winehq.org/attachment.cgi?id=48195 Screenshot: error dialog
Thanks Bruno, I attached the screenshot, it should be something like that.
https://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #8 from Bruno Jesus 00cpxxx@gmail.com --- I have found the first issue in this bug, still looking for the second one that triggers the background app to quit and close all listener sockets.
Remembering that the current offered installer is updated and cannot be used to trigger the issue.
https://bugs.winehq.org/show_bug.cgi?id=32205
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #9 from Bruno Jesus 00cpxxx@gmail.com --- Created attachment 50147 --> https://bugs.winehq.org/attachment.cgi?id=50147 Ugly hack
Ok, with http://source.winehq.org/patches/data/108059 and the attached hack the application starts and displays the main screen but fails again in another error.
Qian, can you translate the new error to see if it has any new information? Or is it just a generic error message.
https://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #10 from Jactry Zeng jactry92@gmail.com --- Hi Bruno, (In reply to Bruno Jesus from comment #9)
Created attachment 50147 [details] Ugly hack
Ok, with http://source.winehq.org/patches/data/108059 and the attached hack the application starts and displays the main screen but fails again in another error.
Qian, can you translate the new error to see if it has any new information? Or is it just a generic error message.
Text in that picture means: Intitalize fail, would you like try again? And the blue button is "try again", another is "close".
https://bugs.winehq.org/show_bug.cgi?id=32205
Jactry Zeng jzeng@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jzeng@codeweavers.com
--- Comment #11 from Jactry Zeng jzeng@codeweavers.com --- (In reply to Jactry Zeng from comment #10)
Hi Bruno, (In reply to Bruno Jesus from comment #9)
Created attachment 50147 [details] Ugly hack
Ok, with http://source.winehq.org/patches/data/108059 and the attached hack the application starts and displays the main screen but fails again in another error.
Qian, can you translate the new error to see if it has any new information? Or is it just a generic error message.
Text in that picture means: Intitalize fail, would you like try again? And the blue button is "try again", another is "close".
Oops, this is not what you want, my wrong. And I can not reproduce it with new version of Youkun, so I didn't get the error. Sorry :(
https://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #12 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to Jactry Zeng from comment #11)
Oops, this is not what you want, my wrong. And I can not reproduce it with new version of Youkun, so I didn't get the error. Sorry :(
Don't worry, thanks for trying to help. The app version is 4.6, the file info:
535962eb1e2fbdbec76969053df0a726c772e44c youkuclient_setup.exe 13M
https://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #13 from Bruno Jesus 00cpxxx@gmail.com --- The current problem in this bug is that the application attempts to call WSAStringtoAddressA with an empty string, that results in WSAEINVAL (as expected). But the background application is not happy and quit after that so Youku cannot connect to it.
The question is: where did it get that empty IP from and why it was empty?
0024:trace:iphlpapi:GetAdaptersInfo pAdapterInfo 0x33c74c, pOutBufLen 0x33c744 0024:trace:iphlpapi:AllocateAndGetIpForwardTableFromStack table 0x33c680, bOrder 0, heap 0x110000, flags 0x00000000 0024:trace:iphlpapi:AllocateAndGetIpForwardTableFromStack returning ret 0 table 0x18a2c0 0024:trace:iphlpapi:GetAdaptersInfo returning 0 0024:trace:winsock:WSAStringToAddressA ("", 2, (nil), 0x33c638, 0x33c630) sm exited,Error: Unknown error <<<===== application log before quitting
What seems to happen is that the application is trying to list the interfaces and get the IP of a specific interface that does not have an IP, ending up with an empty string. Bug forcing an IP over all empty interfaces (or disabling interfaces without an IP) do not help.
https://bugs.winehq.org/show_bug.cgi?id=32205
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |317fd11e85157e0b9eaca1d0019 | |14706072d3f7f Status|NEW |RESOLVED Component|-unknown |iphlpapi Resolution|--- |FIXED
--- Comment #14 from Bruno Jesus 00cpxxx@gmail.com --- Fixed by http://source.winehq.org/git/wine.git/commitdiff/317fd11e85157e0b9eaca1d0019...
https://bugs.winehq.org/show_bug.cgi?id=32205
--- Comment #15 from Qian Hong fracting@gmail.com --- (In reply to Bruno Jesus from comment #14)
Fixed by http://source.winehq.org/git/wine.git/commitdiff/ 317fd11e85157e0b9eaca1d001914706072d3f7f
Confirming Fixed, great work, thanks Bruno!
Next might be a builtin IE bug, with `winetricks ie7` YoukuDesktop works quite good. Builtin IE doesn't support Flash yet, which is a known bug.
https://bugs.winehq.org/show_bug.cgi?id=32205
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.35.