Bug 575815 – crash in Evolution Mail and Calendar: Ran filter. Pressed Ctr...

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 575815 - crash in Evolution Mail and Calendar: Ran filter. Pressed Ctr...


Summary:	crash in Evolution Mail and Calendar: Ran filter. Pressed Ctr...


Status:	RESOLVED DUPLICATE of bug 561644

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.24.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-03-18 10:59 UTC by Dwayne Bailey
Modified:	2009-03-19 06:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Dwayne Bailey 2009-03-18 10:59:34 UTC

What were you doing when the application crashed?
Ran filter.  Pressed Ctrl-E. Crash


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.19-170.2.35.fc10.i686 #1 SMP Mon Feb 23 13:21:22 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 668999680 vsize: 668999680 resident: 103845888 share: 23285760 rss: 103845888 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237362388 rtime: 11476 utime: 9924 stime: 1552 cutime:24 cstime: 35 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb8049980 (LWP 12934)]
[New Thread 0xb7341b90 (LWP 12960)]
0x00454416 in __kernel_vsyscall ()

+ Trace 213590

Thread 1 (Thread 0xb8049980 (LWP 12934))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at gspawn.c line 694
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 segv_redirect
at main.c line 414
#8 <signal handler called>
#9 camel_message_info_free
at camel-folder-summary.c line 4363
#10 free_message_info
at camel-folder.c line 1027
#11 camel_folder_free_message_info
at camel-folder.c line 1045
#12 clear_info
at message-list.c line 2522
#13 IA__g_hash_table_foreach
at ghash.c line 1076
#14 clear_tree
at message-list.c line 2541
#15 build_tree
at message-list.c line 2712
#16 regen_list_done
at message-list.c line 4175
#17 mail_msg_idle_cb
at mail-mt.c line 500
#18 g_idle_dispatch
at gmain.c line 4235
#19 g_main_dispatch
at gmain.c line 2144
#20 IA__g_main_context_dispatch
at gmain.c line 2697
#21 g_main_context_iterate
at gmain.c line 2778
#22 IA__g_main_loop_run
at gmain.c line 2986
#23 bonobo_main
at bonobo-main.c line 311
#24 main
at main.c line 690



----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug/lib/libcom_err.so.2.1.debug" does not match "/lib/libcom_err.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//lib/libuuid.so.1.2.debug" does not match "/lib/libuuid.so.1" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/lib/libuuid.so.1.2.debug" does not match "/lib/libuuid.so.1" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libegroupwise-1.2.so.13.0.1.debug" does not match "/usr/lib/libegroupwise-1.2.so.13" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/libegroupwise-1.2.so.13.0.1.debug" does not match "/usr/lib/libegroupwise-1.2.so.13" (CRC mismatch).
--------------------------------------------------

Comment 1 Akhil Laddha 2009-03-19 06:08:48 UTC

Thanks for the bug report. 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 561644 ***