Bug 608567 – unknown crash

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 608567 - unknown crash


Summary:	unknown crash


Status:	RESOLVED DUPLICATE of bug 557613

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.28.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:	2010-01-31 01:30 UTC by Brian J. Murrell
Modified:	2010-02-16 03:22 UTC

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

Description Brian J. Murrell 2010-01-31 01:30:33 UTC

I can't really tell where this crashed.  Please do update the Summary: if you can determine.

+ Trace 220326

Thread 2 (Thread 24532)

#0 strcmp
at ../sysdeps/i386/i686/strcmp.S line 40
#1 camel_folder_summary_check_uid
at camel-folder-summary.c line 453
#2 message_info_from_uid
at camel-vee-summary.c line 362
#3 camel_folder_summary_uid
at camel-folder-summary.c line 620
#4 unmatched_check_uid
at camel-vee-folder.c line 1049
#5 IA__g_hash_table_foreach
at /build/buildd/glib2.0-2.22.3/glib/ghash.c line 1211
#6 vee_rebuild_folder
at camel-vee-folder.c line 1267
#7 vee_add_folder
at camel-vee-folder.c line 1939
#8 camel_vee_folder_add_folder
at camel-vee-folder.c line 226
#9 vfolder_adduri_exec
at mail-vfolder.c line 273
#10 mail_msg_proxy
at mail-mt.c line 522
#11 g_thread_pool_thread_proxy
at /build/buildd/glib2.0-2.22.3/glib/gthreadpool.c line 265
#12 g_thread_create_proxy
at /build/buildd/glib2.0-2.22.3/glib/gthread.c line 635
#13 start_thread
at pthread_create.c line 300
#14 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Thread 1 (Thread 24476)

#0 __pthread_mutex_lock
at pthread_mutex_lock.c line 50
#1 e_flag_set
at e-flag.c line 83
#2 try_open_e_book_cb
at em-utils.c line 2001
#3 emit_async_open_response
at e-book.c line 2814
#4 g_idle_dispatch
at /build/buildd/glib2.0-2.22.3/glib/gmain.c line 4065
#5 g_main_dispatch
at /build/buildd/glib2.0-2.22.3/glib/gmain.c line 1960
#6 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.22.3/glib/gmain.c line 2513
#7 g_main_context_iterate
at /build/buildd/glib2.0-2.22.3/glib/gmain.c line 2591
#8 IA__g_main_loop_run
at /build/buildd/glib2.0-2.22.3/glib/gmain.c line 2799
#9 bonobo_main
at bonobo-main.c line 311
#10 main
at main.c line 732

Comment 1 Akhil Laddha 2010-02-01 03:25:35 UTC

similar to bug 557613 or bug 602394. 

Do you have all the fixes applied from bug 557613 ?

Comment 2 Brian J. Murrell 2010-02-01 03:41:08 UTC

(In reply to comment #1)
> similar to bug 557613 or bug 602394. 
> 
> Do you have all the fixes applied from bug 557613 ?

No, none I would tend to think.  To be clear, attachment 121349 [details] [review], attachment 144486 [details] [review] and attachment 144487 [details] [review] should be applied?

Comment 3 Brian J. Murrell 2010-02-04 11:43:55 UTC

Akhil, if you get a moment, could you please answer comment #2 so that I can apply the correct patches?  Thanx.

Comment 4 Brian J. Murrell 2010-02-04 12:01:16 UTC

attachment 121349 [details] [review] does not apply to 2.28.1.  The code I have in my source is already similar to that patch.

attachment 144486 [details] [review] does apply to 2.28.1 so I will apply it to my build.

attachment 144487 [details] [review] does not apply to 2.28.1.  The code it patches doesn't even exist in my source.

Thots?

Comment 5 Akhil Laddha 2010-02-04 12:07:29 UTC

(In reply to comment #4)
> attachment 144487 [details] [review] does not apply to 2.28.1.  The code it patches doesn't even > exist in my source.
> 

This patch is only for master.

Comment 6 Milan Crha 2010-02-15 17:32:39 UTC

I agree with Akhil that this is an instance of bug #557613, thus can be closed as a duplicate.

Comment 7 Akhil Laddha 2010-02-16 03:22:13 UTC

Please feel free to open a new bug if you see crash even after applying fixes from bug #557613

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