This one should really have gone to the Ferret list rather than the LAS list, but here we are.
I think this will be an issue of letting well enough alone. You say Ferret had been working until you tried this change. The Ferret installation guide says
So take that setting to MONSTER:0.0 out of your startup file, and start a new xterm session. What does "printenv DISPLAY" show?
On 4/25/2013 9:19 AM, Ajay Krishnan wrote:
Hi Everyone, My installation of FERRET stopped working when I tweaked the display environment based on the documentation. I used 'export=' instead of 'setenv' since I am running a bash shell script. root@MONSTER:~/ferret# export DISPLAY=MONSTER:0.0 root@MONSTER:~/ferret# printenv DISPLAY MONSTER:0.0 root@MONSTER:~/ferret# ferret Application initialization failed: couldn't connect to display "MONSTER:0.0" Loading external megawidget libraries: BWidget 1.6 Error in startup script: couldn't connect to display "MONSTER:0.0" while executing "load /usr/lib/libtk8.5.so.0 Tk" ("package ifneeded Tk 8.5.11" script) invoked from within "package require Tk 8.1.1" ("package ifneeded BWidget 1.9.5" script) invoked from within "package require BWidget 1.6" (file "/usr/share/ferret/ferret.tcl" line 886) invoked from within "source /usr/share/ferret/ferret.tcl" (file "/usr/bin/ferret" line 2) Can anyone tell me how I can get the graphical output to show on my workstation please? Thanks, Ajay