http://bugs.winehq.org/show_bug.cgi?id=16130
Summary: Runes of Magic client doesn't communicate with the server Product: Wine Version: 1.1.8 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: ulf@dedio.de
Created an attachment (id=17366) --> (http://bugs.winehq.org/attachment.cgi?id=17366) Wireshark protocol of login on Windows
Hi,
I tried to start "Runes of Magic" with wine, but failed.
After the installation it starts fine, the License-Dialog and Login-Screen appear correctly.
After entering the login data, the client tries to communicate with the login server (authentication and fetching the server list).
This doesn't work with Wine. I attach 2 wireshark protocols. The windows protocol shows data in the tcp packets from both sides after the SYN.
The Linux/Wine protocol shows data only from the server, the client (running on Wine) doesn't send data, just an ACK packet.
This leads me to the suspicion, that either the RPC library on Wine is not working as expected or there is some encryption, which is only done with empty stubs on Wine.
I tried to substitute rpcrt4.dll and secur32.dll on wine, but it doesn't solve the problem.
As the Windows rpcrt4.dll leads also to an error (something with service manager, but after maybe 30sec it continued), I removed it again from the list of native libs.
If there is some more information, which I can provide, or some test I can do, please tell me.
http://bugs.winehq.org/show_bug.cgi?id=16130
--- Comment #1 from dideldum ulf@dedio.de 2008-11-20 03:15:09 --- Created an attachment (id=17367) --> (http://bugs.winehq.org/attachment.cgi?id=17367) Wireshark protocol of login on Linux with Wine
http://bugs.winehq.org/show_bug.cgi?id=16130
--- Comment #2 from Lei Zhang thestig@google.com 2008-11-20 13:29:15 --- Can you attach the console output, without any Windows dlls?
http://bugs.winehq.org/show_bug.cgi?id=16130
--- Comment #3 from dideldum ulf@dedio.de 2008-11-20 15:10:28 --- Thanks for your fast answer!
I called it like:
WINEDEBUG=+loaddll wine Runes\ of\ Magic.exe
This starts first the launcher. In the launcher I clicked the "Start" button. Until line 834 of the log file it's launcher related. Then (I assume from line 851 onwards) it is related to the real client. I haven't found out how to start the client directly, either exe starts first the launcher. I guess there is a parent-child-process-check to avoid direct client start... Just my imagination...
I entered the login data in the client and pressed the enter button. The effect is seen in line 5623 of the log, here the socket communication with the server is opened (the SYN packets in the wireshark trace).
I attach the log (compressed with bzip2) after this post.
Hope this helps. If you need more traces, please tell me the channels. I cannot trace all channels at once, as this leads to many GB of log (and my Linux partition has only 7GB left).
If there is any other activity to help you, I offer, whatever I can.
http://bugs.winehq.org/show_bug.cgi?id=16130
--- Comment #4 from dideldum ulf@dedio.de 2008-11-20 15:11:56 --- Created an attachment (id=17377) --> (http://bugs.winehq.org/attachment.cgi?id=17377) wine log starting the RoM launcher and then the RoM client from the launcher
log was created calling "WINEDEBUG=+loaddll wine Runes\ of\ Magic.exe"
http://bugs.winehq.org/show_bug.cgi?id=16130
Carl Smotricz carl.smotricz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |carl.smotricz@gmail.com
--- Comment #5 from Carl Smotricz carl.smotricz@gmail.com 2008-12-16 14:04:54 --- Perhaps this will help: Pretty much at the time of failure, I see this message on the console:
fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER {25a207b9-ddf3-4660-8ee9-76e58c74063e}: stub
Which I read to mean: The client is trying to call this fancy Winsock function, which is currently unimplemented, and that halts everything dead.
http://bugs.winehq.org/show_bug.cgi?id=16130
Florian Friedrich friedrich@hooster.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #6 from Florian Friedrich friedrich@hooster.de 2009-01-04 18:56:15 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=16130
Ivo Nunes ivo.a.nunes@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ivo.a.nunes@gmail.com
--- Comment #7 from Ivo Nunes ivo.a.nunes@gmail.com 2009-03-24 10:16:40 --- This bug is solved with wine 1.1.17.
Please set the state of the bug to solved.
http://bugs.winehq.org/show_bug.cgi?id=16130
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #8 from Austin English austinenglish@gmail.com 2009-03-24 11:07:30 --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=16130
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Alexandre Julliard julliard@winehq.org 2009-03-27 13:54:33 --- Closing bugs fixed in 1.1.18.
http://bugs.winehq.org/show_bug.cgi?id=16130
Randy randallrandybob@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |randallrandybob@yahoo.com
--- Comment #10 from Randy randallrandybob@yahoo.com 2009-08-31 23:17:18 --- Hi...I can't figure out how to solve this issue with the instructions below. I've downloaded the attachments but I don't know how to use them or where to put them. I probably missed something but if someone could just post a step by step that'd be great. :D
-
wine-bugs＠winehq.org