https://bugs.winehq.org/show_bug.cgi?id=53179
Bug ID: 53179 Summary: Can't get into the Lineage 2 server Product: Wine-staging Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: terapy-session@bk.ru CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Не зайти на сервер Lineage 2. После авторизации прохожу до выбора сервера, и при нажатии войти никакой реакции, через несколько минут происходит дисконнект. 3 июня работало, возможно повлияло обновление Wine. Старого пакета Wine не сохранилось чтоб проверить.
В ошибках логах есть: 0298:err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions.
Сервер использует WMI, возможно там что-то меняли.
https://bugs.winehq.org/show_bug.cgi?id=53179
Dmitry terapy-session@bk.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #1 from Dmitry terapy-session@bk.ru --- Can't access the Lineage 2 server. After logging in, go to server selection and no reaction when I press enter, disconnect after a few minutes. On June 3 it worked, maybe Wine update had an effect. Didn't keep the old Wine package to check.
The errors in the logs are: 0298:err:winediag:WSASocketW Failed to create a socket of type SOCK_RAW, this requires special permissions.
The server uses WMI, maybe something was changed there.
https://bugs.winehq.org/show_bug.cgi?id=53179
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Can't get into the Lineage |Lineage 2 can't connect to |2 server |server
--- Comment #2 from Gijs Vermeulen gijsvrm@gmail.com --- You've marked this bug as a wine-staging only issue, does it work with upstream wine?
Please attach the full terminal output, see: https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal...
https://bugs.winehq.org/show_bug.cgi?id=53179
Dmitry terapy-session@bk.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Dmitry terapy-session@bk.ru --- It's working now.
Wine out of the box lacks some built-in libraries. After running Winetricks with DX9 libraries installed, the game works. Maybe something was missing, maybe it's d3dcompiler or dbghelp not detected.
https://bugs.winehq.org/show_bug.cgi?id=53179
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Resolution|INVALID |--- Status|RESOLVED |UNCONFIRMED
--- Comment #4 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to Dmitry from comment #3)
Wine out of the box lacks some built-in libraries. After running Winetricks with DX9 libraries installed, the game works. Maybe something was missing, maybe it's d3dcompiler or dbghelp not detected.
That's a bug in Wine, not invalid.
Please list the winetricks components that you installed.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #5 from Dmitry terapy-session@bk.ru --- After repeating the past actions I did with the old wine folder, I deleted it, repeated it, but the game still didn't work. Then I remembered that the version from win10 to win7 had flipped, so last time I switched back to win10, this time I did it only at the very end after all the experiments. And lo and behold, the game started up. For some reason that particular client needs win10 compatibility mode. I'll be checking soon to see if it works on purely Windows 7 to find out the details.
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #6 from Dmitry terapy-session@bk.ru --- Tested on Windows 7, game works. So Wine has a problem with Win7 compatibility mode for the latest version of Lineage 2. No problem with older clients.
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #7 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
Please attach terminal logs of the game not working in win7 mode and of the game working in win10 mode for comparison, to this bug.
You've marked this bug as a wine-staging only issue, does it work with upstream wine?
Please attach the full terminal output, see: https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a. _terminal_output.29.3F
Regards
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #8 from Zeb Figura z.figura12@gmail.com --- Unless the application works on actual Windows 7, I'm not sure there's going to be anything to fix here. In most such cases the application just requires a newer Windows version.
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #9 from Dmitry terapy-session@bk.ru --- (In reply to Zeb Figura from comment #8)
Unless the application works on actual Windows 7, I'm not sure there's going to be anything to fix here. In most such cases the application just requires a newer Windows version.
On Windows 7 the real thing works, I wrote just above.
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #10 from Zeb Figura z.figura12@gmail.com --- Okay, I didn't carefully read the prior comments. Sorry about that.
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #11 from Dmitry terapy-session@bk.ru --- Created attachment 72694 --> https://bugs.winehq.org/attachment.cgi?id=72694 win7 log
win7 log
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #12 from Dmitry terapy-session@bk.ru --- Created attachment 72695 --> https://bugs.winehq.org/attachment.cgi?id=72695 win10 log
https://bugs.winehq.org/show_bug.cgi?id=53179
--- Comment #13 from Dmitry terapy-session@bk.ru --- I would like to take advantage of the presence of people to point out that the forum lacks support for downloading zst archives, good for .txt compression. I wanted to offer on the main forum, but it's impossible to recover the password there as it asks you to contact the administrator, but that doesn't work.