https://bugs.winehq.org/show_bug.cgi?id=42005
Bug ID: 42005 Summary: "osu!" cannot connect to the internet Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: eldiablodivino@gmail.com Distribution: ---
Created attachment 56439 --> https://bugs.winehq.org/attachment.cgi?id=56439 The logs produced by both Wine 2.0rc1 and Wine Staging 1.9.23-3 when WINEDEBUG is set to "+wininet".
======== Summary: ========
I have been having a great deal of trouble getting Osu to work on Arch Linux. The short version is that I have no internet access as far as both Osu itself, and the Osu installer, are concerned. I have attached my +wininet debug logs to this report. Please help.
============================================ Longer explanation / background information: ============================================
Originally, I was running Ubuntu 16.10. I had Osu installed via PlayOnLinux4 . Usually I use PlayOnLinux just as a wine prefix manager, but in this case I think I *did* install it via their automated installation script. In any case, it was running with Wine 1.9.1, and it worked perfectly fine, with no issues whatsoever.
Very recently, I switched to Arch Linux. This means that I am running a relatively fresh installation. Unfortunately, I can no longer get Osu working. Here is what I have tried:
1. First, I installed PlayOnLinux 4 via the "playonlinux" package from the official repository. I then simply copied across my .PlayOnLinux folder from my old Ubuntu install. This folder contains both the wine prefixes and the actual wine binaries - in other words, it should contain everything needed to run Osu, and it should all be set up EXACTLY as it was on Ubuntu. When I launch Osu via PlayOnLinux, the game runs in offline mode. I can play it just fine, but I'm limited to single-player and have no online statistics recording. At the bottom of the screen, it constantly says "Connection failed. Retrying in 30s...". It seems to repeatedly attempt to connect to the Osu servers, but always fails.
2. I then installed the "wine-gaming-nine" package from the Arch User Repository, as well as "winetricks" from the official repository. This time, I decided to try without touching PlayOnLinux, and just use Wine directly. Following the guidance on the AppDB page for Osu, I set up a clean prefix with the win32 architecture, and installed dotnet45 via winetricks. I then tried to run the Osu installer... and the Osu installer fails, saying that it could not connect to the internet! In other words, it has the same issue as before, just moved to an earlier stage (since this time I was installing it from scratch).
3. I then replaced "wine-gaming-nine" with "wine-staging" from the official repository. Again, I set up a clean win32 prefix, installed dotnet45, and tried to install Osu. Again, it complains about not having internet access.
4. I then replaced "wine-staging" with "wine" from the official repository. Again, I set up a clean win32 prefix, installed dotnet45, and tried to install Osu. Again, it complains about not having internet access.
So to sum up, I've tried running Osu with Wine 1.9.1, Wine Staging 1.9.23-3 (with gallium-nine patches), Wine Staging 1.9.23 (vanilla), and with Wine 2.0rc1, all with the same result: no internet access for Osu.
============ Other notes: ============
I should add that I have other programs running in Wine (Skype and Garena), and they are able to use the internet. They aren't .NET apps, as far as I'm aware, so perhaps that's why?
My internet works just fine outside of Wine, as far as I can tell. I'm able to browse the internet, send and receive emails, use Discord, etc. I'm just running NetworkManager with mostly default settings, albeit with IPv6 disabled.
I don't know much about Wine, so I could be barking up the wrong tree, but one log message that stands out to me is "fixme:ras:RasEnumConnectionsW RAS support is not implemented! Configure program to use LAN connection/winsock instead!". I did some searching online for this message, but unfortunately I wasn't able to find much. I did see some people saying to "just install libgnutls, as well as the 32-bit version". But the thing is, I DO have both installed. On Arch, these are the "gnutls" and "lib32-gnutls" packages, and I have confirmed that I have both. I even tried reinstalling them, and it made no difference.
I have attached the logs produced by both Wine 2.0rc1 and Wine Staging 1.9.23-3 when WINEDEBUG is set to "+wininet".
===
I'm not sure if this is a Wine bug or just something weird on my system, but either way I would really appreciate any help you could offer. Please let me know if I need to provide any more information. Thanks.
https://bugs.winehq.org/show_bug.cgi?id=42005
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net --- The logs don't show any wininet messages. Are you using native wininet in that wineprefix?
https://bugs.winehq.org/show_bug.cgi?id=42005
--- Comment #2 from John eldiablodivino@gmail.com --- (In reply to Rosanne DiMesio from comment #1)
The logs don't show any wininet messages. Are you using native wininet in that wineprefix?
Thanks for your reply. I don't believe that I am. I haven't manually added any overrides. I'm literally using a clean win32 prefix, with dotnet45 then installed via winetricks.
Running winecfg shows only two overrides: *mscoree (native) and *msxlm3 (native).
https://bugs.winehq.org/show_bug.cgi?id=42005
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- Also running Arch, and for me it works. You probably need a "+winsock" trace, it doesn't seem to use wininet.
https://bugs.winehq.org/show_bug.cgi?id=42005
--- Comment #4 from John eldiablodivino@gmail.com --- (In reply to Fabian Maurer from comment #3)
Also running Arch, and for me it works. You probably need a "+winsock" trace, it doesn't seem to use wininet.
Thanks for your reply. I'm attaching a new log with "+winsock". It seems to include the following winsock warning: "warn:winsock:WSASocketW failed, error 10043!"
https://bugs.winehq.org/show_bug.cgi?id=42005
--- Comment #5 from John eldiablodivino@gmail.com --- Created attachment 56445 --> https://bugs.winehq.org/attachment.cgi?id=56445 The log produced by Wine 2.0rc1 when WINEDEBUG is set to "+winsock".
https://bugs.winehq.org/show_bug.cgi?id=42005
John eldiablodivino@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #6 from John eldiablodivino@gmail.com --- Well, I fixed it. Thanks for the help. The winsock error message got me down the right path to figuring it out.
It turns out it was caused by me disabling IPv6 in the kernel. I did this during installation, when I was following along the Arch wiki. My ISP doesn't even support IPv6, and the wiki suggested disabling it, mentioning that although it can break certain programs, in most cases it is completely harmless. I suppose this was one of those cases. :)
Re-enabling IPv6 for the kernel fixed the issue. It was just user error and not a Wine bug, so I'll mark this as resolved. I'll post a comment on the Osu AppDB page in case anyone else comes across this issue in the future.
https://bugs.winehq.org/show_bug.cgi?id=42005
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- Good to hear it's resolved. Although I feel like we should have better reporting for such a case, like an actual error message instead of a (hidden by default) warning, but I don't know how feasible this is.
https://bugs.winehq.org/show_bug.cgi?id=42005
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|"osu!" cannot connect to |"osu!" cannot connect to |the internet |the internet (IPv6 disabled | |in kernel) Status|RESOLVED |CLOSED
--- Comment #8 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to Fabian Maurer from comment #7)
Although I feel like we should have better reporting for such a case, like an actual error message instead of a (hidden by default) warning, but I don't know how feasible this is.
It is difficult to deduce that the socket creation failed because IPv6 is disabled, the error returned by the function is sort of generic. We could make the error always visible so at least it would give a hint by turning the warn into error.
https://bugs.winehq.org/show_bug.cgi?id=42005
John eldiablodivino@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED Summary|"osu!" cannot connect to |"osu!" cannot connect to |the internet (IPv6 disabled |the internet |in kernel) |
--- Comment #9 from John eldiablodivino@gmail.com --- Thinking on it a bit more, I think I may have been a bit too hasty in marking this as invalid. I'm not a Wine developer and don't know much about its inner workings, so perhaps I should have waited first to see if the experts think it's a bug or not?
I say this because Osu actually has an in-development native version, which uses regular Mono, and it was able to connect to the internet perfectly fine with IPv6 disabled. This native version is available via the "osu-git" AUR package on Arch, or from this GitHub repository: https://github.com/ppy/osu
The native version of Osu is in a very early stage though, which is why I wasn't using it. At present, it's not really playable. It works just enough for me to be able to open it up, log in, and verify that it can indeed connect to the internet with IPv6 disabled.
With the Windows version of Osu running in Wine (https://osu.ppy.sh), however, it could not connect to the internet with IPv6 disabled. I'm wondering now if this could be an issue in Wine-Mono or something?
Again, I'm not an expert, so I don't know - but I thought it would be worth adding this. I'm not sure if it should just fail with IPv6 disabled, or if it should be able to handle it somehow.
https://bugs.winehq.org/show_bug.cgi?id=42005
--- Comment #10 from Bruno Jesus 00cpxxx@gmail.com --- The application from bug 41279 suffered from the exact same issue with native .net. I guess mono is just less picky about socket failures.
https://bugs.winehq.org/show_bug.cgi?id=42005
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Jeff Zaroyko jeffz@jeffz.name --- Closing invalid.
https://bugs.winehq.org/show_bug.cgi?id=42005
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |---
--- Comment #12 from Jeff Zaroyko jeffz@jeffz.name --- Reopening in case there's more discussion on this. The previous close was just a mass-close.
https://bugs.winehq.org/show_bug.cgi?id=42005
crazylegoguy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |crazylegoguy@gmail.com
--- Comment #13 from crazylegoguy@gmail.com --- Osu! requires the encryption library lib32-gnutls (at least this is the name of the package on arch) to connect to the game servers. If this package is missing, you won't be connected to the server.
https://bugs.winehq.org/show_bug.cgi?id=42005
Invictus Tiberius invictustiberius@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |invictustiberius@gmail.com
--- Comment #14 from Invictus Tiberius invictustiberius@gmail.com --- It is not a bug on Wine. It should be marked as Invalid or Upstream.
https://bugs.winehq.org/show_bug.cgi?id=42005
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #15 from Fabian Maurer dark.shadow4@web.de --- I'm marking this as resolved, there hasn't been discussion for a long time and the original issue is fixed.
https://bugs.winehq.org/show_bug.cgi?id=42005
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org