PlaneShift
Support => Linux Specific Issues => Topic started by: Pirx on March 01, 2008, 10:26:29 pm
-
Hello,
i believe there are some issues with 4.0:
First: the scripts, for instance psclient:
#!/bin/bash
R=$PWD/$0
# this concats the current directory with the path of the script, resulting in something like
# /home/Pirx//opt/Planeshift/psclient
# this should probably read R=$0
R=${R%/*}
# this strips the last component of the path, now we are getting
# /home/Pirx//opt/Planeshift
# it think that should read "/opt/Planshift", one could also use $(dirname $0)
cd $R
# this obviously fails. it works if you do R=$0 above, or cd $(dirname $0)
chmod 770 psclient.bin
# this should not work for ordinary users, because the user playing the game
# should not have write access to the install directory
# the file should be made executable by the installer
export LD_LIBRARY_PATH=libs/:\$LD_LIBRARY_PATH
# ok, i would prefer that the game would use the system libraries,
# but that it should work this way too
exec ./psclient.bin $@
# ok
after fixing the scripts as described above i get:
$ /opt/PlaneShift/psclient
Your configuration files are in... /home/Pirx/.PlaneShift
DEBUG: Sound System Software Renderer Initializing...
planeshift.application.client:
PlaneShift Steel Blue (0.4.00)
This game uses Crystal Space Engine created by Jorrit and others
1.2.0 [Unix-x86-GCC]
315) LOG_ANY flag deactivated with no filter.
...
319) All LOGS are off.
Mounting skin: /this/art/skins/default.zip
432) <src/common/paws/pawsimagedrawable.cpp:56 PreparePixmap>
Speicherzugriffsfehler
-
Okay, I'll fix that script.
The game can't use the system libraries because there's no guarantee they'll be there, or ABI compatible.
I assume that last line means "Segmentation Fault"?
-
Yes it does.
EDIT:
Well, at least this is what is printed on a german version when it would be Segmentation Fault otherwise.
-
yes, segmentation fault. sorry.
i made the install directory writable to the user, and the game started (the login-screen anyway). It created file "errorlog.txt". It probably segfaults if i cannot create that file. so i removed write access again, only left errorlog.txt writable an it still works.
the errorlog.txt should be create in ~./.PlaneShift
Thanks for moving the configuration to the user-dir anyway.
And thanks for the fast replay
there should probably be better checking of return codes of file operations...
-
Okay, I'll look at that now also.
Edit: The code which does that is very old and will need some rewriting to fix properly. I'll make a bug report and hopefully it'll get done soon.
-
I am having similar issues. I modified the startup scripts as described, but I am getting a crash after the splash screen displays and I only get the following error message:
./psclient.bin: symbol lookup error: libs/libvorbisfile.so.3: undefined symbol: vorbis_synthesis_idheader
I have tried disabling sound using pssetup, but I still error out here.
I am running Fedora 7 with the latest 0.4.00 client downloaded today. I was running 0.3.020 previously with no issues. I have tried completely wiping that install and installing clean with 0.4.00 and still have the same issue.
-
I just read on another forum about replacing that file with the .so from my system. That works great.
-
I just read on another forum about replacing that file with the .so from my system. That works great.
yep that is pretty much what I did to fix it.
-
Okay, the issue with the broken shellscript where fixed with the updater and will work for most people I guess, but not for me.
cd ${dirname $0}
I copy the scripts to /usr/bin so I have them in my path automatically (the Arch Linux PKGBUILD does that). So they are not at the orginal place. Why can't the script be like they were in 0.3.020, just changing direct to the directory (/opt/Planeshift normally)? That worked quite well with the last version.
-
Because that means I can't update them. If you want them in your path then just install as root and select the option which will do that for you...
-
Okay I already figured with the update problem since I did all the updates in the last minutes *g*.
But there is a reason why I move files to /usr/bin. I don't see the installer copy any files to $prefix/usr/bin. Am I missing something? I am using the option "--syswide yes" and also tried the GUI installer, just in case it can do something the CL version can't.
EDIT:
I actually thought the wrapper script ARE psclient pssetup and psupdater. These are the ones I copied to /usr/bin since they won't with the installation.
EDIT:
Could it be possible, that the installer doesn't follow the $prefix consequent? If so, this is somewhat of an issue because the prefix is very important to build packages for linux distributions and therefore a clean way to install and uninstall the game through the normal package management. I tested it now with a prefix in my user directory and before with fakeroot and a prefix. Neither way I got any /usr/bin files.
-
It could be that I broke the installer bit which does this and I didn't realise.. I'll look at it for next release.
-
Thank you. It's no showstopper now, so there are more important things to fix, but it would be nice to have a nice way to build packages again.
-
I am having similar issues. I modified the startup scripts as described, but I am getting a crash after the splash screen displays and I only get the following error message:
./psclient.bin: symbol lookup error: libs/libvorbisfile.so.3: undefined symbol: vorbis_synthesis_idheader
I have tried disabling sound using pssetup, but I still error out here.
I am running Fedora 7 with the latest 0.4.00 client downloaded today. I was running 0.3.020 previously with no issues. I have tried completely wiping that install and installing clean with 0.4.00 and still have the same issue.
I have the same problem but on a 32bit system with 32 bit version. Will try to copy there the appropriate lib from my system.
update: It solved my problem, i made a symlink to the appropriate version.
-
Actually there was an update already with a new libvorbis.so. Did you do that update? (sudo psupdater, in game directory)
-
Actually there was an update already with a new libvorbis.so. Did you do that update? (sudo psupdater, in game directory)
That was the first thing i did. After i looked for a fixlibs script :)