Smalltalk › Pharo › Pharo Smalltalk Users

OSEnvironment issue

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Eno

OSEnvironment issue

Problem with opening pharo image on macOS 10.12.6. cann't find requested
origin: #home.

i.e. the script "Smalltalk os current environment getEnv: 'HOME'" failed.

(actually The ffiCall from LibC in the method UnixEnvironment>>getEnv:
failed ).

Is it occurred recently? or issued or fixed in issue tracker already?

Best regards.

--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

HilaireFernandes

Re: OSEnvironment issue

Work there on a P7 on Linux.

Wrong VM of yours?

Le 10/12/2017 à 17:25, Eno a écrit :

> Problem with opening pharo image on macOS 10.12.6. cann't find requested
> origin: #home.
>
> i.e. the script "Smalltalk os current environment getEnv: 'HOME'" failed.
>
> (actually The ffiCall from LibC in the method UnixEnvironment>>getEnv:
> failed ).
>
> Is it occurred recently? or issued or fixed in issue tracker already?
>
> Best regards.

--
Dr. Geo
http://drgeo.eu

http://drgeo.eu

Eno

Re: OSEnvironment issue

yes, you are right, it's caused by wrong VM, since by default, my images are
opened by pharo 5 VM, I cann't change to pharo 6.1 anyway without manual
effort. I would easily miss this point while saving to new image and reopen.

BTW, another wierd error occured frequently, nearly everytime, i.e. system
font error while runing IDEs.
Error message: FT2Error: Freetype2 primitive failed[error 2][unknown file
format] while calling FreeTypeFace>>create.

The system would halt complete at that point and the debugger window also
failed since they all depended upon the font to show.

I tried to change the system via Setting Browser, but it was locked due to
the same reason.

--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Stephane Ducasse-3

Re: OSEnvironment issue

Hi eno

On sierra I removed the Freetype plugin because it was crashing too
many times (apparently in Pharo 70 this was fixed)
then now I have crash when typing. :(

Stef

On Mon, Dec 11, 2017 at 6:08 AM, Eno <[hidden email]> wrote:

> yes, you are right, it's caused by wrong VM, since by default, my images are
> opened by pharo 5 VM, I cann't change to pharo 6.1 anyway without manual
> effort. I would easily miss this point while saving to new image and reopen.
>
> BTW, another wierd error occured frequently, nearly everytime, i.e. system
> font error while runing IDEs.
> Error message: FT2Error: Freetype2 primitive failed[error 2][unknown file
> format] while calling FreeTypeFace>>create.
>
> The system would halt complete at that point and the debugger window also
> failed since they all depended upon the font to show.
>
> I tried to change the system via Setting Browser, but it was locked due to
> the same reason.
>
>
>
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>

Eno

Re: OSEnvironment issue

Yep, It's very bothersome to be tangled inside the font issue.

Actually, I find out the cause.

My pharo folders with images and sandstone files are synced with cloud
(synology NAS) in order to allow update at my different work places.

I found that if I triggered image saving several times too quickly, the
updates get trouble inside what the image was saved, maybe the font files
were lost or conflicted as a result and error occured while reopen that
image.

I quitted the cloud synchronize and the errors resolved.

Best regards.

--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Ben Coman

Re: OSEnvironment issue

Thanks for the update.

cheers -ben

On 12 December 2017 at 22:27, Eno <[hidden email]> wrote:

Yep, It's very bothersome to be tangled inside the font issue.

Actually, I find out the cause.

My pharo folders with images and sandstone files are synced with cloud
(synology NAS) in order to allow update at my different work places.

I found that if I triggered image saving several times too quickly, the
updates get trouble inside what the image was saved, maybe the font files
were lost or conflicted as a result and error occured while reopen that
image.

I quitted the cloud synchronize and the errors resolved.

Best regards.

--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html