Smalltalk › Pharo › Pharo Smalltalk Users

Issue with starting 32-bit Pharo under Linux

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

horrido

Issue with starting 32-bit Pharo under Linux

I'm running 32-bit Debian.

I installed 32-bit Pharo 6.1 using:

wget -O- https://get.pharo.org | bash

When I try to run Pharo with:

./pharo-ui Pharo.image &

I get this error:

PrimitiveFailed: primitive #createDirectory: in UnixStore failed

And when I try to close the image, I get this error:

PrimitiveFailed: primitive #primSize: in MultiByteFileStream failed

What's going on???

horrido

Re: Issue with starting 32-bit Pharo under Linux

I just discovered why! I have to run the bloody thing as root! Why the hell
is that???

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

alistairgrant

Re: Issue with starting 32-bit Pharo under Linux

On Sun, 18 Nov 2018 at 04:55, horrido <[hidden email]> wrote:
>
> I just discovered why! I have to run the bloody thing as root! Why the hell
> is that???

Just a guess: do you have write access to the image directory?

Cheers,
Alistair

horrido

Re: Issue with starting 32-bit Pharo under Linux

Yes, of course. It's $home (/home/richard/pharo).

Alistair Grant wrote
> On Sun, 18 Nov 2018 at 04:55, horrido <

> horrido.hobbies@

> > wrote:
>>
>> I just discovered why! I have to run the bloody thing as root! Why the
>> hell
>> is that???
>
> Just a guess: do you have write access to the image directory?
>
> Cheers,
> Alistair

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

Ben Coman

Re: Issue with starting 32-bit Pharo under Linux

In reply to this post by horrido

On Sun, 18 Nov 2018 at 11:50, Richard Kenneth Eng <[hidden email]> wrote:

I'm running 32-bit Debian.

I installed 32-bit Pharo 6.1 using:
wget -O- https://get.pharo.org | bash

When I try to run Pharo with:
./pharo-ui Pharo.image &

I get this error:

PrimitiveFailed: primitive #createDirectory: in UnixStore failed

Does the Image freeze or crash at this point, or can you inspect the stack

and let us know what is the path its trying to create?

They might allow additional insight as to what is going on.

cheers -ben