After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 576355 - crash in GNU Image Manipulation Program: Tools -
crash in GNU Image Manipulation Program: Tools -
Status: RESOLVED DUPLICATE of bug 574584
Product: GIMP
Classification: Other
Component: General
2.6.5
Other All
: High critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-03-23 08:00 UTC by d-i-g-i-t-a-l
Modified: 2009-03-23 19:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description d-i-g-i-t-a-l 2009-03-23 08:00:44 UTC 
What were you doing when the application crashed?
Tools -> GEGL Operations -> hstack

It always crashes there.


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.24.3 2009-01-22 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.28-gentoo-r3 #1 SMP PREEMPT Wed Mar 18 11:31:45 SAMT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 66080768 vsize: 66080768 resident: 43380736 share: 16990208 rss: 43380736 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237794653 rtime: 5002 utime: 4731 stime: 271 cutime:19 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gimp-2.6'

[Thread debugging using libthread_db enabled]
[New Thread 0xb734f6c0 (LWP 11439)]
0xffffe424 in __kernel_vsyscall ()

+ Trace 213744

Thread 1 (Thread 0xb734f6c0 (LWP 11439))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 bugbuddy_segv_handle
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 get_bounding_box
    from /usr/lib/gegl-0.0/hstack.so
  • #8 gegl_operation_get_bounding_box
    from /usr/lib/libgegl-0.0.so.0
  • #9 visit_node
    from /usr/lib/libgegl-0.0.so.0
  • #10 gegl_visitor_visit_node
    from /usr/lib/libgegl-0.0.so.0
  • #11 visitable_accept
    from /usr/lib/libgegl-0.0.so.0
  • #12 gegl_visitable_accept
    from /usr/lib/libgegl-0.0.so.0
  • #13 dfs_traverse
    from /usr/lib/libgegl-0.0.so.0
  • #14 dfs_traverse
    from /usr/lib/libgegl-0.0.so.0
  • #15 gegl_eval_mgr_apply
    from /usr/lib/libgegl-0.0.so.0
  • #16 gegl_node_blit
    from /usr/lib/libgegl-0.0.so.0
  • #17 gegl_processor_work
    from /usr/lib/libgegl-0.0.so.0
  • #18 gimp_image_map_do
  • #19 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 app_run
  • #24 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (41 sec old) ---------------------
** (gimp-2.6:11439): WARNING **: no format for gegl:c2g presuming RGBA float
** (gimp-2.6:11439): WARNING **: gegl_operation_get_format: returns NULL
** (gimp-2.6:11439): WARNING **: no format for gegl:c2g presuming RGBA float
(gimp-2.6:11439): Gimp-Tools-WARNING **: gimp_param_spec_duplicate: not supported: GeglParamCurve (curve)
** (gimp-2.6:11439): WARNING **: gegl_operation_get_format: returns NULL
** (gimp-2.6:11439): WARNING **: no format for gegl:demosaic-bimedian presuming RGBA float
--------------------------------------------------
Comment 1 palfrey 2009-03-23 17:17:59 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Sven Neumann 2009-03-23 19:40:56 UTC 

*** This bug has been marked as a duplicate of 574584 ***