https://bugs.winehq.org/show_bug.cgi?id=46704 --- Comment #27 from Jonathan Preston <jpreston(a)jpreston.net> --- I made some progress, I think. I am now able to successfully log in in all cases, assuming the game launches to the login screen (which it doesn't about 50% of the time, but I think that's an unrelated issue). Essentially, what I did is bypass systemd-resolved. To reproduce the "solution" on Ubuntu 18.04 (assuming you are already impacted by this issue): 1. Tell Network Manager not to manage our resolv.conf by editing /etc/NetworkManager/NetworkManager.conf, and adding the following line to the [main] section: dns=none 2. Restart Network Manager: systemctl restart network-manager 3. Now remove symlinked resolv.conf that is part of systemd: rm /etc/resolv.conf 4. Create a new resolv.conf with your text editor of choice and add the following line: nameserver 8.8.8.8 5. Restart Network Manager again. To revert the changes: Remove the line "dns=none" from /etc/NetworkManager/NetworkManager.conf rm /etc/resolv.conf ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf systemctl restart network-manager I'm not exactly sure why this works, but it does work on the one system I've tried it on, and the problem returned immediately when I reverted the changes. Naturally, I do not recommend this approach as a permanent workaround, as local DNS caching is generally good. Hopefully this is helpful information. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.