Johnny Ernst Nielsen wrote:

...

SUSE Linux 10.0 on an old pentium 400Mhz

Fredag 27 januar 2006 05:41 kvad James Wright:

Do you have the required 128 meg of RAM?

Greetings James, the computer has 250 meg of RAM. Best regards Johnny :o)

The Thursday 2006-01-26 at 20:51 +0100, Johnny Ernst Nielsen wrote:

...

SUSE Linux 10.0 on an old pentium 400Mhz

After the initial setup dialogs on first run, nothing happens. Subsequent starting attempts simply does nothing at all.

Greetings Carlos. Søndag 29 januar 2006 13:29 kvad Carlos E. R.:

You could remove the directory ~/.gimp-{version}

That does not help. I even removed GIMP and reinstalled it. That did not work either.

Or you could try tweaking something there, but I don't know what. File 'gimprc' seems to be the main config.

I have no idea what settings i should try to fiddle with. Especially since the Gimp runs fine on my computer, but not on my mother's, and the software installations are identical. The computers differ only with regards to hardware.

If you start gimp from an xterm you might see an error message.

Yes. The message is: hanne@comp:~> gimp Illegal instruction (SIGILL) hanne@comp:~>

...

I have tried "strace gimp 2> outdata.txt"

Better use "strace -o filename gimp". Perhaps also use "-f".

The last 20 lines of strace -o filename gimp: read(4, "", 4000) = 0 close(4) = 0 gettimeofday({1138652503, 336856}, NULL) = 0 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x411e4000 munmap(0x411e4000, 32768) = 0 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x411e4000 munmap(0x411e4000, 32768) = 0 open("/home/hanne/.gimp-2.2", O_RDONLY|O_NONBLOCK|O_LARGEFILE| O_DIRECTORY) = 4 fstat64(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0 getdents64(4, /* 23 entries */, 4096) = 720 getdents64(4, /* 0 entries */, 4096) = 0 close(4) = 0 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x411e4000 munmap(0x411e4000, 32768) = 0 open("/home/hanne/.gimp-2.2/gimpswap.5863", O_RDWR|O_CREAT| O_LARGEFILE, 0600) = 4 close(4) = 0 unlink("/home/hanne/.gimp-2.2/gimpswap.5863") = 0 --- SIGILL (Illegal instruction) @ 0 (0) --- +++ killed by SIGILL +++ The last 20 lines of strace -f -o filename gimp: 5869 read(4, "", 4000) = 0 5869 close(4) = 0 5869 gettimeofday({1138652644, 122856}, NULL) = 0 5869 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE| MAP_ANONYMOUS, -1, 0) = 0x411e4000 5869 munmap(0x411e4000, 32768) = 0 5869 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE| MAP_ANONYMOUS, -1, 0) = 0x411e4000 5869 munmap(0x411e4000, 32768) = 0 5869 open("/home/hanne/.gimp-2.2", O_RDONLY|O_NONBLOCK|O_LARGEFILE| O_DIRECTORY) = 4 5869 fstat64(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 5869 fcntl64(4, F_SETFD, FD_CLOEXEC) = 0 5869 getdents64(4, /* 23 entries */, 4096) = 720 5869 getdents64(4, /* 0 entries */, 4096) = 0 5869 close(4) = 0 5869 mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE| MAP_ANONYMOUS, -1, 0) = 0x411e4000 5869 munmap(0x411e4000, 32768) = 0 5869 open("/home/hanne/.gimp-2.2/gimpswap.5869", O_RDWR|O_CREAT| O_LARGEFILE, 0600) = 4 5869 close(4) = 0 5869 unlink("/home/hanne/.gimp-2.2/gimpswap.5869") = 0 5869 --- SIGILL (Illegal instruction) @ 0 (0) --- 5869 +++ killed by SIGILL +++ Best regards :o) Johnny :o)

Greetings Carlos, and thank you for your effort this far. :o) Sorry about the delay. The computer owner was out of town and I had some homework to tend to. Onsdag 01 februar 2006 01:57 kvad Carlos E. R.:

Perhaps... try reducing memory used. You can look the variables in "/etc/gimp-2.2/gimprc". These seem interesting:

On this SUSE Linux 10.0 the path is: /etc/gimp/2.0/gimprc

# There is always a tradeoff between memory usage and speed. In most cases, # the GIMP opts for speed over memory. However, if memory is a big issue, # try to enable this setting. Possible values are yes and no. # # (stingy-memory-use no)

Try "yes".

This stingy thing is not in our gimprc. Neither the one under /etc nor in the one under ~/.gimp-2.2

# (tile-cache-size 128M)

Try a lower setting.

We tried 32M No luck -- Gimp still does not start.

...

...

If you start gimp from an xterm you might see an error message.

Yes. The message is: hanne@comp:~> gimp Illegal instruction (SIGILL) hanne@comp:~>

It seems a bug in gimp that surfaces with your hardware. I see that gimp has some options:

--verbose Show startup messages. -c, --console-messages Display warnings to console instead of a dialog box. --debug-handlers Enable non-fatal debugging signal handlers. --stack-trace-mode <never | query | always> Debugging mode for fatal signals.

But I doubt they might help here.

No harm in trying them out. We did: gimp --verbose -c --stack-trace-mode always And the computer replied: INIT: gimp_load_config Interpreter '/etc/gimp/2.0/gimprc' Interpreter '/home/hanne/.gimp-2.2/gimprc' Illegal instruction (SIGILL)

...

mmap2(NULL, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x411e4000 munmap(0x411e4000, 32768) = 0 open("/home/hanne/.gimp-2.2/gimpswap.5863", O_RDWR|O_CREAT|O_LARGEFILE, 0600) = 4 close(4) = 0 unlink("/home/hanne/.gimp-2.2/gimpswap.5863") = 0 --- SIGILL (Illegal instruction) @ 0 (0) --- +++ killed by SIGILL +++

It seems a problem after opening the local swap file. The partition has no problems, and is local, I suppose?

Everything is local. It is a home desktop computer with one hard drive and only modem connection to the internet. So no network drives or other such stuff. All is on the same partition except /boot and Linux swap. /boot has its own partition. Linux swap has its own partition. All other programs has no problems reading and writing to the same partition as gimp (the same partition they are all on). Best regards :o) Johnny :o)

Greetings Carlos, Tirsdag 07 februar 2006 20:53 kvad Carlos E. R.:

Anyway, my /etc/gimp/2.0/gimprc does have the variables I mentioned the other day.

We tried putting the variable in gimprc, but it still does not start. Thank you very much for all your good efforts Carlos :o)

It seems the only solution would be to get either an older version of gimp, or newer; hope it is a bug that is not present in another version.

That I will look into now. I have never compiled anything before, so I will learn something very new this time. :o) Do you think compiling SUSE's GIMP source for SUSE Linux 10.0 for the exact architecture would do a difference? Or should I go directy to the newest stable vanillla GIMP source? Best regards :o) Johnny :o)

Greetings Carlos, Johnny wrote:

...

Do you think compiling SUSE's GIMP source for SUSE Linux 10.0 for the exact architecture would do a difference?

Torsdag 02 marts 2006 02:08 kvad Carlos E. R.:

I doubt it. It could be, perhaps, optimizing for size if that's an issue, but I was thinking of compiling a different version, in case it is a bug.

...

Or should I go directy to the newest stable vanillla GIMP source?

Well... I have never tried to compile The Gimp, so I don't know how difficult or easy it is, but I can tell you that I would do it with respect (I don't know if you understand my meaning, it is "an idiom"). I would at least look at SuSE's spec file to see how they compiled it. Perhaps they are also using some patches, they usually do with many packages.

Thank you for your suggestions. Thank you for your effort on my issue. :o) I will look into it. Best regards :o) Johnny :o)