... and on Debian 14.04 x64.
BW,
Volkert
Am 02.08.2014 um 02:09 schrieb volk...@nivoba.de:
I had the same problem today on W8.1 x64 :-(
BW,
Volkert
Am 31.07.2014 um 10:50 schrieb Blondeau Vincent:
Hi,
Yesterday, I was using GraphET (a part of Roassal) to do some charts
and, today, when I
I had the same problem today on W8.1 x64 :-(
BW,
Volkert
Am 31.07.2014 um 10:50 schrieb Blondeau Vincent:
Hi,
Yesterday, I was using GraphET (a part of Roassal) to do some charts
and, today, when I wanted to reopen the image.
And I got that :
It is **very** unpleasant…
To reproduce the
la part
>> de* stepharo
>> *Envoyé :* jeudi 31 juillet 2014 22:55
>> *À :* Pharo Development List
>> *Objet :* Re: [Pharo-dev] Pharo image corruption and fatal VM error with
>> Roassal
>>
>>
>>
>> vincent
>>
>> you can take an image/cha
; *Objet :* Re: [Pharo-dev] Pharo image corruption and fatal VM error with
> Roassal
>
>
>
> vincent
>
> you can take an image/change copy
> your change as the change of the new image
> and do recovery last changes and you get all your changes back.
>
> Ok that is cool
De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de stepharo
Envoyé : jeudi 31 juillet 2014 22:55
À : Pharo Development List
Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal
vincent
you can take an image/change copy
your change as the change of
line every day…
Vincent
*De :*Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] *De la part
de* Usman Bhatti
*Envoyé :* jeudi 31 juillet 2014 10:59
*À :* Pharo Development List
*Cc :* Moose-related development
*Objet :* Re: [Pharo-dev] Pharo image corruption and fatal VM error
with Roassal
vincent
you can take an image/change copy
your change as the change of the new image
and do recovery last changes and you get all your changes back.
Now before concluding that this is pharo's fault... we should check
cairo and roassal's athens usage.
Stef
On 31/7/14 10:50, Blondeau Vincent wr
t;> Vincent
>>
>>
>>
>> *De :* Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] *De la part
>> de* Usman Bhatti
>> *Envoyé :* jeudi 31 juillet 2014 10:59
>> *À :* Pharo Development List
>> *Cc :* Moose-related development
>>
>> *O
use :).
>
>
> Vincent
>
>
>
> *De :* Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] *De la part
> de* Usman Bhatti
> *Envoyé :* jeudi 31 juillet 2014 10:59
> *À :* Pharo Development List
> *Cc :* Moose-related development
>
> *Objet :* Re: [Phar
-dev] Pharo image corruption and fatal VM error with Roassal
This may be related to this known issue reported a few days back.
https://code.google.com/p/moose-technology/issues/detail?id=1084
And there is a possible solution to recover your image.
usman
On Thu, Jul 31, 2014 at 10:50 AM, Blondeau
10:54
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error with Roassal
Looks like Cairo can't be loaded.
Does the Eliot VM comes with libCairo?
Hilaire
Le 31/07/2014 16:50, Blondeau Vincent a écrit :
> Hi,
>
> Yesterday, I was using Grap
This may be related to this known issue reported a few days back.
https://code.google.com/p/moose-technology/issues/detail?id=1084
And there is a possible solution to recover your image.
usman
On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent <
vincent.blond...@worldline.com> wrote:
> Hi,
>
Looks like Cairo can't be loaded.
Does the Eliot VM comes with libCairo?
Hilaire
Le 31/07/2014 16:50, Blondeau Vincent a écrit :
Hi,
Yesterday, I was using GraphET (a part of Roassal) to do some charts
and, today, when I wanted to reopen the image.
And I got that :
It is **very** unpleasant…
Hi,
Yesterday, I was using GraphET (a part of Roassal) to do some charts and,
today, when I wanted to reopen the image.
And I got that :
[cid:image001.png@01CFACAA.E0CB2060]
It is *very* unpleasant...
To reproduce the bug:
1 - You can do either:
| builder |
14 matches
Mail list logo
