FOF, Linux - LINUX
Forum rules
- Before posting in this section please make sure your question has not already been answered:
- Read the FAQs and stickied topics. In particular: /******READ THIS POST BEFORE POSTING IN THIS SECTION!******\
- Visit the Wiki: http://fretsonfire.wikidot.com/
- Please try to search the forums before posting
- Questions about FoFiX?
- For general help, visit the project's Wiki: http://code.google.com/p/fofix/w/list
- Problem running FoFiX from git? Ask ALL your questions in the FoFiX forum
This topic is 18 years and 1 month old. Instead of replying, please begin a new topic, or search for another related topic that may be more suitable.
root@pedrotski-linux:/home/pedrotski# '/home/pedrotski/Desktop/FretsOnFire/FretsOnFire.bin'
Traceback (most recent call last):
File "/home/skyostil/src/cx_Freeze-3.0.3/initscripts/Console.py", line 27, in ?
File "src/FretsOnFire.py", line 27, in ?
File "src/GameEngine.py", line 34, in ?
File "src/Data.py", line 25, in ?
File "src/Svg.py", line 39, in ?
File "src/Log.py", line 55, in <lambda>
File "src/Log.py", line 50, in log
LookupError: unknown encoding: iso-8859-1
root@pedrotski-linux:/home/pedrotski#
Traceback (most recent call last):
File "/home/skyostil/src/cx_Freeze-3.0.3/initscripts/Console.py", line 27, in ?
File "src/FretsOnFire.py", line 27, in ?
File "src/GameEngine.py", line 34, in ?
File "src/Data.py", line 25, in ?
File "src/Svg.py", line 39, in ?
File "src/Log.py", line 55, in <lambda>
File "src/Log.py", line 50, in log
LookupError: unknown encoding: iso-8859-1
root@pedrotski-linux:/home/pedrotski#
I have the exact same problem - but it doesn't matter which directory I run from. Same set of messages:
Furthermore, I tried to download the sources from the FoF homepage with the vague idea of trying to find the problem myself - but the gzipped tarball is actually a gzip of an HTML file of some kind - no sourcecode in sight. The ZIP file comes up with some kind of 404 error in some non-english language that I don't recognise.
Help?!
Code: Select all
fof/FretsOnFire> ./FretsOnFire
Traceback (most recent call last):
File "/home/skyostil/src/cx_Freeze-3.0.3/initscripts/Console.py", line 27, in ?
File "src/FretsOnFire.py", line 27, in ?
File "src/GameEngine.py", line 34, in ?
File "src/Data.py", line 25, in ?
File "src/Svg.py", line 39, in ?
File "src/Log.py", line 55, in <lambda>
File "src/Log.py", line 50, in log
LookupError: unknown encoding: iso-8859-1
Furthermore, I tried to download the sources from the FoF homepage with the vague idea of trying to find the problem myself - but the gzipped tarball is actually a gzip of an HTML file of some kind - no sourcecode in sight. The ZIP file comes up with some kind of 404 error in some non-english language that I don't recognise.
Help?!
3D_geek wrote:Furthermore, I tried to download the sources from the FoF homepage with the vague idea of trying to find the problem myself - but the gzipped tarball is actually a gzip of an HTML file of some kind - no sourcecode in sight. The ZIP file comes up with some kind of 404 error in some non-english language that I don't recognise.
Download it from the SourceForge project page.
Frets on Fire game tester
-
- Member
- Posts: 1
- Joined: February 13th, 2007
- Reputation: 0
Hi all,
I have the exact same problem and it seems that there is a lot of missin python packages.
The only thing I found was that in rder to make it..work, Python has to be able to decode unicode types (ISO)
I tried to make default ISO in etc/python/2.x/site.py but it doesn't seem to work neither.. I just feel stuck !
Has anybody found a way to solve this ?
I have the exact same problem and it seems that there is a lot of missin python packages.
The only thing I found was that in rder to make it..work, Python has to be able to decode unicode types (ISO)
I tried to make default ISO in etc/python/2.x/site.py but it doesn't seem to work neither.. I just feel stuck !
Has anybody found a way to solve this ?
Welle well,
Solved it with another lauching method and after installing python-pygame :
Solved it with another lauching method and after installing python-pygame :
Code: Select all
sh FretsOnFire
-
- Member
- Posts: 1
- Joined: March 12th, 2007
- Reputation: 0
This is how I solved the "LookupError: unknown encoding: iso-8859-1" problem in Ubuntu Edgy:
gave me
Next
That's it!
So, basically, try "export LANGUAGE=x.ISO-8859-1:y:z", where x,y and z are the values of your environment variable LANGUAGE. Remember to write down the original values to be able to back up, if something goes wrong or if this solution just doesn't work or if this breaks something else.
I found the solution here. There is also some information about the bug. It seems that it's Python's, not FoF's bug.
Be careful when editing the environment variables. I won't be responsible if you suddenly find your linux box speaking zulu! :p
Code: Select all
$ locale
gave me
Code: Select all
...
LANGUAGE=fi_FI:fi:en_GB:en
...
Next
Code: Select all
$ export LANGUAGE=fi_FI.ISO-8859-1:fi:en_GB:en
That's it!
So, basically, try "export LANGUAGE=x.ISO-8859-1:y:z", where x,y and z are the values of your environment variable LANGUAGE. Remember to write down the original values to be able to back up, if something goes wrong or if this solution just doesn't work or if this breaks something else.
I found the solution here. There is also some information about the bug. It seems that it's Python's, not FoF's bug.
Be careful when editing the environment variables. I won't be responsible if you suddenly find your linux box speaking zulu! :p
- bellerophon
- Member
- Posts: 12
- Joined: February 16th, 2007
- Reputation: 0
Hmmm, didn't work for me. 
One note however: There is no need to be careful, since the exporting of an environment variable using export will not be permanent. This means, after restarting your shell, the values assigned to the variables will be lost.
If you want to keep them permanently, put the export command into your ~/.bashrc, so the value will be assigned any time you start your bash (or any other shell of your personal taste for which there might be another configuration script than the bashrc).
Or, even better, do a non-permanent change which remains permanent for FretsOnFire. Edit FretsOnFire using nano (in the FoF dir: nano FretsOnFire) or vim or somehting else and add the line containing your desired locale:

One note however: There is no need to be careful, since the exporting of an environment variable using export will not be permanent. This means, after restarting your shell, the values assigned to the variables will be lost.
If you want to keep them permanently, put the export command into your ~/.bashrc, so the value will be assigned any time you start your bash (or any other shell of your personal taste for which there might be another configuration script than the bashrc).
Or, even better, do a non-permanent change which remains permanent for FretsOnFire. Edit FretsOnFire using nano (in the FoF dir: nano FretsOnFire) or vim or somehting else and add the line containing your desired locale:
Code: Select all
#!/bin/sh
export LANGUAGE=de_AT.iso-8859-1:de
export LD_LIBRARY_PATH=$(dirname $0)
exec ./FretsOnFire.bin $@
Last edited by bellerophon on Mon Apr 09, 2007 9:16 am, edited 1 time in total.
-
- Member
- Posts: 1
- Joined: November 26th, 2006
- Location: Pittsburgh
- Reputation: 0
Who is online
Users browsing this forum: No registered users and 6 guests