Similiar problems where reported for CinePaint. Look at your libtiff
version. If it has 3.8.0 update or downgrad. This libtiff version is
buggy.
Hopd this helps.
kind regards
Kai-Uwe Behrmann
+ development for color management
+ imaging / panoramas
+ email: [EMAIL PROTECTED]
+ http://www.behrmann.name
Am 25.03.06, 01:19 -0300 schrieb Roberto Winter:
> hi.
>
> as i saved a file just now gimp crashed. i had it built from cvs some 10
> days ago (gcc 3.3.5).
> i'm using debian unstable, e16 window manager, nvidia drivers 8178 on xorg
> and kernel 2.6.13.1 .
>
> on the terminal i got:
>
> file_save_dialog_check_uri: URI =
> file:///home/media/fotos_tangara/xcf/tif/IMG_6384.TIF
>
> file_save_dialog_check_uri: basename = IMG_6384.TIF
> file_save_dialog_check_uri: selected save_proc: NULL
> file_save_dialog_check_uri: URI save_proc: TIFF image
> file_save_dialog_check_uri: basename save_proc: TIFF image
>
> file_save_dialog_check_uri: no save_proc was selected from the list
> file_save_dialog_check_uri: use URI's proc 'TIFF image' so indirect saving
> works
> *** glibc detected *** corrupted double-linked list: 0x0a86a390 ***
> /opt/gimp/bin/gimp-2.3: terminated: Aborted
>
> (script-fu:4033): LibGimpBase-WARNING **: script-fu: wire_read(): error
>
> the image is a 8Mp photograph. it was a single layer file.
>
> is this known? should i report a bug (i suspect it might be something with
> my environment, not gimp)? has it been noticed? fixed?
> the thing is it had been running absolutely stable the last days. and the
> weirder is that it crashed while doing something that i do often (saving as
> tif).
> another thing that might matter is that the file was written fine and is not
> corrupted (~10Mb in size).
>
> thanks for any help,
> roberto
>
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
