Singularity startet in gedit

Giuseppe Balan
Giuseppe Balan
 Member edited July 2014 in Technical Support
Guten Abend zusammen :)

Ich habe heute Nachmittag mein System auf Ubuntu 14.04 upgedatet, nun hab ich einige Programme schon neu installiert, so auch den Singularity Viewer.
Jetzt wollte ich den starten, nachdem ich meine Region gestartet hatte, da öffnet der sich aber nicht wie gewohnt, sondern in gedit.

Ich kopier den Text mal hier rein, vielleicht weiß jemand von Euch rat, was da falsch gelaufen ist.

#!/bin/bash

## Here are some configuration options for Linux Client Testers.
## These options are for self-assisted troubleshooting during this beta
## testing phase; you should not usually need to touch them.

## - Avoids using any FMOD Ex audio driver.
#export LL_BAD_FMODEX_DRIVER=x
## - Avoids using any OpenAL audio driver.
#export LL_BAD_OPENAL_DRIVER=x
## - Avoids using any FMOD audio driver.
#export LL_BAD_FMOD_DRIVER=x

## - Avoids using the FMOD Ex PulseAudio audio driver.
#export LL_BAD_FMOD_PULSEAUDIO=x
## - Avoids using the FMOD or FMOD Ex ALSA audio driver.
#export LL_BAD_FMOD_ALSA=x
## - Avoids using the FMOD or FMOD Ex OSS audio driver.
#export LL_BAD_FMOD_OSS=x
## - Avoids using the FMOD or FMOD Ex ESD audio driver.
#export LL_BAD_FMOD_ESD=x

## - Avoids the optional OpenGL extensions which have proven most problematic
## on some hardware. Disabling this option may cause BETTER PERFORMANCE but
## may also cause CRASHES and hangs on some unstable combinations of drivers
## and hardware.
## NOTE: This is now disabled by default.
#export LL_GL_BASICEXT=x

## - Avoids *all* optional OpenGL extensions. This is the safest and least-
## exciting option. Enable this if you experience stability issues, and
## report whether it helps in the Linux Client Testers forum.
#export LL_GL_NOEXT=x

## - For advanced troubleshooters, this lets you disable specific GL
## extensions, each of which is represented by a letter a-o. If you can
## narrow down a stability problem on your system to just one or two
## extensions then please post details of your hardware (and drivers) to
## the Linux Client Testers forum along with the minimal
## LL_GL_BLACKLIST which solves your problems.
#export LL_GL_BLACKLIST=abcdefghijklmno

## - Some ATI/Radeon users report random X server crashes when the mouse
## cursor changes shape. If you suspect that you are a victim of this
## driver bug, try enabling this option and report whether it helps:
#export LL_ATI_MOUSE_CURSOR_BUG=x

## - If you experience crashes with streaming video and music, you can
## disable these by enabling this option:
#export LL_DISABLE_GSTREAMER=x


## Everything below this line is just for advanced troubleshooters.
##


## - For advanced debugging cases, you can run the viewer under the
## control of another program, such as strace, gdb, or valgrind. If
## you're building your own viewer, bear in mind that the executable
## in the bin directory will be stripped: you should replace it with
## an unstripped binary before you run.
if [ -n "$ASCENDED_DEVELOPER" ]; then
if [ "$ASCENDED_DEVELOPER" = "1" ]; then
export LL_WRAPPER='gdb --args'
elif [ "$ASCENDED_DEVELOPER" = "2" ]; then
export LL_WRAPPER='valgrind --smc-check=all --error-limit=no --log-file=secondlife.vg --leak-check=full --suppressions=/usr/lib/valgrind/glibc-2.5.supp --suppressions=secondlife-i686.supp'
elif [ "$ASCENDED_DEVELOPER" = "3" ]; then
export LL_WRAPPER='strace -f -ff -o singularity.strace'
fi
fi

## - This allows one to set an arbitrary value for LD_PRELOAD.
## It won't work if LL_TCMALLOC is set because that uses it's
## own value of LD_PRELOAD.
#export AI_PRELOAD='/path/to/libmemleak.so'

## - Avoids an often-buggy X feature that doesn't really benefit us anyway.
export SDL_VIDEO_X11_DGAMOUSE=0

## - Works around a problem with misconfigured 64-bit systems not finding GL
# This is less needed nowadays; don't uncomment this unless LibGL can't find your
# drivers automatically.
#export LIBGL_DRIVERS_PATH="${LIBGL_DRIVERS_PATH}":/usr/lib64/dri:/usr/lib32/dri:/usr/lib/dri

## - The 'scim' GTK IM module widely crashes the viewer. Avoid it.
if [ "$GTK_IM_MODULE" = "scim" ]; then
export GTK_IM_MODULE=xim
fi

# Work around for a crash bug when restarting OpenGL after a change in the
# graphic settings (anti-aliasing, VBO, FSAA, full screen mode, UI scale).
# When you enable this work around, you can change the settings without
# crashing, but you will have to restart the viewer after changing them
# because the display still gets corrupted.
export LL_OPENGL_RESTART_CRASH_BUG=x

## - Automatically work around the ATI mouse cursor crash bug:
## (this workaround is disabled as most fglrx users do not see the bug)
#if lsmod | grep fglrx &>/dev/null ; then
# export LL_ATI_MOUSE_CURSOR_BUG=x
#fi


## Nothing worth editing below this line.
##

SCRIPTSRC=`readlink -f "$0" || echo "$0"`
RUN_PATH=`dirname "${SCRIPTSRC}" || echo .`
echo "Running from ${RUN_PATH}"
cd "${RUN_PATH}"

# Re-register the secondlife:// protocol handler every launch, for now.
./register_secondlifeprotocol.sh

# Re-register the application with the desktop system every launch, for now.
./refresh_desktop_app_entry.sh

## Before we mess with LD_LIBRARY_PATH, save the old one to restore for
## subprocesses that care.
export SAVED_LD_LIBRARY_PATH="${LD_LIBRARY_PATH}"

SL_ENV=

if [ -n "$AI_PRELOAD" ]; then
SL_ENV='LD_PRELOAD="$AI_PRELOAD" '
fi

if [ -n "$LL_TCMALLOC" ]; then
tcmalloc_libs='/usr/lib/libtcmalloc.so.0 /usr/lib/libstacktrace.so.0 /lib/libpthread.so.0'
all=1
for f in $tcmalloc_libs; do
if [ ! -f $f ]; then
all=0
fi
done
if [ $all != 1 ]; then
echo 'Cannot use tcmalloc libraries: components missing' 1>&2
else
SL_ENV='LD_PRELOAD="$(echo $tcmalloc_libs | tr '"' '"' : ) " '
if [ -z "$HEAPCHECK" -a -z "$HEAPPROFILE" ]; then
export HEAPCHECK=${HEAPCHECK:-normal}
fi
fi
fi

export VIEWER_BINARY='singularity-do-not-run-directly'
BINARY_TYPE=$(expr match "$(file -b bin/$VIEWER_BINARY)" '\(.*executable\)' | sed -e 's/ / /g')
if [ "${BINARY_TYPE}" == "ELF 64-bit LSB executable" ]; then
SL_ENV+='LD_LIBRARY_PATH="`pwd`/lib64:`pwd`/lib32:$LD_LIBRARY_PATH"'
else
SL_ENV+='LD_LIBRARY_PATH="`pwd`/lib:$LD_LIBRARY_PATH"'
fi
export SL_CMD='$LL_WRAPPER bin/$VIEWER_BINARY'

if [ -n "$AITESTPLUGIN" ]; then
SL_CMD="$LL_WRAPPER bin/SLPlugin"
SL_OPT="TESTPLUGIN"
else
SL_OPT="`cat gridargs.dat` $@"
fi

# Run the program.
eval ${SL_ENV} ${SL_CMD} ${SL_OPT} || LL_RUN_ERR=runerr

# Handle any resulting errors
if [ "$LL_RUN_ERR" = "runerr" ]; then
# generic error running the binary
echo '*** Bad shutdown. ***'
fi

Comments

  • Ska Skaduwee
    Ska Skaduwee
     Member edited 12:23AM
    huhu Giu

    die datei (singularity) hat das "Ausführen-Recht" verloren. Angenommen singularity ist im /opt/singularity/ ordner:
    cd /opt/singularity/
    ls -l singularity
    
    muss kommen -rwxr--r-- ...... singularity
    das x fehlt dort
    chmod 744 singularity
    ls -l singularity
    
    jetzt sollte dort -rwxr--r-- ...... singularity stehen
    je nach eigenen rechten musst du sudo chmod... ausführen

    grüsse
  • Giuseppe Balan
    Giuseppe Balan
     Member edited 12:23AM
    Hallo Ska :)

    Vielen Dank für den Versuch mir zu helfen. :)

    Ich steh wie der berühmte Ochs vorm Berge und weiß nicht was ich machen soll. :(
    Singularity hab ich erstmal wieder alles gelöscht, auch das Spiel, welches installiert wurde, als ich im Terminal "Singularity" (ohne "") eingegeben hatte.
    Nun hab ich den frisch entpackten Ordner offen und sehe eine Datei mit Namen install.sh. Wenn ich die öffne ist zu lesen dass es ein Script ist.
    Alles gut und schön, nur weiß ich nicht wie ich die Datei ausführe, bzw. ob es überhaupt nötig ist sie auszuführen. :(
  • Ska Skaduwee
    Ska Skaduwee
     Member edited 12:23AM
    huhu Giu

    ich habe das (singularity) archiv entpackt, in den /opt/ verschoben. wenn du eine datei manuell ausführen willst, must du im terminal zum verzeichnis mit cd wechseln und kannst es dann mit z.B. ./singularity ausführen. das ./ stellt den aktuellen (relativen) path dar, damit sucht er nicht die $PATH nach dem befehl "singularity" ab, findet die nicht und meckert. alles verstanden??? ;) wie du eine verknüpfung zum singularity erstellst kann ich dir bei klicki bunti leider nicht erklären. ich habe eine datei singularity.desktop im path /home/"user"/.local/share/applications/
    erstellt:
    [Desktop Entry]
    Version=1.0
    Type=Application
    Name=singularity
    Icon=/opt/Singularity-i686-1.8.5.5617/singularity_icon.png
    Exec=/opt/Singularity-i686-1.8.5.5617/singularity
    NoDisplay=false
    Categories=Game;
    StartupNotify=false
    Terminal=false
    

    dazu musst du die singularity erst mal wie beschrieben startfähig machen.
    brauchst dich nicht sputen, denn tango metropolis is down im moment :?
Sign In or Register to comment.

Welcome

It looks like you're new here. If you want to get involved, click one of these buttons!

Discussions

© Copyright 2017 - Metropolis Metaversum
All times are GMT