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 758836 - Crash when moving a mail (camel_message_info_uint32)
Crash when moving a mail (camel_message_info_uint32)
Status: RESOLVED DUPLICATE of bug 757789
Product: evolution
Classification: Applications
Component: Mailer
3.18.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-11-30 11:45 UTC by Joachim Breitner
Modified: 2015-11-30 12:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Joachim Breitner 2015-11-30 11:45:57 UTC 
Hi,

since a while, I observe frequent, but not completely reproducible crashes in evolution, always and only when I move mails from a one folder to another.

The mails appear to have successfully been moved in all instances.

I then often re-start evolution under gdb, but then it no longer happens – until now:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6d0930b in camel_message_info_uint32 () from /usr/lib/libcamel-1.2.so.54
(gdb) bt

+ Trace 235774

  • #0 camel_message_info_uint32
    from /usr/lib/libcamel-1.2.so.54
  • #1 ??
    from /usr/lib/evolution/libevolution-mail.so.0
  • #2 ??
    from /usr/lib/evolution/libevolution-mail.so.0
  • #3 ??
    from /usr/lib/evolution/libevolution-mail.so.0
  • #4 g_simple_async_result_complete
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #5 ??
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #6 g_main_context_dispatch
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #7 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #9 gtk_main
    at /build/gtk+3.0-bNySRH/gtk+3.0-3.18.5/./gtk/gtkmain.c line 1241
  • #10 main 


I’ll try to get a nother backtrace with debugging information available, but as I said, they are not too frequent when running in gdb.

This is evolution 3.18.2-1, Debian unstable.
Comment 1 Milan Crha 2015-11-30 12:55:33 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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