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 234594 - editor table crash
editor table crash
Status: RESOLVED FIXED
Product: GtkHtml
Classification: Other
Component: html-editor-control
unspecified
Other All
: Normal blocker
: ---
Assigned To: gtkhtml-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-11-25 21:56 UTC by Dan Winship
Modified: 2003-03-08 17:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dan Winship 2002-11-25 21:56:11 UTC
Package: GtkHtml
Priority: Normal
Version: 1.1.6.99
Synopsis: editor table crash
Bugzilla-Product: GtkHtml
Bugzilla-Component: html-editor-control

Description:
Pasted some text with tables into the editor and then wrestled with
trying to get it to look the way I wanted it to instead of the way the
designer of the web page had wanted it to. Ran into lots of weirdnesses
(at one point I typed some text and it was inserting backwards), decided
to give up and try again, closed the editor, and it crashed.




Debugging Information:

Backtrace was generated from
'/opt/evolution/bin/gnome-gtkhtml-editor-1.1'

0x40d744d9 in wait4 () from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 664
  • #3 <signal handler called>
  • #4 html_object_destroy
    at htmlobject.c line 829
  • #5 delete_cells_undo_destroy
    at htmlengine-edit-table.c line 269
  • #6 html_undo_data_unref
    at htmlundo.c line 519
  • #7 html_undo_action_destroy
    at htmlundo-action.c line 55
  • #8 destroy_action_list
    at htmlundo.c line 76
  • #9 html_undo_destroy
    at htmlundo.c line 95
  • #10 html_engine_destroy
    at htmlengine.c line 3287
  • #11 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #12 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #13 gtk_signal_emit
    at gtksignal.c line 552
  • #14 gtk_object_shutdown
    at gtkobject.c line 255
  • #15 gtk_object_destroy
    at gtkobject.c line 246
  • #16 gtk_object_unref
    at gtkobject.c line 1177
  • #17 destroy
    at gtkhtml.c line 692
  • #18 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #19 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #20 gtk_signal_emit
    at gtksignal.c line 552
  • #21 gtk_object_shutdown
    at gtkobject.c line 255
  • #22 gtk_widget_shutdown
    at gtkwidget.c line 4392
  • #23 gtk_object_destroy
    at gtkobject.c line 246
  • #24 gtk_widget_destroy
    at gtkwidget.c line 1391
  • #25 gtk_bin_forall
    at gtkbin.c line 276
  • #26 e_scroll_frame_forall
    at e-scroll-frame.c line 501
  • #27 gtk_container_foreach
    at gtkcontainer.c line 1125
  • #28 gtk_container_destroy
    at gtkcontainer.c line 631
  • #29 e_scroll_frame_destroy
    at e-scroll-frame.c line 363
  • #30 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #31 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #32 gtk_signal_emit
    at gtksignal.c line 552
  • #33 gtk_object_shutdown
    at gtkobject.c line 255
  • #34 gtk_widget_shutdown
    at gtkwidget.c line 4392
  • #35 gtk_object_destroy
    at gtkobject.c line 246
  • #36 gtk_widget_destroy
    at gtkwidget.c line 1391
  • #37 gtk_box_forall
    at gtkbox.c line 776
  • #38 gtk_container_foreach
    at gtkcontainer.c line 1125
  • #39 gtk_container_destroy
    at gtkcontainer.c line 631
  • #40 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #41 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #42 gtk_signal_emit
    at gtksignal.c line 552
  • #43 gtk_object_shutdown
    at gtkobject.c line 255
  • #44 gtk_widget_shutdown
    at gtkwidget.c line 4392
  • #45 gtk_object_destroy
    at gtkobject.c line 246
  • #46 gtk_widget_destroy
    at gtkwidget.c line 1391
  • #47 gtk_bin_forall
    at gtkbin.c line 276
  • #48 gtk_container_foreach
    at gtkcontainer.c line 1125
  • #49 gtk_container_destroy
    at gtkcontainer.c line 631
  • #50 gtk_window_destroy
    at gtkwindow.c line 844
  • #51 bonobo_plug_new
    from /usr/lib/libbonobox.so.2
  • #52 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #53 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #54 gtk_signal_emit
    at gtksignal.c line 552
  • #55 gtk_object_shutdown
    at gtkobject.c line 255
  • #56 gtk_widget_shutdown
    at gtkwidget.c line 4392
  • #57 gtk_window_shutdown
    at gtkwindow.c line 664
  • #58 gtk_object_destroy
    at gtkobject.c line 246
  • #59 gtk_widget_destroy
    at gtkwidget.c line 1391
  • #60 gtk_main_do_event
    at gtkmain.c line 744
  • #61 gdk_event_dispatch
    at gdkevents.c line 2139
  • #62 g_main_dispatch
    at gmain.c line 656
  • #63 g_main_iterate
    at gmain.c line 877
  • #64 g_main_run
    at gmain.c line 935
  • #65 gtk_main
    at gtkmain.c line 524
  • #66 bonobo_main
    from /usr/lib/libbonobo.so.2
  • #67 main
    at editor-control-factory.c line 857
  • #68 __libc_start_main
    from /lib/libc.so.6


Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 yuedong du 2002-12-23 10:35:28 UTC
Step to reproduce this bug:

1. Select the outmost bound of the table.
2. Insert a table when compose a mail, delete one column.
3. Ctrl+Z to undo. the editor crash.

Actually, this just a part of design issue of table bad. I want to 
resolve it in bug 235557. So mark it as dup. 

If you do not agree with me, just change as you want.




*** This bug has been marked as a duplicate of 235557 ***
Comment 2 yuedong du 2002-12-24 02:58:57 UTC
The steps above maybe another bug. But the root reason maybe the same
to bug 235557.
Comment 3 yuedong du 2002-12-24 07:49:21 UTC
Sorry, after closer look at this problem, I think this one is very
likely to be different from the one I described. But I cannot
reproduce this one.

change as reopen.
Comment 4 Larry Ewing 2003-03-07 23:43:42 UTC
The table editing code has gone through a lot of changes, is this
reproducable?
Comment 5 Dan Winship 2003-03-08 17:55:16 UTC
I think I only saw it once, although I've tended to try to avoid
pissing off the table editor since then. :-)

Closing anyway though since if the code has changed the stack
trace isn't likely to do any good. I'll file a new one if I get
it again with the new code.