Installing EVE on Linux: Difference between revisions

Line 105:

Your EVE launcher shortcut may fail with the following message:

:{{code|/bin/sh: {{Color|orange|warning}}: shell level (1000) too high, resetting to 1}}

:{{code|/bin/sh: {{Color|orange|warning}}: shell level (1000) too high, resetting to 1}}

This, and other errors, are likely due to the fact that the 'dirname' and 'pwd' commands will return the location of the soft link, not of the shell script itself. Hence, we need to use readlink to follow every symlink in the path. Make the following changes to /path/to/evelauncher/evelauncher.sh:

:{{code|#!/bin/sh {{Color|green|appname<nowiki>=</nowiki>"evelauncher" }} {{Color|green|dirname<nowiki>=</nowiki>$(dirname "$(readlink -f "$BASH_SOURCE")")}} tmp<nowiki>=</nowiki>"${dirname#?}" if [ "${dirname%$tmp}" !<nowiki>=</nowiki> "/" ]; then dirname<nowiki>=</nowiki>"$PWD/$dirname" fi LD_LIBRARY_PATH<nowiki>=</nowiki>"$dirname:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH export QTDIR<nowiki>=</nowiki>$dirname export QT_PLUGIN_PATH<nowiki>=</nowiki>$dirname/plugins "$dirname/$appname" "$@"}}

:{{code|#!/bin/sh {{Color|green|appname<nowiki>=</nowiki>"evelauncher" }} {{Color|green|dirname<nowiki>=</nowiki>$(dirname "$(readlink -f "$BASH_SOURCE")")}} tmp<nowiki>=</nowiki>"${dirname#?}" if [ "${dirname%$tmp}" !<nowiki>=</nowiki> "/" ]; then dirname<nowiki>=</nowiki>"$PWD/$dirname" fi LD_LIBRARY_PATH<nowiki>=</nowiki>"$dirname:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH export QTDIR<nowiki>=</nowiki>$dirname export QT_PLUGIN_PATH<nowiki>=</nowiki>$dirname/plugins "$dirname/$appname" "$@"}}

:'''Note:''' The first change is necessary only if you choose to give your soft link a different name.

[[Category:Guides]]

===X Server===

If Eve Online fails to launch, try running it from the terminal. Check for the following error message:

:{{code|user@localhost<nowiki> > ./evelauncher.sh</nowiki> ... {{Color|orange|Invalid MIT-MAGIC-COOKIE-1}} }}

As explained [https://unix.stackexchange.com/a/10126/29963 here], an X program needs (1) the address of the display (typically ":0") and (2) the password for the display. The second requirement is known as the "Magic Cookie". One workaround to sidestep this access problem is to use xhost, which is an X server access control program. Make the following changes to /path/to/evelauncher/evelauncher.sh:

:{{code|#!/bin/sh appname<nowiki>=</nowiki>"evelauncher" dirname<nowiki>=</nowiki>$(dirname "$(readlink -f "$BASH_SOURCE")") tmp<nowiki>=</nowiki>"${dirname#?}" if [ "${dirname%$tmp}" !<nowiki>=</nowiki> "/" ]; then dirname<nowiki>=</nowiki>"$PWD/$dirname" fi {{Color|green|xhost +local:}} LD_LIBRARY_PATH<nowiki>=</nowiki>"$dirname:$LD_LIBRARY_PATH" export LD_LIBRARY_PATH export QTDIR<nowiki>=</nowiki>$dirname export QT_PLUGIN_PATH<nowiki>=</nowiki>$dirname/plugins "$dirname/$appname" "$@"}}

:'''Note:''' xhost here is granting temporary access to any local application running as the current user. It is ''not'' allowing any kind of remote access.

[[Category:Guides]]

@@ Line 105: / Line 105: @@
 Your EVE launcher shortcut may fail with the following message:
-:{{code|/bin/sh: {{Color|orange|warning}}: shell level (1000) too high, resetting to 1}}
+:{{code|/bin/sh: {{Color|orange|warning}}: shell level (1000) too high, resetting to 1}} <br>
 This, and other errors, are likely due to the fact that the 'dirname' and 'pwd' commands will return the location of the soft link, not of the shell script itself. Hence, we need to use readlink to follow every symlink in the path. Make the following changes to /path/to/evelauncher/evelauncher.sh:
-:{{code|#!/bin/sh <br>{{Color|green|appname<nowiki>=</nowiki>"evelauncher"<br>}}<br>{{Color|green|dirname<nowiki>=</nowiki>$(dirname "$(readlink -f "$BASH_SOURCE")")}}<br>tmp<nowiki>=</nowiki>"${dirname#?}"<br><br>if [ "${dirname%$tmp}" !<nowiki>=</nowiki> "/" ]; then<br>dirname<nowiki>=</nowiki>"$PWD/$dirname"<br>fi<br><br>LD_LIBRARY_PATH<nowiki>=</nowiki>"$dirname:$LD_LIBRARY_PATH"<br>export LD_LIBRARY_PATH<br>export QTDIR<nowiki>=</nowiki>$dirname<br>export QT_PLUGIN_PATH<nowiki>=</nowiki>$dirname/plugins<br>"$dirname/$appname" "$@"}}
+:{{code|#!/bin/sh <br>{{Color|green|appname<nowiki>=</nowiki>"evelauncher"<br>}}<br>{{Color|green|dirname<nowiki>=</nowiki>$(dirname "$(readlink -f "$BASH_SOURCE")")}}<br>tmp<nowiki>=</nowiki>"${dirname#?}"<br><br>if [ "${dirname%$tmp}" !<nowiki>=</nowiki> "/" ]; then<br>dirname<nowiki>=</nowiki>"$PWD/$dirname"<br>fi<br><br>LD_LIBRARY_PATH<nowiki>=</nowiki>"$dirname:$LD_LIBRARY_PATH"<br>export LD_LIBRARY_PATH<br>export QTDIR<nowiki>=</nowiki>$dirname<br>export QT_PLUGIN_PATH<nowiki>=</nowiki>$dirname/plugins<br>"$dirname/$appname" "$@"}} <br>
 :'''Note:''' The first change is necessary only if you choose to give your soft link a different name.
+[[Category:Guides]]
+<br>
+===X Server===
+If Eve Online fails to launch, try running it from the terminal. Check for the following error message:
+:{{code|user@localhost<nowiki> > ./evelauncher.sh</nowiki><br>...<br>{{Color|orange|Invalid MIT-MAGIC-COOKIE-1}} }}<br>
+As explained [https://unix.stackexchange.com/a/10126/29963 here], an X program needs (1) the address of the display (typically ":0") and (2) the password for the display. The second requirement is known as the "Magic Cookie". One workaround to sidestep this access problem is to use xhost, which is an X server access control program. Make the following changes to /path/to/evelauncher/evelauncher.sh:
+:{{code|#!/bin/sh <br>appname<nowiki>=</nowiki>"evelauncher"<br><br>dirname<nowiki>=</nowiki>$(dirname "$(readlink -f "$BASH_SOURCE")")<br>tmp<nowiki>=</nowiki>"${dirname#?}"<br><br>if [ "${dirname%$tmp}" !<nowiki>=</nowiki> "/" ]; then<br>dirname<nowiki>=</nowiki>"$PWD/$dirname"<br>fi<br><br>{{Color|green|xhost +local:}}<br><br>LD_LIBRARY_PATH<nowiki>=</nowiki>"$dirname:$LD_LIBRARY_PATH"<br>export LD_LIBRARY_PATH<br>export QTDIR<nowiki>=</nowiki>$dirname<br>export QT_PLUGIN_PATH<nowiki>=</nowiki>$dirname/plugins<br>"$dirname/$appname" "$@"}} <br>
+:'''Note:''' xhost here is granting temporary access to any local application running as the current user. It is ''not'' allowing any kind of remote access.
 [[Category:Guides]]