gimp segfaults

[Debian Bug Importer]

Automatically imported from Debian bug report #298723 http://bugs.debian.org/298723

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #298723 http://bugs.debian.org/298723

[Justin Pryzby (justinpryzby-users)]

Hello,

You recently submitted a bug report on Debian's Gimp package [0]; cou
you provide more information?

If you

  cd;
  ulimit -c unlimited;
  rm -fr .gimp*;
  gimp;

you should get a 'core' file. Does

  gdb core $(which gimp)
  bt

give a sane backtrace (or does it say "stack corrupted?").

Was this problem present on previous version of gimp? Is it only
present when removing ~/.gimp*? Did gimp work immediately before
remove those files?

What if you run LANG=C gimp instead?

Thanks,
Justin

References

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298723

[Ari Pollak (ari)]

severity 298723 important
severity 297254 minor

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 09 Mar 2005 12:00:45 -0500
From: Ari Pollak <email address hidden>
To: <email address hidden>
Subject: (no subject)

severity 298723 important
severity 297254 minor

[Debian Bug Importer (debzilla)]

Message-ID: <20050309164807.GA29692@andromeda>
Date: Wed, 9 Mar 2005 11:48:12 -0500
From: Justin Pryzby <email address hidden>
To: <email address hidden>
Subject: gimp crash

Hello,

You recently submitted a bug report on Debian's Gimp package [0]; cou
you provide more information?

If you

  cd;
  ulimit -c unlimited;
  rm -fr .gimp*;
  gimp;

you should get a 'core' file. Does

  gdb core $(which gimp)
  bt

give a sane backtrace (or does it say "stack corrupted?").

Was this problem present on previous version of gimp? Is it only
present when removing ~/.gimp*? Did gimp work immediately before
remove those files?

What if you run LANG=C gimp instead?

Thanks,
Justin

References

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298723

[Ari Pollak (ari)]

Since you didn't tell me how to reproduce this (and especially whether
/tmp is full or not), I'm going to need a backtrace. Instructions on how
to do this correctly are up here: http://wiki.debian.net/?HowToGetABacktrace

You can probably work around this by just setting your swap directory to
the normal .gimp-2.2 directory.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 09 Mar 2005 12:39:55 -0500
From: Ari Pollak <email address hidden>
To: Franz Georg Koehler <email address hidden>, <email address hidden>
Subject: Re: Bug#298723: gimp segfaults

Since you didn't tell me how to reproduce this (and especially whether
/tmp is full or not), I'm going to need a backtrace. Instructions on how
to do this correctly are up here: http://wiki.debian.net/?HowToGetABacktrace

You can probably work around this by just setting your swap directory to
the normal .gimp-2.2 directory.

[Franz Georg Koehler (fgkoehler)]

On Mi, Mär 09, 2005 at 11:48:12 -0500, Justin Pryzby <email address hidden> wrote:
> Hello,
>
> You recently submitted a bug report on Debian's Gimp package [0]; cou
> you provide more information?
>
> If you
>
> cd;
> ulimit -c unlimited;
> rm -fr .gimp*;
> gimp;
>
> you should get a 'core' file. Does
>
> gdb core $(which gimp)
> bt
>
> give a sane backtrace (or does it say "stack corrupted?").
>
> Was this problem present on previous version of gimp? Is it only
> present when removing ~/.gimp*? Did gimp work immediately before
> remove those files?
>
> What if you run LANG=C gimp instead?

Hello,

gimp used to work some time ago, I can't remember when I started gimp up the
last time (probably a few month ago).

gimp did segfault with my old ~/.gimp installed, I therefore removed that
directory.

This are my filesystems:

Filesystem Size Used Avail Use% Mounted on
/dev/sda2 17G 17G 355M 98% /
tmpfs 252M 0 252M 0% /dev/shm
/dev/sda1 23M 11M 12M 47% /boot
phoenix:/home 42G 34G 6,5G 84% /home
orion:/var/ftp 11G 9,9G 381M 97% /ftp.bofh.hanau.net

Backtrace information below:

19:49:30 fgk@fgk:~$ gdb $(which gimp) core
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

(no debugging symbols found)
Core was generated by `gimp'.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /usr/lib/libgimpwidgets-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpwidgets-2.0.so.0
Reading symbols from /usr/lib/libgimpmodule-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpmodule-2.0.so.0
Reading symbols from /usr/lib/libgimpcolor-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpcolor-2.0.so.0
Reading symbols from /usr/lib/libgimpthumb-2.0.so.0...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpthumb-2.0.so.0
Reading symbols from /usr/lib/libgimpmath-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpmath-2.0.so.0
Reading symbols from /usr/lib/libgimpbase-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpbase-2.0.so.0
Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0
Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0
Reading symbols from /usr/lib/libatk-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libatk-1.0.so.0
Reading symbol...

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 9 Mar 2005 19:56:36 +0100
From: Franz Georg =?utf-8?Q?K=C3=B6hler?= <email address hidden>
To: Justin Pryzby <email address hidden>,
 <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#298723: gimp crash

On Mi, Mär 09, 2005 at 11:48:12 -0500, Justin Pryzby <email address hidden> wrote:
> Hello,
>
> You recently submitted a bug report on Debian's Gimp package [0]; cou
> you provide more information?
>
> If you
>
> cd;
> ulimit -c unlimited;
> rm -fr .gimp*;
> gimp;
>
> you should get a 'core' file. Does
>
> gdb core $(which gimp)
> bt
>
> give a sane backtrace (or does it say "stack corrupted?").
>
> Was this problem present on previous version of gimp? Is it only
> present when removing ~/.gimp*? Did gimp work immediately before
> remove those files?
>
> What if you run LANG=C gimp instead?

Hello,

gimp used to work some time ago, I can't remember when I started gimp up the
last time (probably a few month ago).

gimp did segfault with my old ~/.gimp installed, I therefore removed that
directory.

This are my filesystems:

Filesystem Size Used Avail Use% Mounted on
/dev/sda2 17G 17G 355M 98% /
tmpfs 252M 0 252M 0% /dev/shm
/dev/sda1 23M 11M 12M 47% /boot
phoenix:/home 42G 34G 6,5G 84% /home
orion:/var/ftp 11G 9,9G 381M 97% /ftp.bofh.hanau.net

Backtrace information below:

19:49:30 fgk@fgk:~$ gdb $(which gimp) core
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-linux"...(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".

(no debugging symbols found)
Core was generated by `gimp'.
Program terminated with signal 11, Segmentation fault.

warning: current_sos: Can't read pathname for load map: Input/output error

Reading symbols from /usr/lib/libgimpwidgets-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpwidgets-2.0.so.0
Reading symbols from /usr/lib/libgimpmodule-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpmodule-2.0.so.0
Reading symbols from /usr/lib/libgimpcolor-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpcolor-2.0.so.0
Reading symbols from /usr/lib/libgimpthumb-2.0.so.0...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpthumb-2.0.so.0
Reading symbols from /usr/lib/libgimpmath-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpmath-2.0.so.0
Reading symbols from /usr/lib/libgimpbase-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgimpbase-2.0.so.0
Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...
(no debugging symbols found)...done.
Loaded symbols...

[Franz Georg Koehler (fgkoehler)]

All of the sudden, gimp works again...?!

[Ari Pollak (ari)]

Perhaps a corrupted file that got replaced. Closing bug, since you never
provided a workable backtrace and say it works again now.

Franz Georg Köhler wrote:
> All of the sudden, gimp works again...?!
>
>
>
>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 16 Mar 2005 20:49:34 +0100
From: Franz Georg =?utf-8?Q?K=C3=B6hler?= <email address hidden>
To: <email address hidden>
Subject: Re: Bug#298723: Acknowledgement (gimp segfaults)

All of the sudden, gimp works again...?!

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 16 Mar 2005 15:11:20 -0500
From: Ari Pollak <email address hidden>
To: <email address hidden>
Subject: Re: Bug#298723: Acknowledgement (gimp segfaults)

Perhaps a corrupted file that got replaced. Closing bug, since you never=20
provided a workable backtrace and say it works again now.

Franz Georg K=C3=B6hler wrote:
> All of the sudden, gimp works again...?!
>=20
>=20
>=20
>=20

[Sebastien Bacher (seb128)]

not a bug