just for the record I have not created any kind of configuration in Ephestos. The code that you can download from Smalltalkhub or github is the only thing that lives inside the image. I use Smalltalkhub as a backup for github repo until I make sure filetree is a reliable way to work with github and pharo. I have not touche any of the internals of Pharo all my code lives inside the SThub repo. Other than the steps I described , and the code you can get from sthub I have done nothing to the pharo image. Also I forgot to say I dont mind at all late replies, I did not want to imply that I was annoyed or anything like that with people not replying. Its perfectly ok to not reply to my threads or reply days afterwards or even moths. I have in my hand scientific evidence that I am not the center of this world. Thank you Christopher and everyone who is trying to help me in each of my problems. I really appreciate it. On Fri, Sep 19, 2014 at 12:49 PM, kilon alios <kilon.alios@gmail.com> wrote:

I dont use a startup script myself, in windows the image with problem is release 40230, i download that specific release and it works o_O , so maybe it was something I did afterall ? very strange

so I attached my image folder, hope it helps you

On Fri, Sep 19, 2014 at 12:39 PM, Christophe Demarey < Christophe.Demarey@inria.fr> wrote:

...

Le 19 sept. 2014 à 11:21, kilon alios a écrit :

...

Well to kepp you updated , because I did not bother replying to my own thread since none seemed to care or have the same issue as me.

I was out of office last days ...

...

I tried on windows again same error as macos on a fresh image by the way. So I know it must not be me.

On which image? I just tried on a fresh 3.0 image and it also works for me.

...

The only things I am doing with pharo is

1) use dark theme

2) use free type font Arial on windows and Monaco on macos

3) use filetree for working with a git directory.

Maybe a side effect. Could you give me a script to help reproducing the problem? Maybe just your startup script. Does the problem appear the first time you open Versionner?

Thanks, Christophe.