protonscr

IP-based IPC prevents running Steam under linux alongside Steam under WINE.

steamopen reviewed
ValveSoftware/steam-for-linux#4264 · opened 2016-01-16 by KingBowser · updated 2019-07-18 · 4 comments · github
KKingBowser 2016-01-16 github

Scenario:

  • I own borderlands and want to run it under linux.

Solution:

  • borderlands will run under wine
  • steam will run under wine

Roadblock:

  • running steam under wine results in steam for linux disconnecting from steam

Why is this a problem:

  • the webkit library used in steam is not functional under wine, and therefore steam for windows under wine may only launch games and chat.

Temporary solutions:

  • install all desired windows games and run steam in offline mode, therefore preventing you from receiving achievements, cards, playtime, etc...

Demo: https://youtu.be/VlFml8oEifg

From what I have read, this was a non-issue for some time, after which it came to be an issue.

The only way this could be happening were if both processes intended to open the same port on the same interface. netstat output supports my theory:

tcp        0      0 0.0.0.0:27036           0.0.0.0:*               LISTEN      24044/steam         
tcp        0      0 127.0.0.1:57343         0.0.0.0:*               LISTEN      24044/steam         
udp        0      0 0.0.0.0:41524           0.0.0.0:*                           24044/steam         
udp        0      0 0.0.0.0:27036           0.0.0.0:*                           24044/steam
JJoshuaMurphynz 2016-01-16 github

So what are you proposing valve should do?
On 16 Jan 2016 17:30, "Bowser" [email protected] wrote:

Scenario:

  • I own borderlands and want to run it under linux

Solution:

borderlands will run under wine

steam will run under wine

Roadblock:

  • running steam under wine results in steam for linux disconnecting
    from steam

Why is this a problem:

  • the webkit library used in steam is not functional under wine, and
    therefore steam for windows under wine may only launch games and chat

Temporary solutions:

  • install all desired windows games and run steam in offline mode,
    therefore preventing you from receiving achievements, cards, playtime, etc

Demo: https://youtube/VlFml8oEifg

From what I have read, this was a non-issue for some time, after which it
came to be an issue

The only way this could be happening were if both processes intended to
open the same port on the same interface netstat output supports my
theory:

tcp 0 0 0000:27036 0000:* LISTEN 24044/steam
tcp 0 0 127001:57343 0000:* LISTEN 24044/steam
udp 0 0 0000:41524 0000:* 24044/steam
udp 0 0 0000:27036 0000:* 24044/steam

—
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4264.

KKingBowser 2016-01-16 github

I would suggest using a different transport layer for IPC, such as sockets, as they are far better suited to this sort of thing anyways.

Mmajor-gnuisance 2016-04-08 github

As long as this problem persists, you could try working around it using Linux network namespaces.

Iivan 2017-05-06 github

Steam listening on port 57343 is also a bad idea because it's inside Linux's default ephemeral port range of 32768 - 60999 (inclusive) and also inside Windows' default ephemeral port range of 49152 - 65535 (inclusive). Another TCP connection can tie up the port and prevent Steam games from starting.

Upstream links