d4x- 2.5.0rel-1 segfaults when using "smooth" GTK themes

I'm using the industrial theme, and I crash also. Here is the gdb run and
backtrace:

(d4x:10722): Gdk-CRITICAL **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (g
c)' failed
(d4x:10722): Gdk-CRITICAL **: gdk_draw_line: assertion `GDK_IS_GC (gc)' failed
(d4x:10722): Gdk-CRITICAL **: gdk_draw_line: assertion `GDK_IS_GC (gc)' failed
(d4x:10722): Gdk-CRITICAL **: gdk_draw_line: assertion `GDK_IS_GC (gc)' failed
(d4x:10722): Gdk-CRITICAL **: gdk_draw_line: assertion `GDK_IS_GC (gc)' failed
(d4x:10722): Gdk-CRITICAL **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (g
c)' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1082850496 (LWP 10722)]
0x4048ea8f in g_type_check_instance_is_a () from /usr/lib/libgobject-2.0.so.0
(gdb) bt
#0 0x4048ea8f in g_type_check_instance_is_a ()
   from /usr/lib/libgobject-2.0.so.0
#1 0x403b884d in gdk_gc_set_clip_rectangle ()
   from /usr/lib/libgdk-x11-2.0.so.0
#2 0x413f2d9a in industrial_rc_style_register_type ()
   from /usr/lib/gtk-2.0/2.4.0/engines/libindustrial.so
#3 0x413f5aa4 in industrial_rc_style_register_type ()
   from /usr/lib/gtk-2.0/2.4.0/engines/libindustrial.so
#4 0x413f65cb in industrial_rc_style_register_type ()
   from /usr/lib/gtk-2.0/2.4.0/engines/libindustrial.so
#5 0x402237df in gtk_paint_shadow () from /usr/lib/libgtk-x11-2.0.so.0
#6 0x080dc5de in my_gtk_graph_new ()
#7 0x080dcae1 in my_gtk_graph_new ()
#8 0x401cbbca in _gtk_marshal_BOOLEAN__BOXED ()
   from /usr/lib/libgtk-x11-2.0.so.0
#9 0x404765bf in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0
#10 0x40476351 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#11 0x40486270 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
#12 0x404856ef in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#13 0x40485b75 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#14 0x402ada11 in gtk_widget_send_expose () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x401c9792 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#16 0x403a48b2 in gdk_window_clear_area_e () from /usr/lib/libgdk-x11-2.0.so.0
#17 0x403a49e7 in gdk_window_process_all_updates ()
   from /usr/lib/libgdk-x11-2.0.so.0
#18 0x40146d6b in gtk_container_set_reallocate_redraws ()
   from /usr/lib/libgtk-x11-2.0.so.0
#19 0x4005da03 in g_child_watch_add () from /usr/lib/libglib-2.0.so.0
#20 0x4005ad0f in g_main_depth () from /usr/lib/libglib-2.0.so.0
#21 0x4005bcb5 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0x4005bfd7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0x4005c51e in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#24 0x401c910f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#25 0x08092099 in main ()

As suggested, switching to Human works.. changing back to Industrial while the
app is running seems to be fine too.

I can confirm this bug also, exactly the same thing happens for me.

For what it's worth, I tried to reproduce this bug on an up to date dapper, and Was unable to produce a backtrace, because each gnome application stopped working (they all segfaulted) once I switched to Nuvola. Including the gnome-terminal. I suppose that with some ingenious ssh setup one could produce a new backtrace, but it shouldn't be hard for the developers to reproduce it. However, if they can't please contact me and I'll try to reproduce it.

Does this still happen to anybody using Edgy?

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.