I can only test it in Ubuntu and Windows for the moment.
Steps to reproduce (in Windows)
1) Download:
3) Unzip everything to the same directory, then start Pharo.exe
4) Execute in Workspace
Metacello new
baseline:'Seaside3';
repository: 'github://SeasideSt/Seaside:master/repository';
load
5) Save and Quit
6) Try to start Pharo.exe
If I delete stderr, stdout and PharoDebug.log before restarting Pharo, I can see that stderr and PharoDebug.log are created at 0 bytes, there is no other log that I can find.
As you can see, no startup scripts are involved. This is a clean Pharo installation. And this happens both in Windows and in Ubuntu, no matter in which OS I try to do the download+load.
If it is of any help, this has been happening exactly since build 383. It worked perfectly up to build 382.
On Thursday, February 8, 2018, 4:42:36 PM GMT-3, Sean P. DeNigris <sean@clipperadams.com> wrote:
Pharo Smalltalk Developers mailing list wrote
> I have no idea why this is happening
I had a similar situation due to a deprecation warning generated by my
startup script. I aborted from the debugger, and the image worked normally,
but when I saved, quit and tried to restart the image, it wouldn't open (VM
icon in list of active apps, but window never appeared macOS high Sierra).
-----
Cheers,
Sean
--
Sent from:
http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html