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 617511 - Crash in summary_header_to_db at camel-vee-folder.c:784
Crash in summary_header_to_db at camel-vee-folder.c:784
Status: RESOLVED DUPLICATE of bug 617509
Product: evolution-mapi
Classification: Applications
Component: Mail
0.30.x
Other Linux
: Normal critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2010-05-03 10:23 UTC by Akhil Laddha
Modified: 2010-05-03 14:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description Akhil Laddha 2010-05-03 10:23:52 UTC 
evolution 0.31.1

Do File -> empty trash

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb25ffb70 (LWP 14736)]
0xb7c4b52f in summary_header_to_db (s=0x0, ex=0x0) at camel-vee-folder.c:784
784		full_name = camel_folder_get_full_name (s->folder);
(gdb) t a a bt

+ Trace 221682

Thread 30 (Thread 0xb25ffb70 (LWP 14736))

  • #0 summary_header_to_db
    at camel-vee-folder.c line 784
  • #1 vee_folder_finalize
    at camel-vee-folder.c line 957
  • #2 IA__g_object_unref
    at gobject.c line 2484
  • #3 empty_trash_exec
    at mail-ops.c line 1786
  • #4 mail_msg_proxy
    at mail-mt.c line 468
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 315
  • #6 g_thread_create_proxy
    at gthread.c line 1893
  • #7 start_thread
    at pthread_create.c line 297
  • #8 ??
    at pthread_create.c line 216 






Comment 1


Milan Crha





          2010-05-03 14:55:56 UTC
        



After work on bug #617509 this doesn't happen any more. But the fix there came to 0.31.2 release, thus it's possible there will be more duplicates for this with that version 0.31.1, thus from here will be a pointer to the other bug. I'm marking this as a duplicate of it.

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