Register
Events
Popular
More
Post #1
I see the game client finally loads in Linux but there hasn't been any servers in the list and the console just says "Need Steam to refresh servers!". I'm seeing all kinds of great things in the playrust blog/etc but can't see any of it for myself because I'm in Linux :(
-
-
Why does the forum seem to think that you're on Win7?
-
Because I'm using a user-agent override (lets me watch Netflix with Pipelight)
-
Interesting... I was just curious. I always wanted a way to watch Netflix on Linux. Thanks!
-
lol Its a bit off topic, but yea look up how to install "Pipelight" on your distro. Then just use a user-agent override to get past the unsupported OS message.Interesting... I was just curious. I always wanted a way to watch Netflix on Linux. Thanks!
BTW, are you using Linux right now? Seeing same problem with experimental branch of Rust?
-
No, I haven't even tried getting into the exp branch yet, much less on Linux. Kind of holding off on Rust until the exp branch is either very close to done or switched to production.
I usually have Fedora or Ubuntu on dual-boot but I recently wiped my PC and haven't taken the time to set it all back up yet, really just a fun side project for me to learn.
Also I'm on my work PC... games on this would not bode well with Meraki breathing down my neck all day.
-
I'm a distro hopper myself. I usually end up back in Ubuntu though. Lately I keep going to SteamOS and Manjaro to check on their progress. But I've been hopping around for about 14 years (I remember the early Red Hat back when it was free). Ubuntu appears to have the best support all around. I depend on Steam for my games now. So far I'm much more pleased with the overall system stability compared to my old Windows setup. In Linux an application rarely causes a systemwide crash. Its almost always recoverable if something goes wrong. If something goes wrong in Windows... hang on to your butts.
-
I'm still having the same problem when loading the experimental branch in Linux. The client loads up but the servers still can't be refreshed properly. Console still says I need Steam. Any progress on this bug?
-
I also have the same problem. I'm running Arch Linux 64 bit and I can play the production branch just fine. F1 pops up the console that just says "rust. Need Steam to refresh servers!" and none of the tabs will have any servers on the list. It also says "REFRESHING..." at the bottom with no change.
-
I have the same issue on 64 bit Arch Linux.
I tried putting the app id in the rust folder, to no avail. Perhaps we can join directly if someone could share the ip of an experiemental server that was joined from a different OS.
Either way, this appears to be an issue with rust and the steam api/runtime on linux.
-
The issue here is with the location of the SteamNative library. If you can do some research and find out why it's not finding it, or why it's not loading it.. that will help me out a lot
-
We're on it, boss.
Linux user power activate!
-
Seems that rust doesn't play well with gdb. How unfortunate.
A quick scan for steam related libaries being loaded by rust revealed only this:
/opt/SteamApps/common/rust/rust_Data/Managed/System.Runtime.Serialization.dll
For clarity, /opt is where my steam library resides. Anyway, this probably doesn't show us much. Must keep searching.
Off topic: It seems that the 64 bit client of rust for linux is "working" now, unlike before.
-
That is what I get in my log when is start rust.x86 -logFile:
I made a symbolic link of /home in "rust_Data/Mono/x86_64" in such a way that /home/xavier/.local/share/Steam/SteamApps/common/rust/rust_Data/Mono/x86_64/.//home/xavier/.local/share/Steam/SteamApps/common/rust/rust_Data/Plugins/x86/libSteamNative.so would exist but is still not loaded by rust :(
-
Maybe I've solved this. The libsteam_api.so library is 64-bit (as ldd shows long addresses) while Rust always run as 32-bit. I use Debian Jessie amd64 but Steam always run rust.x86 no matter what. So it just can't load the library. I copied this file from Painkiller Hell & Damnation (32-bit version) and servers have shown up. The game freezes on connect (unsurprisingly, since it's a crude hack; the same library from another game causes crash on launch and all these libs have different sizes) but at least it's something. I can run rust.x86_64 manually but it also doesn't show servers because it can't find the Steam runtime. There are ways of running games with the runtime manually but I'm too lazy to check them out. Anyway, the solution is simple: either replace the library with a 32-bit counterpart or make a short script to detect the arch and run the appropriate executable. And move the library somewhere like rust_Data/Plugins/<arch> or such.
-
agreed. linked libsteam_api.so from Portal 2 and it showed servers for me as well-
-
FWIW, renaming (or linking) rust.x86_64 to rust.x86 doesn't solve anything. It runs fine from Steam but servers aren't shown and the message about Steam is there. It's like it can't load this exact library no matter what. I'm trying other versions from other games, some of them crash Rust, some work to the said extent (the game freezes on connect anyway). Well, that's a start.
-
Found this in ~/.local/config/unity3d/Facepunch Studios/PlayRust/Player.log (edited to simplify paths):
Which seems to confirm Gary's post, I think. On my system, there is no libsteam.so at that location, but copying it there did not make a difference.Code:dlopen failed trying to load: ~/.local/share/Steam/linux32/libsteam.so with error: ~/.local/share/Steam/linux32/libsteam.so: cannot open shared object file: No such file or directory
I tried copying libsteam.so into the same folder as rust but that didn't made a difference either.
I still have some more things to try.
EDIT: Didn't see the last few posts at the time I wrote this.
-
The right path should be ~/.config/unity3d/Facepunch Studios LTD/Rust/Player.log
BTW, there's a real mess with architectures there. rust_Data/Plugins/x86_64/libSteamNative.so and rust_Data/Plugins/x86/libSteamNative.so are identical and both 32-bit. That's probably why the 64-bit version doesn't show servers either. I do:
Then launch it via Steam. Lots of lines:Code:mv rust.x86 rust.x86.bak ln -s rust.x86_64 rust.x86
Can't say for sure but I doubt that a 32-bit library can be loaded by a 64-bit process.Code:Fallback handler could not load library /opt/SteamLinux/SteamApps/common/rust/rust_Data/Mono/x86_64/.//opt/SteamLinux/SteamApps/common/rust/rust_Data/Plugins/x86_64/libSteamNative.so Fallback handler could not load library /opt/SteamLinux/SteamApps/common/rust/rust_Data/Mono/x86_64/lib/opt/SteamLinux/SteamApps/common/rust/rust_Data/Plugins/x86_64/libSteamNative.so Fallback handler could not load library /opt/SteamLinux/SteamApps/common/rust/rust_Data/Mono/x86_64/./lib/opt/SteamLinux/SteamApps/common/rust/rust_Data/Plugins/x86_64/libSteamNative.so Fallback handler could not load library /opt/SteamLinux/SteamApps/common/rust/rust_Data/Mono/x86_64/lib/opt/SteamLinux/SteamApps/common/rust/rust_Data/Plugins/x86_64/libSteamNative.so
-
Does not work for me. Using Ubuntu 12.04 32bit
-
I had both Facepunch Studios and Facepunch Studios LTD. The LTD folder was older, so I ignored it.
For anyone moving, copying, and/or linking to launch 64 bit rust on steam, you can instead set the launch options for rust within steam to:Code:%command%_64
So the overall issue seems simple:
libsteam_api.so is 64 bit, libSteamNative.so in x86_64 is 32 bit (I know other people in this thread found this first, I am just confirming). That explains why it won't work. When using 32 bit rust, libsteam_api.so is not compatible. When using 64 bit rust, libSteamNative.so is not compatible. This is probably a relatively quick fix for Facepunch, possibly just need to adjust some build scripts.
-
Sounds simple enough. Now to wait for Garry to investigate further. Maybe we'll finally get to play with experimental in Linux soon. Or at least be one step closer to it :)
-
I posted this in the bug reports forum just before the responses started coming in. I've done some poking around as well and I'm anxiously waiting to see when this will be fixed.
-
I'll get on this today
-
A bit disappointed that the person who just summed up what I found got all the recognition... Good news that it's being worked on though.
-
I threw some new x64 dlls on, let me know if it's any better
-
Did a fresh install of Rust experimental via Steam. Still unable to refresh servers. Linking Portal 2 libsteam_api.so helps but the game still crashes on connect.
-
Still no servers.
-
libsteam_api.so is still 64-bit without alternatives. libSteamNative.so has proper versions now but without appropriate libsteam_api.so it's a no go anyway.
-
Rust 64 bit shows servers now. Because my internet is not the greatest, I cannot test further at the moment. I will test 32 bit in a minute, but I don't think it will work since libsteam_api.so is still only found in 64 bit, as far as I can tell.
EDIT: Just confirmed that 32 bit has the same symptoms as before. Which I don't mind so much because everyone with the capable hardware should probably use 64 bit anyway...but it should still be fixed.
Also, I never wanted to make it seem like I am trying to steal the show from rkfg. We had the same conclusions and (s)he deserves credit too.
-
64-bit version now shows the server but crashes on connect. 32-bit version doesn't show anything as it was before. Here's the log, it's too huge to post as plaintext: http://www.mediafire.com/download/np...n579/player.7z I symlinked the 64-bit binary to rust.x86.
-
When running as 64bit I also get some servers on the list. It says it finds 5 servers but only 1 shows up under the Community tab and 4 under History (these may be the servers that I logged into on the production branch?). Hitting refresh gets it stuck again where no servers show up at all. If I try to log into any of the 5 listed servers, the game crashes.
-
Strangely I have the same error than you on Ubuntu 12.04 32bits and Ubuntu 14.04 64bits
I also get those messages several times (on 64bits):
Code:Fallback handler could not load library /home/xavier/.local/share/Steam/SteamApps/common/rust/rust_Data/Mono/x86_64/CoherentUI_Native Fallback handler could not load library /home/xavier/.local/share/Steam/SteamApps/common/rust/rust_Data/Mono/x86_64/libCoherentUI_Native.so
-
Those seem to be common since the build is still broken. If I understand the traceback right, it has an over the top level recursion, so that may be the culprit. The game overflows the stack and then crashes.
-
I am surprised that you don't get the same error on 64 bits
-
I am also running 64 bit Arch Linux and both 32 and 64 versions of Rust are crashing with same errors for me. Here is my Player.log: https://www.dropbox.com/s/61ho1skegkkjzid/Player.7z
It does the same whether I start rust manually or through Steam, with or without STEAM_RUNTIME disabled.
Edit: I should mention that after one of the updates today the 64-bit version ran and displayed the server list but crashed upon trying to connect. The next update broke everything.
-
Wow, wow, wow. The game crashes now when the white screen appears (core dumped)
-
I don't know if this is somebody else's case but now (after the last update) I can pass the white screen crash yet it freezes when the background (the trees in the night) shows up. I am waiting for the menu but nothing. The CPU is at 32% and the used memory is the same. Also, I see that rust.x86 is started when clicking PLAY in Steam, when my computer has 64-bits architecture. Anyway, no matter which of them I click and even with the lowest settings it still hangs at the 'after-white screen' step. No error in the console. The errors.html is this:
Code:DllNotFoundException: CoherentUI_Native Coherent.UI.CoherentUI_NativePINVOKE+SWIGExceptionHelper..cctor () Rethrow as TypeInitializationException: An exception was thrown by the type initializer for SWIGExceptionHelper Coherent.UI.CoherentUI_NativePINVOKE..cctor () Rethrow as TypeInitializationException: An exception was thrown by the type initializer for Coherent.UI.CoherentUI_NativePINVOKE Coherent.UI.MouseEventData..ctor () CoherentUISystem..ctor () NullReferenceException: Object reference not set to an instance of an object BaseHTMLComponent.Start ()
-
I think it is related to the new HTML UI, sounds like they are having issues with it on Mac, too: https://trello.com/c/hS0dEGpb
Edit: I can confirm same errors in errors.html. Steam reports binary missing but when launching the 'rust' binary it passes the white screen and crashes on loading the background.
Updated Player.log: https://dl.dropboxusercontent.com/u/1289622/Player.7z
errors.html: https://dl.dropboxusercontent.com/u/1289622/errors.html
-
Same here. Also, the launch config is broken, the binary is now named "rust" (without the arch suffix, and it's 64-bit) and Steam possibly tries to run rust.x86 so I made a symlink. By default I get "missing executable". Log contains this in the end:
Code:NullReferenceException: Object reference not set to an instance of an object at BaseHTMLComponent.Trigger (System.String name) [0x00000] in <filename unknown>:0 at ConsoleHTML.Update () [0x00000] in <filename unknown>:0 (Filename: Line: 4294967295) NullReferenceException: Object reference not set to an instance of an object at BaseHTMLComponent.Trigger (System.String name) [0x00000] in <filename unknown>:0 at ConsoleHTML.Update () [0x00000] in <filename unknown>:0 (Filename: Line: 4294967295)
Informative x 2
Agree x 2
Funny x 2
Useful x 1
Winner x 1
Dumb x 1
