Jump to content

Welcome to the Forum!

The best place to exchange builds and ideas! Vote for the best ideas and suggestions here.

Join the Avorion Discord!

Connect with other passionate players and talk about the latest news.
Discord

DLC Avorion Into the Rift Out Now!

Now available on Steam!
Steam

Unable to start singleplayer game - Arch Linux (EndeavourOS)


WrenchInThePlan
 Share

Recommended Posts

Upon trying to start Avorion, I can join multiplayer games fine, but I cannot start my own singleplayer game. When I attempt to start a singleplayer game, I get this message:Screenshot_2023-10-13_18-05-32.thumb.png.3434244a0e25c237a65026d8c6726f6f.png

Paste of the client log is here: https://endeavour.kamprad.net/pastebin/?15095a58fba12b30#Eo8JPTLNYwGTDsdufALqYPpWRcAQ6XvFBoXwjRhGoTNK

My OS is EndeavourOS: Build ID: 2023.08.05

My CPU is an Intel Core i7-10750H CPU @ 2.60GHz x 12

My graphics are a Nvidia GeForce GTX 1660 Ti Mobile

I'm running Avorion through Steam.

Link to comment
Share on other sites

  • Boxelware Team

Could you run this in a terminal:

while ! pgrep AvorionServer ; do sleep 1 ; done ; cat /proc/$(pgrep AvorionServer)/maps > avorionserver-maps.txt

and then try to start a game? Afterwards I would need the generated avorionserver-maps.txt and the matching server log from that attempt.

(This essentially waits until an AvorionServer is running and then dumps its memory layout and loaded libraries. pgrep should be part of package procps-ng.)

Link to comment
Share on other sites

  • Boxelware Team

Thanks for providing the files. Sadly this time the server could not start for a different reason:

2023-10-20 09-37-02| ERROR accepting connections: bind: Address already in use

(Either another AvorionServer was still running (or hanning) or you need a bit of pause after a previous attempt. If in doubt, you can try running pkill -9 AvorionServer before starting a new game.)

Can you try again and get me two new files from one attempt where the serverlog contains a stacktrace?

 

Link to comment
Share on other sites

I just tried again, but I've run into a different problem - instead of the game opening when I hit the Play button, I get a message saying "Failed to initialize Steam API, please restart Steam and try again." I've closed and re-opened Steam, uninstalled and reinstalled the game, and restarted my computer, but I still get this message each time.

Link to comment
Share on other sites

  • Boxelware Team

This message suggests that the Avorion process and the Steam Client process are unable to interact with each other properly. Maybe some sandboxing or security feature of your OS is interfering, but I can only speculate. This new problem seems to be clearly outside of Avorion itself.

Link to comment
Share on other sites

I'm also getting a segfault when trying to play a single player game. Also on Arch. I was able to play a few days ago (can't remember exactly when) but can't today. If I switch Steam to offline mode, I can successfully play.

Not sure if there's been a Steam update since I last played. I attempted to roll back to a previous kernel since that has been updated recently, but that didn't help. I could go back as far as 6.5.7.arch1-1 (oldest in my package cache).

avorionserver-maps.txt

serverlog 2023-10-27 18-29-35.txt

Edited by rfvgyhn
Link to comment
Share on other sites

Is it possible the server is trying to use the wrong network interface? I know Elite Dangerous fairly often selects my wireguard interface and I have to manually select the right one (through the in-game settings menu). Does Avorion allow me to manually specify the interface somewhere?

Link to comment
Share on other sites

I'm also running Arch Linux, and Avorion stopped working normally after I updated all packages on the system on Oct 29 (I hadn't upgraded these for a few weeks). I believe I also updated Steam at the same time.

I'm thankfully able to play singleplayer by following @rfvgyhn's tip to use Go Offline in Steam. So yay, I can keep blasting pirates!

Otherwise, when attempting to load a galaxy while steam is in online mode, AvorionServer starts up and crashes within a few seconds with a segfault (SIGSEGV in the server log) and a stack trace (without debug symbols), and sadly the thread that segfaults isn't identified elsewhere in the log.

Key bits from the serverlog (full serverlog attached):

...
2023-11-01 20-49-53| Thread 139661494187712 Received signal SIGSEGV
...
2023-11-01 20-49-53| === STACKTRACE =====================================
2023-11-01 20-49-53| #1: ?? [0xd01781]
2023-11-01 20-49-53| #2: [ext] ?? [0x7f0583a5c710]
...
2023-11-01 20-49-53| #23: [ext] ?? [0x7f0583b2e7cc]
2023-11-01 20-49-53| ===================================================
...

Edit: the first and last addresses in this stack fall within the following ranges from the captured avorionserver-maps.txt (and most of the addresses in the middle fall in ranges for steamclient.so):

7f05839ee000-7f0583a6f000 rw-s 00000000 00:18 551121                     /dev/shm/u1000-Shm_93c3be7d
7f0583a6f000-7f0583c6f000 rw-s 00000000 00:18 507726                     /dev/shm/u1000-ValveIPCSharedObj-Steam

In case it's helpful to pin this down, I cross-referenced the libraries that AvorionServer links against the packages that I upgraded when this stopped working. There were four: glibc, zlib, libx11, and libglvnd.

% while ! pgrep AvorionServer ; do sleep 1 ; done ; cat /proc/$(pgrep AvorionServer)/maps > avorionserver-maps.txt
...
% cat avorionserver-maps.txt | tr -s ' ' | cut -f 6 -d ' ' | sort | uniq | grep /usr | parallel pacman -Qo {}
/usr/lib/libstdc++.so.6.0.32 is owned by gcc-libs 13.2.1-3
...
/usr/lib/libz.so.1.3 is owned by zlib 1:1.3-2
% grep -i graded /var/log/pacman.log | grep 'gcc-libs\|glibc\|libcap\|libglvnd\|libx11\|libxau\|libxcb\|libxdmcp\|systemd-libs\|zlib' | grep -v lib32 | grep 10-29 
[2023-10-29T13:57:42-0600] [ALPM] upgraded glibc (2.38-5 -> 2.38-7)
[2023-10-29T13:57:43-0600] [ALPM] upgraded zlib (1:1.3-1 -> 1:1.3-2)
[2023-10-29T13:57:43-0600] [ALPM] upgraded libx11 (1.8.6-1 -> 1.8.7-1)
[2023-10-29T13:57:44-0600] [ALPM] upgraded libglvnd (1.6.0-1 -> 1.7.0-1)

 

serverlog 2023-11-01 20-49-50.txt avorionserver-maps.txt

Edited by Paeva
updated quoted server log to match the attempt of the avorionserver-maps.txt I'd captured and uploaded both; and added a note about libraries involved in the stack trace
Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

Hi there,

Same problem here but after try to start offline ,Avorion won't start anymore about SteamAPI error.

I hate such errors which only about copyprotection (steam)...

I will keep trying ... 

---

Okay, now i got rid of the steamAPI error (Installed Avorion beta + switching to proton hotfix) and the game starts again.

---

Now i've Avorion Beta installed and if i start the server from shell i can connect to it in the multiplayer menu.:classic_smile:

 


 

Edited by AnnoyedUser
workaround
Link to comment
Share on other sites

  • 2 weeks later...

After switching to proton hotfix, like you suggested, I'm able to start the game as well, both in Beta and on normal version. How do I start a server from shell?

EDIT: Switching Steam to Offline mode worked for me for playing Singleplayer, at least.

Edited by WrenchInThePlan
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...