[Gwyddion-users] Cannot open Gwyddion after installation on macSierra

[Yonatan Horowitz]

Hello everyone,

I have recently installed Gywddion through MacPorts according to the installation guide on my MacBook Pro (Retina, 13-inch, Late 2013).
My OS is the latest (and updated): Sierra [version 10.12.3]
QuartzX did not support the installation so I downloaded the Xcode app.
I had to force install (’sudo') two libraries during the installation I think one of them was libz.
After that the installation of Gwyddion went smoothly.

Calling the app from its StartUp icon (through Launch) did not work but and I was able to call Gwyddion from the Terminal by typing ‘gwyddion’.
Then I closed the Terminal and when I reopened the Terminal and typed ‘gwyddion’ there was no response.

Can you please advise me how to proceed?
Yonatan Horowitz, Ph.D.
Postdoctoral fellow, Prof. G. A. Somorjai group
Department of Chemistry
University of California, Berkeley
Berkeley, CA 9470-1460
***@berkeley.edu <mailto:***@berkeley.edu>

[David Nečas (Yeti)]

Post by Yonatan Horowitz
Calling the app from its StartUp icon (through Launch) did not work
but and I was able to call Gwyddion from the Terminal by typing
‘gwyddion’.
Then I closed the Terminal and when I reopened the Terminal and typed
‘gwyddion’ there was no response.
Can you please advise me how to proceed?

Well, I do not use Mac but anyway:

What is no response? Either you just get the prompt again immediately
or something gets stuck, it is running, running, but the Gwyddion GUI
never appears.

See also what

gwyddion --version

does because it does not invoke any GUI stuff.

See if

which gwyddion

prints something reasonable (although I am not sure what exactly is the
correct location).

Finally, gwyddion seems to be a script handling the different variants

https://github.com/macports/macports-ports/blob/master/science/gwyddion/files/gwyddion

I don't know why programs are run through ‘open’ but... Look at the
script installed at your computer (it has the @SOMETHING@ placeholders
replaced with actual directories), try to find out which of the variants
applies, check if the files and directories exists and try to run the
open commands directly.

This is no magic fix, just standard getting to the core of the problem.

Regards,

Yeti