[Gimp-developer] [SVN 24537], SIGSEGV in Colors - Curves

2008-01-05 Thread Jean-Luc Coulon (f5ibh) 

Hi,

- I've loaded a tif file (43M)
- called Colors - Curves
- got a SIGSEGV

Attached the gdb session

BTW : the same operation on the same file works with 2.4.3 

Regards (and happy 2008)

Jean-Luc
[New Thread 0x40800950 (LWP 12067)]
[New Thread 0x41001950 (LWP 12068)]
[New Thread 0x41802950 (LWP 12069)]
[New Thread 0x42003950 (LWP 12070)]
Removing duplicate PDB procedure 'file-psd-load' registered by 
'/opt/gimp-2.5.0/lib/gimp/2.0/plug-ins/psd-load'
[New Thread 0x42804950 (LWP 12083)]
[New Thread 0x43005950 (LWP 12084)]
[Thread 0x43005950 (LWP 12084) exited]
[Thread 0x42804950 (LWP 12083) exited]
[New Thread 0x42804950 (LWP 12086)]
[New Thread 0x43005950 (LWP 12087)]
[New Thread 0x43806950 (LWP 12088)]
[New Thread 0x44007950 (LWP 12089)]
[New Thread 0x44808950 (LWP 12090)]
[New Thread 0x45009950 (LWP 12091)]
[Thread 0x45009950 (LWP 12091) exited]
[Thread 0x43806950 (LWP 12088) exited]
[Thread 0x44808950 (LWP 12090) exited]
[Thread 0x44007950 (LWP 12089) exited]
[Thread 0x43005950 (LWP 12087) exited]
[Thread 0x42804950 (LWP 12086) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x2aaef13357e0 (LWP 12062)]
0x in ?? ()
(gdb) bt
#0  0x in ?? ()
#1  0x004dfe1e in gimp_image_map_tool_create_map (tool=0xaa4b10)
at gimpimagemaptool.c:448
#2  0x004dff6b in gimp_image_map_tool_initialize (
tool=value optimized out, display=0x1f43580, error=value optimized out)
at gimpimagemaptool.c:337
#3  0x004d5226 in gimp_curves_tool_initialize (tool=0xaa4b10, 
display=0x1f43580, error=0x7fffbff16538) at gimpcurvestool.c:241
#4  0x00502e56 in gimp_tool_initialize (tool=0xaa4b10, 
display=0x1f43580) at gimptool.c:427
#5  0x004c97d4 in tool_manager_initialize_active (
gimp=value optimized out, display=0x1f43580) at tool_manager.c:236
#6  0x2aaeee555a1f in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#7  0x2aaeee5696e8 in ?? () from /usr/lib/libgobject-2.0.so.0
#8  0x2aaeee56b145 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#9  0x2aaeee56b533 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#10 0x2aaeee555a1f in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#11 0x2aaeee5693be in ?? () from /usr/lib/libgobject-2.0.so.0
#12 0x2aaeee56b145 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#13 0x2aaeee56b533 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#14 0x2aaeebdada73 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x2aaeee555a1f in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#16 0x2aaeee5696e8 in ?? () from /usr/lib/libgobject-2.0.so.0
#17 0x2aaeee56b145 in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#18 0x2aaeee56b533 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#19 0x2aaeebf92f88 in gtk_widget_activate ()
   from /usr/lib/libgtk-x11-2.0.so.0
#20 0x2aaeebe94166 in gtk_menu_shell_activate_item ()
   from /usr/lib/libgtk-x11-2.0.so.0
#21 0x2aaeebe95b26 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#22 0x2aaeebe87d9f in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#23 0x2aaeee555a1f in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#24 0x2aaeee569ac8 in ?? () from /usr/lib/libgobject-2.0.so.0
#25 0x2aaeee56ae6f in g_signal_emit_valist ()
   from /usr/lib/libgobject-2.0.so.0
#26 0x2aaeee56b533 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#27 0x2aaeebf8ec05 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#28 0x2aaeebe810b2 in gtk_propagate_event ()
   from /usr/lib/libgtk-x11-2.0.so.0
#29 0x2aaeebe82055 in gtk_main_do_event ()
   from /usr/lib/libgtk-x11-2.0.so.0
#30 0x2aaeec33e22c in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#31 0x2aaeef061e24 in g_main_context_dispatch ()
---Type return to continue, or q return to quit---
   from /usr/lib/libglib-2.0.so.0
#32 0x2aaeef06510d in ?? () from /usr/lib/libglib-2.0.so.0
#33 0x2aaeef065407 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#34 0x0046a857 in app_run (full_prog_name=value optimized out, 
filenames=0x0, alternate_system_gimprc=0x0, alternate_gimprc=0x0, 
session_name=value optimized out, batch_interpreter=0x0, 
batch_commands=0x0, as_new=0, no_interface=0, no_data=0, no_fonts=0, 
no_splash=0, be_verbose=0, use_shm=1, use_cpu_accel=1, console_messages=0, 
use_debug_handler=0, stack_trace_mode=GIMP_STACK_TRACE_QUERY, 
pdb_compat_mode=GIMP_PDB_COMPAT_WARN) at app.c:252
#35 0x0046b7be in main (argc=1, argv=0x7fffbff18498) at main.c:387
(gdb) 





pgp2LOEiQs1vS.pgp
Description: PGP signature
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] [SVN 24537], SIGSEGV in Colors - Curves

2008-01-05 Thread William Skaggs 

From: Jean-Luc Coulon (f5ibh) [EMAIL PROTECTED]
 - I've loaded a tif file (43M)
 - called Colors - Curves
 - got a SIGSEGV

You can expect some instability for a while, because of the
introduction of gegl into the tools.  It probably isn't useful
to file bug reports or send messages to this list until things
have stabilized a bit -- or if you have a problem that persists
for longer than a week.  A mention on #gimp would certainly
be appropriate, though.

Best wishes,

  -- Bill

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] [SVN 24537], SIGSEGV in Colors - Curves

2008-01-05 Thread Kevin Cozens 
Jean-Luc Coulon (f5ibh) wrote:
 - I've loaded a tif file (43M) - called Colors - Curves - got a SIGSEGV
 
 Attached the gdb session

 From the gdb session messages:
 Removing duplicate PDB procedure 'file-psd-load' registered by
 '/opt/gimp-2.5.0/lib/gimp/2.0/plug-ins/psd-load'

In late December there was an update to the PSD file loader. The old loader 
was called psd-load. The new PSD loader is called psd. The message above 
indicates you still have the old PSD file loader installed. Remove the 
psd-load file referenced in the above message.

-- 
Cheers!

Kevin.

http://www.ve3syb.ca/   |What are we going to do today, Borg?
Owner of Elecraft K2 #2172  |Same thing we always do, Pinkutus:
 |  Try to assimilate the world!
#include disclaimer/favourite |  -Pinkutus  the Borg
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Gimp-developer] Haze on GIMP 2.4 image - Should this be a bug report?

2008-01-05 Thread Mark Lowry 
Attached is a link to a screen capture showing the
same image opened in Windows Picture and Fax viewer
and in GIMP 2.4.  As you can see, the GIMP version (no
editing performed) has a haze compared to the WPF
viewer version.

http://vabirdy.tripod.com/images/puppypics/gimp_jpeg_haze.jpg

This is very annoying, but I'm not sure which viewer
is at fault.  Should I submit a bug report for this?

Thanks . Mark



  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

Re: [Gimp-developer] Haze on GIMP 2.4 image - Should this be a bug report?

2008-01-05 Thread Martin Nordholts 
Mark Lowry skrev:
 Attached is a link to a screen capture showing the
 same image opened in Windows Picture and Fax viewer
 and in GIMP 2.4.  As you can see, the GIMP version (no
 editing performed) has a haze compared to the WPF
 viewer version.
 
 http://vabirdy.tripod.com/images/puppypics/gimp_jpeg_haze.jpg
 
 This is very annoying, but I'm not sure which viewer
 is at fault.  Should I submit a bug report for this?
 
 Thanks . Mark
 

Hello

This is probably a color management issue. I don't think the image
viewer in Windows is color managed, so if you also disable display color
management in GIMP (File - Preferences - Color Management - set
Monitor Profile to None and uncheck Try to use the system monitor
profile), does this still happen?

Martin

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer