Mailinglist Archive: opensuse (3767 mails)

< Previous Next >
Re: [SLE] GIMP will not start...
  • From: Johnny Ernst Nielsen <j_e_n_pub@xxxxxxxx>
  • Date: Tue, 7 Feb 2006 17:50:22 +0100
  • Message-id: <200602071750.22829.j_e_n_pub@xxxxxxxx>
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)

< Previous Next >
Follow Ups
References