Thx. This helped me, too Hartmut Krasemann ———————— Königsberger Str. 41c D 22869 Schenefeld +49.171.6451283 krasemann@acm.org

Am 09.10.2026 um 00:13 schrieb Tomohiro Oda via Pharo-users <pharo-users@lists.pharo.org>:

Hartmut,

I had the same problem and I replaced the content of PharoLauncher.app/Contents/MacOS/Pharo and Plugins with the ones from the zeroconf.

$ curl -L https://get.pharo.org | bash $ cp -rp pharo-vm/Pharo.app/Contents/MacOS/* /Applications/PharoLauncher.app/Contents/MacOS/

So far it seems working. I hope this helps. --- tomo

2026年10月8日(木) 19:56 Hartmut Krasemann via Pharo-users <pharo-users@lists.pharo.org>:

...

To whoever can help

On MacOS 27 my Pharo Launcher did no longer start. Loading the latest Launcher from the Pharo website did not help. Neither startet my images by drag and drop (image to app)

I found out that I used an arm-64 vm v10.3.9. and that the latest Launcher from Pharo.org starts the same version.

After searching around a while I discovered that I could load a newer arm-64 vm v10.3.11 . I could not patch the Launcher with this vm, but make it default for all my images. Now an image starts with double click , choosing itself in a Mac dialog , and again double click it. However, starting this way, the working directory obviously is not set. I did not find a way to set the working directory in the running image.

I then wrote a bash shell script (for each image to start) with the working directory as an argument.

Now I can run my images but not the Launcher.

Where can I get a download of a corrected Launcher Or Is there an easy fix?

Regards, hartmut-k

Hartmut Krasemann ———————— Königsberger Str. 41c D 22869 Schenefeld +49.171.6451283 krasemann@acm.org