Hangs after being launched on Linux/x64

[Seegras]

launcher works, but after clicking "Play", it shows a black screen.

strace reveals it does
write(2, "Got a bad hardware address lengt"..., 55) = 55
ad nauseam.

System is Debian Sid, 64bit (with multiarch support for i386).

[petrucio]

You can try skipping the Launcher by adding --bypass to on Game Properties -> Set Launch Options...

--bypass: Skip the Launcher and go straight into the game
--skipintro: Skips loading and playing Adventurezator's Intro cutscene
-popupwindow: Fullscreen borderless mode

If you use --bypass, use the game's option menu to set the desired resolution and quality options.

Let me know if this helps you.

[Seegras]

Doesn't help.
Here's the whole string: "Got a bad hardware address length for an AF_PACKET 16 8"

I found this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519480

Since this was fixed with the system libraries long ago, I suppose it's actually still present in Adventurezator_Data/Mono/x86_64/libmono.so ? Right now I'm doing some version-replacement game with libmono.so, but so far, no avail.

I found this very file in dozens of steam games for Linux. Where does it come from? Is that some specific porting environment? From steam? From some IDE?

[petrucio]

It's from Mono, the .NET platform that comes with Unity. Most Unity games will carry this.

I'll forward this thread to Unity and see what they have to say about it.

[Seegras]

Interesting. Some of the games using this 64bit library, md5sum 913b2866473f90862420e5257c89f689 exhibit the same error: Adventurezator, Habitat, DreadOut. Others work: Ziggurat, Heldric. Plus I've got some more, with a different md5sum, that also have the same problem. Apparently this only affects 64bit.

[petrucio]

Let me know if today:s update fixed it.

[Seegras]

It behaves differently now. The endless looping error is gone. The cursor doesn't revert to the system cursor; but the screen stays blank:
strace says restart_syscall(<... resuming interrupted call ...>
and ltrace:
gettimeofday(0xd83ade70, 0) = 0
pthread_mutex_lock(0x1e193c8, 0, 0x545c83fd, 0x1e925b5a) = 0
pthread_mutex_unlock(0x1e193c8, 0, 0, 0x1e925b5a) = 0
pthread_mutex_lock(0x1e193c8, 0, 0x1e193c8, 1) = 0
pthread_mutex_unlock(0x1e193c8, 0x1df9070, 0, 1) = 0
gettimeofday(0xd83ade40, 0) = 0
usleep(10000) = <void>
And I think strace is making something bad happen, because if you run ltrace after strace, it crashes.

But I gather the above bug has been fixed.

The problem is now completely somewhere else, I suspect Adventurezator_Data/Plugins/x86_64/libCSteamworks.so

[petrucio]

Ok, thanks for all this, I'll see if I can update lib Steamworks in the near future too to see if it helps. I'm sorry you are unable to play in the meantime.

[Seegras]

No problem. If I really wanted I could run it on wine. But I rather help to get it run on Linux 64bit natively and wait ;)

[Katze]

One question: is this fixed by now?

[petrucio]

There will be an update tomorrow with updated libraries that might fix this, will require additional testing.

[petrucio]

Update is up, please let me know if it fixed it. I'll check with the Unity devs if it doesn't.

(It runs fine on my Ubuntu machine which is also 64 bits, so it doesn't seem to affect everyone)

[Katze]

I do not own your game, but I know other games (Screencheat,Survivor Squad) which are affected by the same problem.


Therefore it would be great if you fixed it, because then they could fix it too.

[Seegras]

sorry, no. "Got a bad hardware address length for an AF_PACKET 16 8"

[petrucio]

Today's update was built with the patch recommended by Unity to fix this issue. Please let me know if it's working now. Thanks.

[Seegras]

Hi. I just saw
http://forum.unity3d.com/threads/linux-64-standalone-got-a-bad-hardware-address-length.282402/ so I thought I need to report back ;).

today:
write(2, "Got a bad hardware address length for an AF_PACKET 16 8", 55) = 55
write(2, "\n", 1) = 1