[A14] LINUX: Game not launching (potential fixes in first post)

Started by deboute, July 15, 2016, 03:46:54 PM

Previous topic - Next topic

deboute

Hi !
thanks again for your hard work i love that game.
Now the hard part, i cannot launch A14 at all under linux.
some context:

  • I'm on debian jessie
  • I can launch A13 without any issue
  • i launch the game, the window opens and the process exits immediately
  • it happens wether i use the sendOwl version or the STEAM version
  • it happens wether i use the start_rimworld.sh shell script or execute the binary directly

Attached are the debug logfile (2017-07-15_deboute_debuglog_A14.log) and a log of calling strace while launching the binary (2017-07-15_deboute_linuxstartup_A14.log)

Thanks again and i hope those harsh hours of steam stampede are not too hard on the team.




UPDATE: potential fix
works for me, your mileage may vary.

i've removed the line with "UnitySelectMonitor" from my ~/.config/unity3d/Ludeon Studios/RimWorld/prefs file and the game launches.

You might just want to remove/backup your ~/.config/unity3d/Ludeon Studios/RimWorld folder and launch the game which will reset everything and launch smoothly.



UPDATE: another fix
tskx has another issue with locales possibly and says in https://ludeon.com/forums/index.php?topic=21450.msg234322#msg234322:
" got it working with »wine-1.9.13 (Staging)« and »winetricks tahoma corefonts« isn't nice but works for now."

[attachment deleted by admin - too old]

SrSalem



milon

I've dropped a note in the Support forum, in the Game Won't Run stickied thread (https://ludeon.com/forums/index.php?topic=4805.msg234223#msg234223).  I can't help with Linux issues, but smarter people than me are aware of the problem.

FYI, we use this thread for in-game bugs.  Keep an eye on the thread I linked because that's most likely where any updates & answers will be.

cyorir



loc978

Same issue, launches with a black screen for a few seconds, then crashes to desktop. I've tried with the standard SendOwl DRM-free download version, and now the native Linux Steam version (debating on trying my Wine Steam install with the Windows version)

System specs for my (repurposed bits of my primary Windows XP gaming machine from 2007) Linux box:

CPU: AMD Athlon64X2 @3.1Ghz
GPU: Nvidia GeForce 7950GT (I think 512MB)
RAM: 4GB @ 800Mhz
HDD: 80GB, 7200RPM, SATA 1.5MBps
Monitor: Sceptre 17" 1280x1024 SXGA LCD from 2004. Just the one.
OS: Linux Mint 17.1 Cinnamon ( v2.4.8 ) 64bit, Kernel: 3.13.0-37 generic

Relevant crash data:
bash-
~/Desktop/Rimworld/RimWorld1234Linux $ ./RimWorld1234Linux.x86_64
Set current directory to /home/locke/Desktop/Rimworld/RimWorld1234Linux
Found path: /home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64
Mono path[0] = '/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux_Data/Managed'
Mono path[1] = '/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux_Data/Mono'
Mono config path = '/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux_Data/Mono/etc'
displaymanager : xrandr version warning. 1.4
client has 2 screens
displaymanager screen (0)(DVI-I-1): 1280 x 1024
Using libudev for joystick management


Importing game controller configs
Aborted

Player.log-
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct null not valid
Stacktrace:


Native stacktrace:

/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux_Data/Mono/x86_64/libmono.so(+0x91772) [0x7fbb82480772]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330) [0x7fbb8769a330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7fbb85e6dc37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7fbb85e71028]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x155) [0x7fbb86778535]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e6d6) [0x7fbb867766d6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e703) [0x7fbb86776703]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e922) [0x7fbb86776922]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt19__throw_logic_errorPKc+0x67) [0x7fbb867c81c7]
./RimWorld1234Linux.x86_64() [0xf02f36]
./RimWorld1234Linux.x86_64() [0xef4f0b]
./RimWorld1234Linux.x86_64() [0xee7549]
./RimWorld1234Linux.x86_64() [0xef37db]
./RimWorld1234Linux.x86_64() [0xe7a225]
./RimWorld1234Linux.x86_64() [0xe76fba]
./RimWorld1234Linux.x86_64() [0x696e7a]
./RimWorld1234Linux.x86_64() [0x7b2e78]
./RimWorld1234Linux.x86_64() [0x789c9d]
./RimWorld1234Linux.x86_64() [0x4686cd]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fbb85e58f45]
./RimWorld1234Linux.x86_64() [0x472889]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

After reading that, I tried it as root... same result, and didn't change the text of the log file.

deboute

Okay guys, i got it !

I renamed ~/.config/unity3d/Ludeon Studios/Rimworld to ~/.config/unity3d/Ludeon Studios/Rimworld_backup and the game launches.
Of course without any preference.
I'll try to move around some old files to see where the issue actually comes from and i'll report here

milon

@deboute, thank you so much!!  Would you also post an update at the link I posted above?  Other folks could benefit from this too.

deboute

Nailed it, it's the ~/.config/unity3d/Ludeon Studios/Rimworld/prefs file that causes the crash.

just remove the line with the "UnityGraphicsQuality" setting from the file and everything will work fine.

alternatively you can backup your ~/.config/unity3d/Ludeon Studios/Rimworld, delete the Rimworld folder and launch the game , it will generate an empty configuration with a working prefs file that you can put in your original folder but you really have to be allergic to editing a simple text file : )

deboute

@milon: right away, i'll make a post in the BLACK SCREEN thread ! could you put FIXED in this topic please ? should i LOCK the thread too ?

loc978

Update: trying to run the Windows Steam version through Wine necessitated a soft reboot. Not recommended.
I had already deleted the ~/.config/unity3d/Ludeon Studios/Rimworld/Config/ folder as per Tynan's troubleshooting instructions... so I went and deleted the entire ~/.config/unity3d/Ludeon Studios/Rimworld/ folder (I have nothing I feel compelled to keep in saves or config) just to see if I could solve it the same way you did, deboute.
Same result as before (both DRM-free and Steam), unfortunately. Exactly the same bash results, but here's the Player.log, just in case the stack trace changed at all:
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_S_construct null not valid
Stacktrace:


Native stacktrace:

/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux_Data/Mono/x86_64/libmono.so(+0x91772) [0x7f431e53a772]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330) [0x7f4323754330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f4321f27c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f4321f2b028]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x155) [0x7f4322832535]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e6d6) [0x7f43228306d6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e703) [0x7f4322830703]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e922) [0x7f4322830922]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt19__throw_logic_errorPKc+0x67) [0x7f43228821c7]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0xf02f36]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0xef4f0b]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0xee7549]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0xef37db]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0xe7a225]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0xe76fba]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0x696e7a]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0x7b2e78]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0x789c9d]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0x4686cd]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f4321f12f45]
/home/locke/Desktop/Rimworld/RimWorld1234Linux/RimWorld1234Linux.x86_64() [0x472889]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================


Side note: launched v1135 just now, to make sure. Still works fine, and it regenerated the config files.

*edit*
tried deleting just the ~/.config/unity3d/Ludeon Studios/Rimworld/prefs file from what was regenerated, same issue. Regenerated it again with v1135, searched it for a "UnityGraphicsQuality" line, but didn't find it.

deboute

@loc978 sorry it does not work for you :( I have no doubt the support team will help you with your bug soon !

let's here it from the others, i wonder if generating a new prefs files works for some people that reported here.

milon

Quote from: deboute on July 15, 2016, 04:43:13 PM
@milon: ... should i LOCK the thread too ?

Your call.  On the one hand, if it's open people can post more questions & fixes.  On the other hand, the Support forum is a better place for this kind of discussion.  Personally I'd leave it open, but that's mostly because I attempt to future-proof by minimizing the number of threads I lock.

Doesn't seem to be fixed for everyone, so I'm not going to tag [FIXED] yet.  But you can too, by editing the subject in your 1st post.  :)

tskx

seams to crash at libmono, every log says:
libmono.so(+0x91772) [0x7ffff352a772]
after that all the logs differ. No idea what that means but in my log there is a part that might help:
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
RimWorldLinux.x86_64: xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

and the part about deleting the unity3d configs does nothing on my end. Is there maybe another dir to delete?

btw. running with:
AMD Phenom(tm) II X6 1090T Processor
[AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] (multi-head with xrandr)