Ciao, thanks.
I didn't realize that you couldn't open the GemTools client ... I' ve only run GemTools myself on Ubuntu 16.04 ...
Here's the output of a GemTools on my Ubuntu16.04:
foos:GemTools>ls gemtools GemTools-1.0-beta.8.6-301x.app.zip GemTools-1.0-beta.8.7-340xx.app GemTools-1.0b6.app GemTools-1.0-beta.8.7-3101x.app GemTools1.0-beta.8.7.zip GemTools-1.0b6.zip GemTools-1.0-beta.8.7-310x.zip GemTools-2.3.1-preview.app GemTools-1.0-beta.8.6-244x.app GemTools-1.0-beta.8.7-31x.zip gemToolsBuilder GemTools-1.0-beta.8.6-244x.app.zip GemTools-1.0-beta.8.7-320xx.app GemTools-1.0-beta.8.6-301x.app GemTools-1.0-beta.8.7-324_linux.zipI don't have the GemTools directory.
I have only copy the:GemTools-1.0-beta.8.7-3101.app from a MacBook system to Ubuntu 18.04 LTS system
That's what I expected you to do ..
in your GemTools*.sh script you should see the lines that are listed below (without the leading plusses) ... this is the code where zenity is used and you should be able to remove the conditional block that calls zenity ... if you don't have any code that looks (exactly) like this script code, then send me your GemTools*.sh script that is in the GemTools.app directory.
You should be able to copy the GemTools*.app directory over to your Ubunutu system and start the image ... you'll need to have 32 bit X libraries installed ... if you are using GsDevKit_home, the support for Pharo will be installed.
I don't understand what do you do in the next lines.foos:GemTools>cd GemTools-1.0-beta.8.7-340xx.app foos:GemTools-1.0-beta.8.7-340xx.app>ls Contents COPYRIGHT GemTools-1.0-beta.8.7-32x.lnk GemTools-1.0-beta.8.7-32x.sh README.tx
foos:GemTools-1.0-beta.8.7-340xx.app>./GemTools-1.0-beta.8.7-32x.sh & [1] 12955 foos:GemTools-1.0-beta.8.7-340xx.app>+ dirname ./GemTools-1.0-beta.8.7-32x.sh + readlink -f . + ROOT=/export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app + LINUX=/export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Linux686 + RESOURCES=/export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Resources + gvfs-set-attribute ./GemTools-1.0-beta.8.7-32x.sh metadata::custom-icon file:///export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Resources/Squeak.png + ls /export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Resources/GemTools-1.0-beta.8.7-32x.image + wc -l + image_count=1 + + [ 1 -ne 1 ] + image=/export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Resources/GemTools-1.0-beta.8.7-32x + exec /export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Linux686/squeak -plugins /export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Linux686 -encoding latin1 -vm-display-X11 /export/foos1/users/dhenrich/GemTools/GemTools-1.0-beta.8.7-340xx.app/Contents/Resources/GemTools-1.0-beta.8.7-32x + which zenity /usr/bin/zenityHere's the listing of the GemTools startup script:#!/bin/sh set -x # path ROOT=`readlink -f $(dirname $0)` LINUX="$ROOT/Contents/Linux686" RESOURCES="$ROOT/Contents/Resources" # icon (note: gvfs-set-attribute is found in gvfs-bin on Ubuntu # systems and it seems to require an absolute filename) gvfs-set-attribute \ "$0" \ "metadata::custom-icon" \ "file://$RESOURCES/Squeak.png" \ 2> /dev/null # zenity is part of GNOME image_count=`ls "$RESOURCES"/*.image 2>/dev/null |wc -l` if which zenity &>/dev/null && [ "$image_count" -ne 1 ]; then olddir=`pwd` cd "$RESOURCES" image=`zenity --title 'Select an image' --file-selection --file-filter '*.image' --file-filter '*'` cd "$olddir" else image="$RESOURCES/GemTools-1.0-beta.8.7-32x" fi # execute exec "$LINUX/squeak" \ -plugins "$LINUX" \ -encoding latin1 \ -vm-display-X11 \ "$image".. and I'd think that you could just directly set the image file and skip the zenity code altogether and just use the line `image="$RESOURCES...` to set the image ... eliminating the zenity code works for my on Ubuntu 16.04 ...
I eliminating the zenity code and define the $RESOURCES
but the ./GemTools-1.0-beta.8.7-31x.sh report:
could not find module vm-display-X11Annullato (core dump creato)
Okay, it sounds like you have not installed X support on your client machine ... To install the x support use the highlighted shell script commands in [1], [2]. and [3].
Dale
[1] https://github.com/GsDevKit/GsDevKit_home/blob/master/bin/utils/installOsPrereqs#L39-L59
[2] https://github.com/GsDevKit/GsDevKit_home/blob/master/bin/utils/installOsPrereqs#L81-L85
[3] https://github.com/GsDevKit/GsDevKit_home/blob/master/bin/utils/installOsPrereqs#L63-L78
Free forum by Nabble | Edit this page |