Bug 665021 – Crash in message_info_from_uid at camel-folder-summary.c:1765

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 665021 - Crash in message_info_from_uid at camel-folder-summary.c:1765


Summary:	Crash in message_info_from_uid at camel-folder-summary.c:1765


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	3.10.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-11-28 10:16 UTC by Akhil Laddha
Modified:	2018-12-12 14:56 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
gdb backtrace full (2.32 KB, text/plain) 2013-02-13 15:33 UTC, Martin Erik Werner	Details

Description Akhil Laddha 2011-11-28 10:16:30 UTC

Evolution 3.3.3

Nothing specific, evolution was idle for a while, returned to Evolution window and found that evolution has crashed.

(evolution:30342): camel-CRITICAL **: camel_folder_get_full_name: assertion `CAMEL_IS_FOLDER (folder)' failed

(evolution:30342): camel-CRITICAL **: camel_folder_get_parent_store: assertion `CAMEL_IS_FOLDER (folder)' failed

Program received signal SIGSEGV, Segmentation fault.

+ Trace 229153

Thread 2 (Thread 0xb5e4fb70 (LWP 30343))

#0 read
at ../sysdeps/unix/syscall-template.S line 82
#1 read
at /usr/include/bits/unistd.h line 45
#2 unix_signal_helper_thread
at gmain.c line 4551
#3 g_thread_create_proxy
at gthread.c line 1962
#4 start_thread
at pthread_create.c line 301
#5 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 133


        shell = 0x8132030 [EShell]
---Type <return> to continue, or q <return> to quit---
        settings = 0x8127a50 [GParamObject]
        skip_warning_dialog = 1
        error = 0x0

Comment 1 Martin Erik Werner 2013-02-13 15:33:44 UTC

Created attachment 235895 [details]
gdb backtrace full

Comment 2 Martin Erik Werner 2013-02-13 15:34:33 UTC

I'm seeing this crash quite frequently on version 3.6.3-1 in Debian Sid.

gdb backtrace attached.

Comment 3 Milan Crha 2014-09-22 10:56:05 UTC

Similar downstream bug report from evolution 3.10.4:
https://bugzilla.redhat.com/show_bug.cgi?id=1144749

Version-Release number of selected component:
evolution-3.10.4-3.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        evolution
crash_function: message_info_from_uid
executable:     /usr/bin/evolution
kernel:         3.15.10-201.fc20.x86_64

Core was generated by `evolution'.
Program terminated with signal SIGSEGV, Segmentation fault.

+ Trace 234115

Thread 1 (Thread 0x7f043f59fa40 (LWP 2508))

#0 message_info_from_uid
at camel-folder-summary.c line 1919
#1 vee_info_uint32
at camel-vee-summary.c line 104
#2 is_node_selectable
at message-list.c line 3640
#3 find_next_selectable
at message-list.c line 3688
#4 build_tree
at message-list.c line 3848
#5 message_list_regen_done_cb
at message-list.c line 5597
#6 g_simple_async_result_complete
at gsimpleasyncresult.c line 777
#7 complete_in_idle_cb_for_thread
at gsimpleasyncresult.c line 845
#8 g_main_dispatch
at gmain.c line 3066
#9 g_main_context_dispatch
at gmain.c line 3642
#10 g_main_context_iterate
at gmain.c line 3713
#11 g_main_loop_run
at gmain.c line 3907
#12 gtk_main
at gtkmain.c line 1158
#13 main
at main.c line 683

Comment 4 Milan Crha 2018-12-12 14:56:55 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.