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 632312 - crash sending mail ...
crash sending mail ...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 637305 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-10-16 19:37 UTC by Michael Meeks
Modified: 2018-12-12 14:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Meeks 2010-10-16 19:37:04 UTC


Thread 1 (Thread 0xb63f3870 (LWP 1765))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/libc.so.6
  • #2 g_poll
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 IA__gtk_dialog_run
    at gtkdialog.c line 1094
  • #6 action_mail_move_cb
    at e-mail-reader.c line 696
  • #7 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 _gtk_action_emit_activate
    at gtkaction.c line 794
  • #13 closure_accel_activate
    at gtkaction.c line 1764
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 IA__gtk_accel_group_activate
    at gtkaccelgroup.c line 889
  • #19 IA__gtk_accel_groups_activate
    at gtkaccelgroup.c line 926
  • #20 IA__gtk_window_activate_key
    at gtkwindow.c line 8348
  • #21 gtk_window_key_press_event
    at gtkwindow.c line 5225
  • #22 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 86
  • #23 ??
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #28 gtk_widget_event_internal
    at gtkwidget.c line 4977
  • #29 IA__gtk_propagate_event
    at gtkmain.c line 2434
  • #30 IA__gtk_main_do_event
    at gtkmain.c line 1665
  • #31 gdk_event_dispatch
    at gdkevents-x11.c line 2377
  • #32 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #33 ??
    from /usr/lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #35 IA__gtk_main
    at gtkmain.c line 1237
  • #36 main
    at main.c line 645

Comment 1 Michael Meeks 2010-10-16 19:38:56 UTC
I was using:

$ rpm -q evolution evolution-data-server
evolution-2.32.20100914-4.5.i586
evolution-data-server-2.32.20100914-8.16.i586
Comment 2 Milan Crha 2010-11-03 12:09:06 UTC
Seeing there that fortify_fail, could be compilation flags and/or gcc related here?
Comment 3 Milan Crha 2010-11-08 09:06:17 UTC
Downstream bug report about the same with 2.32.0:
https://bugzilla.redhat.com/show_bug.cgi?id=650575
Comment 4 Michael Meeks 2011-01-05 15:56:41 UTC
*** Bug 637305 has been marked as a duplicate of this bug. ***
Comment 5 Milan Crha 2011-02-11 12:26:30 UTC
valgrind log from bug #637836 shows that there was done some access out of bounds when reading indexes, which might be caused by a crash while data was about to save on a disk. I would try to remove all indexes from subfolders of
~/.local/share/evolution/mail
(*.ibex* files) and made it recreate them from scratch. There might be done some test for out-of-bounds reading, but I'm afraid it'll not fix the root problem on this.

Please make sure your ~/.evolution is gone, as the migration process to XDG folder structure didn't succeeded for you or you run also 2.30.x or earlier version after its migration to 2.32.x.
Comment 6 Yan Li 2011-05-04 04:50:29 UTC
Also see this issue several times a day with Debian's 2.32.3-1 package. Will try the method from the last comment.
Comment 7 Yan Li 2011-05-06 13:05:09 UTC
Tried Milan's advice and cleared *.ibex* files. Still getting crash several times a day. The backtraces look similar to the one from this bug report  :(
Comment 8 Matt 2012-01-31 23:13:12 UTC
I get a crash when I try to send to certain addresses, but not if I just use the plain email address.

Example:
crash with: Doug Butabi <doug@butabi.com>
no crash: doug@butabi.com

This only happens for certain addresses, not all I use.

Let me know if you need further info.
Comment 9 Milan Crha 2012-02-01 09:39:53 UTC
(In reply to comment #8)
> This only happens for certain addresses, not all I use.
> 
> Let me know if you need further info.

Is it still with 2.32.x or any more recent version, like 3.2.3? The 2.32.x is quite outdated, thus it is better to test with current stable, which is 3.2.3. It would be good to get updated backtrace, if it's reproducible there as well.
Comment 10 Matt 2012-02-01 11:49:45 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > This only happens for certain addresses, not all I use.
> > 
> > Let me know if you need further info.
> 
> Is it still with 2.32.x or any more recent version, like 3.2.3? The 2.32.x is
> quite outdated, thus it is better to test with current stable, which is 3.2.3.
> It would be good to get updated backtrace, if it's reproducible there as well.

It is version 3.2.2, running in Ubuntu oneiric. I'll do a backtrace as soon as I have time.
Comment 11 Milan Crha 2018-12-12 14:53:23 UTC
Thanks for a bug report. I'm closing this as obsolete, but feel free to reopen or comment in case you can reproduce with the current 3.30.x stable series.