Hi,
On Fri, 2007-11-02 at 13:59 +0100, Stephan Hegel wrote:
> Further analysis revealed:
> The problem is, that Gimp 2.4.1 tries to convert existing .gimp-2.2
> resp. .gimp-2.3 directories to .gimp-2.4. This doesn't seem to be
> perfect. My guess (just a guess !): the templates aren't converted
>
Hi,
On Fri, 2007-11-02 at 12:25 +0100, Stephan Hegel wrote:
> I've got the following problem with a self-compiled Gimp 2.4.1 on an
> openSuse 10.3 box (x86_64) when doing a simple "File->New" with no
> image open before:
>
> [prompt]/home/steve: gimp
> *** glibc detected *** gimp: double free or
Alex,
All clear.
Thanks for the rpm -q output. Exactly the same like on my box.
Further analysis revealed:
The problem is, that Gimp 2.4.1 tries to convert existing .gimp-2.2
resp. .gimp-2.3 directories to .gimp-2.4. This doesn't seem to be
perfect. My guess (just a guess !): the templates aren'
Checked on openSuse 10.3 (x86_64, AMD) with last
updates installed.
Work fine, without described error.
Configure options:
--prefix=/home/alex/programs/gimp
--disable-default-binary --disable-python
--- Stephan Hegel <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've got the following problem with a s
Hi,
I've got the following problem with a self-compiled Gimp 2.4.1 on an
openSuse 10.3 box (x86_64) when doing a simple "File->New" with no
image open before:
[prompt]/home/steve: gimp
*** glibc detected *** gimp: double free or corruption (out):
0x037f2e40 ***
Killed
Glib2 and Gtk2 and
