Bug 433273 – crash in Evolution: clicked on the 'Unmatche...

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 433273 - crash in Evolution: clicked on the 'Unmatche...


Summary:	crash in Evolution: clicked on the 'Unmatche...


Status:	RESOLVED DUPLICATE of bug 352396

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

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

URL:
Whiteboard:

Duplicates:	482779 (view as bug list)
Depends on:
Blocks:

Reported:	2007-04-25 11:30 UTC by Jon
Modified:	2008-03-20 12:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Jon 2007-04-25 11:30:20 UTC

What were you doing when the application crashed?
clicked on the 'Unmatched' folder under 'Search Folders'. If it makes a difference, I had previously deleted one of my accounts


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 235335680 vsize: 0 resident: 235335680 share: 0 rss: 51556352 rss_rlim: 0
CPU usage: start_time: 1177498916 rtime: 0 utime: 1530 stime: 0 cutime:1430 cstime: 0 timeout: 100 it_real_value: 0 frequency: 4563

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232587088 (LWP 16992)]
[New Thread -1341559904 (LWP 17052)]
[New Thread -1374737504 (LWP 17026)]
[New Thread -1366344800 (LWP 17025)]
[New Thread -1357952096 (LWP 17022)]
[New Thread -1332773984 (LWP 17015)]
[New Thread -1265632352 (LWP 17014)]
[New Thread -1324381280 (LWP 17013)]
[New Thread -1315988576 (LWP 17012)]
[New Thread -1307595872 (LWP 17011)]
[New Thread -1290810464 (LWP 17009)]
[New Thread -1282417760 (LWP 17008)]
[New Thread -1274025056 (LWP 17007)]
[New Thread -1255310432 (LWP 17005)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 130474

Thread 1 (Thread -1232587088 (LWP 16992))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 segv_redirect
at main.c line 426
#4 <signal handler called>
#5 ??
#6 camel_message_info_uint32
at camel-folder-summary.c line 2985
#7 vee_info_uint32
at camel-vee-summary.c line 71
#8 camel_message_info_uint32
at camel-folder-summary.c line 2985
#9 folder_getv
at camel-folder.c line 352
#10 camel_object_get
at camel-object.c line 1598
#11 view_changed_timeout
at mail-component.c line 515
#12 g_timeout_dispatch
at gmain.c line 3422
#13 IA__g_main_context_dispatch
at gmain.c line 2045
#14 g_main_context_iterate
at gmain.c line 2677
#15 IA__g_main_loop_run
at gmain.c line 2881
#16 bonobo_main
from /usr/lib/libbonobo-2.so.0
#17 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 palfrey 2007-05-30 11:08:42 UTC

Can you reproduce this while running Evolution under gdb? See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details how to do this.

Comment 2 Karsten Bräckelmann 2007-06-30 00:02:14 UTC

No need to reproduce this under gdb, pretty decent stacktrace with debugging symbols.

Probably a duplicate of bug 352396 or bug 338218.

Comment 3 Reinout van Schouwen 2007-10-02 23:38:23 UTC

*** Bug 482779 has been marked as a duplicate of this bug. ***

Comment 4 Tobias Mueller 2008-03-20 12:31:23 UTC

I'd say, this is a dup of bug 352396, as already mentioned in comment #2. Thus marking as dup.

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