The program suddently crashed....

Thanks for taking the time to report this bug. Unfortunately, we are
not able to fix and find the bug because your description of the bug
didn't have enough information in it. You may find it helpful to read
"How to report bugs effectively",
        http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.
We'd be grateful if you would then provide a more complete description
of the problem.

Debugging procedures for certain types of problems can be found at
http://wiki.ubuntu.com/DebuggingProcedures

I've attached the dump file generated by Ubuntu. I had some problems with the browser so that's why this attachment was not initially sent.

Can you please attach the file you were trying to edit?

debug backtrace:

"(gdb) bt
#0 0xb7801851 in handlers_find (instance=<value optimized out>, mask=<value optimized out>, signal_id=0, detail=0,
    closure=0x0, func=0xb7c9a080, data=0x8dedc90, one_and_only=0) at gsignal.c:476
#1 0xb78090db in signal_handlers_foreach_matched_R (instance=0x8da47a8, mask=148823184, signal_id=151400344, detail=0,
    closure=0x0, func=0xb7c9a080, data=0x8dedc90, callback=0xb7808420 <IA__g_signal_handler_disconnect>) at gsignal.c:1849
#2 0xb78096ec in IA__g_signal_handlers_disconnect_matched (instance=0x8da47a8, mask=24, signal_id=0, detail=0,
    closure=0x0, func=0xb7c9a080, data=0x8dedc90) at gsignal.c:1934
#3 0xb7c9a133 in gtk_tearoff_menu_item_parent_set (widget=0x8dedc90, previous=0x8da47a8) at gtktearoffmenuitem.c:241
#4 0xb77ff039 in IA__g_cclosure_marshal_VOID__OBJECT (closure=0x83a9860, return_value=0x0, n_param_values=2,
    param_values=0xbfd0708c, invocation_hint=0xbfd06f9c, marshal_data=0xb7c9a0b0) at gmarshal.c:636
#5 0xb77f0fb9 in g_type_class_meta_marshal (closure=0x83a9860, return_value=0x0, n_param_values=2,
    param_values=0xbfd0708c, invocation_hint=0xbfd06f9c, marshal_data=0x88) at gclosure.c:567
#6 0xb77f279b in IA__g_closure_invoke (closure=0x83a9860, return_value=0x0, n_param_values=2, param_values=0xbfd0708c,
    invocation_hint=0xbfd06f9c) at gclosure.c:490
#7 0xb780302a in signal_emit_unlocked_R (node=0x83a9908, detail=0, instance=0x8dedc90, emission_return=0x0,
    instance_and_params=0xbfd0708c) at gsignal.c:2370
#8 0xb78040b7 in IA__g_signal_emit_valist (instance=0x8dedc90, signal_id=17, detail=0, var_args=0xbfd072d0 "\210;")
    at gsignal.c:2199
#9 0xb7804279 in IA__g_signal_emit (instance=0x8dedc90, signal_id=17, detail=0) at gsignal.c:2243
..."

that looks like a GTK issue

I must say that I'm working with a beta-release of the nVidia drivers.
Maybe that hacked the GTK components and Gimp payed the bill.

Thank you for your speed handling the (possible) bug.

Best regards,
Jaume,

En/na Sebastien Bacher ha escrit:
> debug backtrace:
>
> "(gdb) bt
> #0 0xb7801851 in handlers_find (instance=<value optimized out>, mask=<value optimized out>, signal_id=0, detail=0,
> closure=0x0, func=0xb7c9a080, data=0x8dedc90, one_and_only=0) at gsignal.c:476
> #1 0xb78090db in signal_handlers_foreach_matched_R (instance=0x8da47a8, mask=148823184, signal_id=151400344, detail=0,
> closure=0x0, func=0xb7c9a080, data=0x8dedc90, callback=0xb7808420 <IA__g_signal_handler_disconnect>) at gsignal.c:1849
> #2 0xb78096ec in IA__g_signal_handlers_disconnect_matched (instance=0x8da47a8, mask=24, signal_id=0, detail=0,
> closure=0x0, func=0xb7c9a080, data=0x8dedc90) at gsignal.c:1934
> #3 0xb7c9a133 in gtk_tearoff_menu_item_parent_set (widget=0x8dedc90, previous=0x8da47a8) at gtktearoffmenuitem.c:241
> #4 0xb77ff039 in IA__g_cclosure_marshal_VOID__OBJECT (closure=0x83a9860, return_value=0x0, n_param_values=2,
> param_values=0xbfd0708c, invocation_hint=0xbfd06f9c, marshal_data=0xb7c9a0b0) at gmarshal.c:636
> #5 0xb77f0fb9 in g_type_class_meta_marshal (closure=0x83a9860, return_value=0x0, n_param_values=2,
> param_values=0xbfd0708c, invocation_hint=0xbfd06f9c, marshal_data=0x88) at gclosure.c:567
> #6 0xb77f279b in IA__g_closure_invoke (closure=0x83a9860, return_value=0x0, n_param_values=2, param_values=0xbfd0708c,
> invocation_hint=0xbfd06f9c) at gclosure.c:490
> #7 0xb780302a in signal_emit_unlocked_R (node=0x83a9908, detail=0, instance=0x8dedc90, emission_return=0x0,
> instance_and_params=0xbfd0708c) at gsignal.c:2370
> #8 0xb78040b7 in IA__g_signal_emit_valist (instance=0x8dedc90, signal_id=17, detail=0, var_args=0xbfd072d0 "\210;")
> at gsignal.c:2199
> #9 0xb7804279 in IA__g_signal_emit (instance=0x8dedc90, signal_id=17, detail=0) at gsignal.c:2243
> ...."
>
> that looks like a GTK issue
>

--
  Jaume Catarineu
  Noba Informatica, SL

Can you try with the 'nv' driver - just to be sure?

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.