On Nov 9, 2013, at 10:52 AM, Camillo Bruni <camillobr...@gmail.com> wrote:
> > On 2013-11-09, at 14:29, Camillo Bruni <camillobr...@gmail.com> wrote: > >> On 2013-11-09, at 14:17, Camillo Bruni <camillobr...@gmail.com> wrote: >>> On 2013-11-09, at 14:00, Marcus Denker <marcus.den...@inria.fr> wrote: >>>> On 09 Nov 2013, at 13:55, Johan Fabry <jfa...@dcc.uchile.cl> wrote: >>>>> Nope, I just unzip the new image and double click it. (+ I never defined >>>>> any startup script anywhere) >>>>> >>>> do you have a .sources file? >>> >>> probably that, since the lookup logic changed the other day. I will try >>> without the .sources >> >> Confirmed, if I open the image without sources it hangs (strangely enough >> not even with stderr output) >> Saving the image with sources and then opening it again without sources >> works, producing a proper warning > > https://pharo.fogbugz.com/f/cases/12129/FileLocator-is-not-initialized-at-the-right-point-during-startup Confirmed from my end: putting a PharoV20.sources in the same directory as the VM (Pharo.app) solved the problem. Note that putting it in the same directory as the image does NOT solve the problem. I don't know what the expected behavior is anymore, so I am just reporting both behaviors here. Thanks for looking into this! ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
