Introducing Borderlands 2 Linux!

[Aspyr-Blair]

Aspyr is extrememly proud to announce our second Linux effort on one of the most fun games we've ever had the pleasure to work on, Borderlands 2. This SteamOS release includes ALL released DLC.

We are targeting SteamOS and Ubuntu 14.04 support, but we absolutely need feedback on what you Vault Hunters are seeing in the wild wild world of Linux distros. So please chime in here and let us know!

Please note that we are currently only supporting NVIDIA GPU chipsets, and while we continue to work hard on supporting both ATI and Intel (just as we do on the Mac) the experience on those chipsets is currently not something we can support as gamers.

[FoolishOwl]

de.nagicallinux eredeti hozzászólása:

Well, then you could try

env SSL_CERT_DIR=/etc/pki/tls/cert strace -f -e file ./Borderlands2 &> strace.log

from within the games directory and then look in the trace file for that cert/an error.

Shift still works for my gentoo box.

There's a complication. I actually need to use the Bumblebee drivers to get my graphic card to work with most games; the actual "launch option" string I use to run Borderlands 2 is

SSL_CERT_DIR="/etc/pki/tls/certs" primusrun %command%.

I tried to figure out how to adjust the command line accordingly, and my best guess was

env SSL_CERT_DIR=/etc/pki/tls/cert primusrun strace -f -e file ./Borderlands2 &> strace.log

However, it exits after a few seconds, with an error message about a core dump. strace.log doesn't have any reference to cert, crt, or pem; I don't think it gets nearly far enough to try.

Note: Borderlands 2 runs just fine on my system with the settings I'm using, except it won't connect to SHIFT.

[de.nagical[linux]]

FoolishOwl eredeti hozzászólása:

de.nagicallinux eredeti hozzászólása:

Well, then you could try

env SSL_CERT_DIR=/etc/pki/tls/cert strace -f -e file ./Borderlands2 &> strace.log

from within the games directory and then look in the trace file for that cert/an error.

Shift still works for my gentoo box.

There's a complication. I actually need to use the Bumblebee drivers to get my graphic card to work with most games; the actual "launch option" string I use to run Borderlands 2 is

SSL_CERT_DIR="/etc/pki/tls/certs" primusrun %command%.

I tried to figure out how to adjust the command line accordingly, and my best guess was

env SSL_CERT_DIR=/etc/pki/tls/cert primusrun strace -f -e file ./Borderlands2 &> strace.log

However, it exits after a few seconds, with an error message about a core dump. strace.log doesn't have any reference to cert, crt, or pem; I don't think it gets nearly far enough to try.

Note: Borderlands 2 runs just fine on my system with the settings I'm using, except it won't connect to SHIFT.

Ok, let me nitpick a bit: primusrun seems to be deprecated in favour of optirun -b primus, and both might yield different behavior (though, not sure if that holds in your case)

You can also use /etc/ssl/certs since it seems to be symlinked to the proper directory.

Not quite sure either, on how to use strace with optirun. Maybe env SSL strace -f -e ... optirun ./Borderlands2? Or if the integrated cards can handle OpenGL3 you could just test the network stuff with the integrated one.

Or you could use:

openssl s_client -connect 54.210.24.108:443

to test if your openssl is actually able to use the shift login server. Though there's still a possibility the game's libraries behave differently (which would need a 32bit openssl binary to verify :/)

[FoolishOwl]

I found a modified workaround. (Anyone who finds this through a search, please note I'm using Fedora 21, and read the last few posts.) Some more experimenting led me to this:

% grep cert strace.log
[pid  6527] open("/usr/lib/ssl/cert.pem", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
[pid  6527] stat64("/etc/pki/tls/certs/2c543cd1.0", 0xfff75620) = -1 ENOENT (No such file or directory)

So I added a symlink to 2c543cd1.0, the way I'd previously had one for 157753a5.0.

% sudo ln -s /etc/pki/tls/cert.pem 2c543cd1.0

And then I could authenticate with SHIFT. So I'm wondering if they switched TLS cert providers, or some such.

Some other details: I hadn't created a symlink for /usr/lib/ssl, which is the solution others recommend, and it looks like Borderlands2 still checks for /usr/lib/ssl/cert.pem, regardless of the environment setting. So perhaps doing that would be more robust.

Also, I noticed that Borderlands2 kept crashing when I tried to launch it from the command line, but I was able to insert the strace command into "launch options", and that worked -- with the caveat that it didn't work with '&> strace.log', which I had to replace with '> strace.log 2>&1', so my full "launch options" (note: for debugging purposes) were this:

SSL_CERT_DIR="/etc/pki/tls/certs" primusrun strace -f -e file %command% > strace.log 2>&1

So I'm guessing that Steam does more to modify the environment, perhaps to resemble the typical Ubuntu environment, which is why I couldn't launch Borderlands2 from the command line. Also, it's not launching a BASH shell, but something more restricted, which is why '&> strace.log' didn't work.

Finally, de.nagical[linux], I'm not sure why you're suggesting 'primusrun' is deprecated, since both the Bumblebee and primus projects suggest using it, and neither says anything about it being deprecated.

[de.nagical[linux]]

FoolishOwl eredeti hozzászólása:

I found a modified workaround. (Anyone who finds this through a search, please note I'm using Fedora 21, and read the last few posts.) Some more experimenting led me to this:

% grep cert strace.log
[pid  6527] open("/usr/lib/ssl/cert.pem", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
[pid  6527] stat64("/etc/pki/tls/certs/2c543cd1.0", 0xfff75620) = -1 ENOENT (No such file or directory)

So I added a symlink to 2c543cd1.0, the way I'd previously had one for 157753a5.0.

% sudo ln -s /etc/pki/tls/cert.pem 2c543cd1.0

And then I could authenticate with SHIFT. So I'm wondering if they switched TLS cert providers, or some such.

Some other details: I hadn't created a symlink for /usr/lib/ssl, which is the solution others recommend, and it looks like Borderlands2 still checks for /usr/lib/ssl/cert.pem, regardless of the environment setting. So perhaps doing that would be more robust.

Also, I noticed that Borderlands2 kept crashing when I tried to launch it from the command line, but I was able to insert the strace command into "launch options", and that worked -- with the caveat that it didn't work with '&> strace.log', which I had to replace with '> strace.log 2>&1', so my full "launch options" (note: for debugging purposes) were this:

SSL_CERT_DIR="/etc/pki/tls/certs" primusrun strace -f -e file %command% > strace.log 2>&1

So I'm guessing that Steam does more to modify the environment, perhaps to resemble the typical Ubuntu environment, which is why I couldn't launch Borderlands2 from the command line. Also, it's not launching a BASH shell, but something more restricted, which is why '&> strace.log' didn't work.

Finally, de.nagical[linux], I'm not sure why you're suggesting 'primusrun' is deprecated, since both the Bumblebee and primus projects suggest using it, and neither says anything about it being deprecated.

Glad you could resolve the issue, or lets call it work around it. Probably the game's libraries aren't able to load the cert bundles or something in that way. I don't have /usr/lib*/ssl or a single cert bundle, so it's probably not more robust to symlink that file. The distributed libcrypto seems to look into:

/usr/lib/ssl/private
/usr/lib/ssl
/usr/lib/ssl/certs
/usr/lib/ssl/cert.pem

If you have a system openssl 1.0.0 to <1.0.2 it should be possible to use those. Unfortunately, 1.0.2 fails due to a steam bug.

Steam launches a subshell for the game (I noticed because of the lobby join bug):

[pid 30566] execve("/bin/sh", ["/bin/sh", "-c", "+connect_lobby 12345678910 env SSL_CERT_DIR=/etc/ssl/certs \"$INSTPATH/Borderlands 2/./Borderlands2\""]

We should probably note, that /bin/sh is also system specific symlinked...

env SSL_CERT_DIR=/etc/ssl/certs strace -f -e file %command% &> /tmp/bl.log

works for me (with /bin/sh -> bash)

[pid  3548] open("/etc/ssl/certs/2c543cd1.0", O_RDONLY|O_LARGEFILE) = 171

It opens cert "2c543cd1.0" three times.

And about primusrun: "[..] We do not depend on primusrun script anymore for primus backend, note that primusrun and optirun -b primus will have different behavior [..]"[github.com]. Though it seems to be an enhancement to not use it anymore.

May I still ask, if the openssl s_client command, I posted in an earlier comment, did work without the symlinks?

[Sinedio]

Is there any news regarding the patch which allows us to bind more mouse buttons? (like buttons 4 and 5 which are usually thumb buttons)

[Katrina Bekers]

AFAIK, it's already in.

I can recharge ammo with my first thumb button now.

[Sinedio]

Did you "import" your files from Windows? That may explain why the buttons work.

When I try to bind my thumb buttons to anything it does not work. Also, I can't bind the Ctrl key to "Crouch" either. These are both problems the game originally had.

[Katrina Bekers]

No, I didn't. Original installation only on Linux.

Yep, at first it had the problem, I remember that. But nowadays it works, don't remind since which patch.

[librin.so.1]

@Katrina Bakers

1. I don't remember there being a single update since Linux release. (and thus, if my memory serves me right, "since whitch patch" is not applicable)
2. I re-tested moments ago, just in case. Nope, still can't bind mouse keys 4 and 5

[FoolishOwl]

de.nagicallinux eredeti hozzászólása:

May I still ask, if the openssl s_client command, I posted in an earlier comment, did work without the symlinks?

It did.

Also, while I now initially connect to SHIFT, and get a list of all the awards I've claimed, when I try to claim a SHIFT code, I eventually get an error message that it isn't possible to claim it. Perhaps this is because there haven't been any new codes since February, and I've already claimed them, but in the past that gave me a specific error that I'd already claimed it.

[Sinedio]

Katrina Bekers eredeti hozzászólása:

No, I didn't. Original installation only on Linux.

Yep, at first it had the problem, I remember that. But nowadays it works, don't remind since which patch.

Are you sure it's Borderlands 2 you're talking about and not the Pre-Sequel? Because that one does not have this problem.

[Katrina Bekers]

Sinedio eredeti hozzászólása:


Are you sure it's Borderlands 2 you're talking about and not the Pre-Sequel? Because that one does not have this problem.

Pffft, may I show you an idiot? That's me, pleased to meet you! :P

I mixed and matched BL2 and TPS - just checked, in TPS it works (btn4 & 5), in BL2 it doesn't

My bad

[GIGA PUDDING]

Thanks

[uNLuckyBOY]

Trade gift Borderlans 2!!!

[Corben]

Recently Borderlands 2 creates a core dump file on my system in steamapps/common/Borderlands 2/steamassets/binaries/win32 when exiting the game.
If that file exists, the game won't start anymore. Deleting it helps.
That problem is new, as it worked normally weeks ago.
I'm running Ubuntu 14.04 LTS (german) on a Intel Q9550 with nVidia GTX 670 and 349.16 proprietary drivers.
Any suggestions, or should I send in the ~1 GB core file?