Jump to content

The Linux Thread!


Recommended Posts

Here's a new one, I was going through the logfile looking for errors and I see that it was full of these 3 errors:

Serialization depth limit exceeded at 'ThermalLink'. There may be an object composition cycle in one or more of your serialized classes.

Serialization depth limit exceeded at 'OcclusionData'. There may be an object composition cycle in one or more of your serialized classes.

Serialization depth limit exceeded at 'Contracts.Agents::AgentStanding'. There may be an object composition cycle in one or more of your serialized classes.

These appear to be a unity issue. I fired up a brand new stock version of 1.0.2 and all three of these errors are still all over the logfile. Any clue what these are? I'm running Linux Mint 17.1 64bit.

Link to comment
Share on other sites

Prof_Strangelove, sorry I have no idea what's causing it, have you tried checking for broken packages in Synaptic? There's a filter for it.

Eleven, yeah, those are new for 1.0, they are generated by the heat system and the contracts system respectively, they seem to be harmless though, they probably should have been suppressed as they are unnecessary log writes.

Link to comment
Share on other sites

Eleven, yeah, those are new for 1.0, they are generated by the heat system and the contracts system respectively, they seem to be harmless though, they probably should have been suppressed as they are unnecessary log writes.

Ah k...so everyone is seeing those :)

Link to comment
Share on other sites

Is it possible to specify the location of an alternate glibc?

I am getting the errors

./KSP.x86_64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by ./KSP.x86_64)

./KSP.x86_64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./KSP.x86_64)

I've built newer versions of libc, but specifying LD_LIBRARY_PATH is not changing where KSP is looking for the library (which is in fact out of date on my system and not easy to fix).

Viz:

export LD_LIBRARY_PATH=/opt

shawn@kali:/mnt/win8/Games/KSP_linux$ ldd ./KSP.x86_64

./KSP.x86_64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by ./KSP.x86_64)

./KSP.x86_64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./KSP.x86_64)

__SNIP__

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f85291db000)

But my new libs.so.6 is actually in /opt/lib...

any solutions to this?

Link to comment
Share on other sites

Well, right at the top e have this:


(process:13590): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed

And further down this:


FMOD failed to get number of drivers ... File not found.

So it looks like you're missing some libraries that KSP needs, open a terminal and run the ldd commands from the previous link, they will say if a library is missing or an incorrect version.

Edit:

kiwiak you're using a 1.0.0 settings.cfg on 0.90, delete your settings.cfg and try again.

Edited by sal_vager
Link to comment
Share on other sites

Firefox doesn't write to the KSP logs though, you have a 1.0.0 settings.cfg yet your logs say you are playing .90, that will cause things to break.

Edited by sal_vager
Link to comment
Share on other sites

Curious question to the other Linux users out there.

Is anyone else seeing higher CPU loads with KSP 1.0.2?

I've been playing since 0.25 and never had issues with overheating, but suddenly I'm locking up left and right.

Watching KSP in top, I see CPU usage at something like 200%. My temps idle around 45, but get to 70 while still in the main menu.

Sometimes I can only play for 5 minutes, but sometimes for an hour. I can't make sense of it, but 0.90 definitely didn't do this to me, modded or unmodded.

Just wondering if I'm the only one noticing higher CPU usage.

EDIT: Somewhere between reinstalling KSP, reinstalling Nvidia 331 (from 349) drivers, and changing the x86_64 offsets per soulsource, my thermal issues went away, as did my lockups.

Edited by amo28
Link to comment
Share on other sites

I managed to fix my problem, yay ! Turns out I needed to install the libwnck-3-0 package to fix a gnome-panel crash. Works flawlessly now !

Excellent news Prof_Strangelove, I don't use Gnome panel here so would never have spotted this one, I'll add your findings to the opening post so it can help others.

Link to comment
Share on other sites

I think I found the offsets for the memory addressing issue in 1.0.2 64bit, but as I haven't tested them thoroughly, they could in principle

...

Please be aware, that I won't take responsibility for any damage done by relying on these values. As said, I'm not absolutely certain that they are correct.

008ab803

008ab808

Link to comment
Share on other sites

I think I found the offsets for the memory addressing issue in 1.0.2 64bit, but as I haven't tested them thoroughly, they could in principle
...

Please be aware, that I won't take responsibility for any damage done by relying on these values. As said, I'm not absolutely certain that they are correct.

008ab803

008ab808

Worked for me. Thanks very much.

Link to comment
Share on other sites

Nice work soulsource, I've updated the first post :)

Can anyone find the new values for gerners fix for Intel card shadows?

I used to do this fix, but it was unreliable after a short time, for several releases now I have just used a hex editor, found the very first instance of "Intel" and zeroed it out. After that, Bam!, aerodynamic effects and shadows on my laptop :)

I used to zero out all three "Intel"s but on one release, I think it 0.25 it caused the game to slow down...after that, I started doing just the first one.

Link to comment
Share on other sites

You are amazing Eleven, have I told you that? :D

lol actually, if you look one fix lower than where you just credited me, diego_gz's fix for 'no hardware support button' is what I used. I believe those two issues are one and the same, even though at one point there were two different fixes. At least that's the case for me and my laptop. I've had 2 different CPUs in it, an i3 and i5, and just using diego_gz's fix enabled aerodynamic effects and shadows for me.

So...I don't get the credit, I may have just stumbled into realizing that one fix solved two problems :)

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...