Bug 357082 – crash in Evolution: Keyed in a users name in...

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 357082 - crash in Evolution: Keyed in a users name in...


Summary:	crash in Evolution: Keyed in a users name in...


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

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

Reported:	2006-09-21 17:56 UTC by Wendell MacKenzie
Modified:	2010-05-07 04:54 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description Wendell MacKenzie 2006-09-21 17:56:36 UTC

What were you doing when the application crashed?
Keyed in a users name in the To: field when creating a new email message.


Distribution: SUSE LINUX 10.1 (i586)
Gnome Release: 2.16.0 2006-09-12 (GARNOME)
BugBuddy Version: 2.16.0

Memory status: size: 201220096 vsize: 0 resident: 201220096 share: 0 rss: 63561728 rss_rlim: 0
CPU usage: start_time: 1158854135 rtime: 0 utime: 1392 stime: 0 cutime:1307 cstime: 0 timeout: 85 it_real_value: 0 frequency: 0

Backtrace was generated from '/home/wendell/garnome/bin/evolution-2.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232935248 (LWP 9375)]
[New Thread -1416590432 (LWP 9445)]
[New Thread -1332397152 (LWP 9418)]
[New Thread -1323697248 (LWP 9405)]
[New Thread -1313317984 (LWP 9404)]
[New Thread -1304507488 (LWP 9401)]
[New Thread -1296114784 (LWP 9400)]
[New Thread -1287722080 (LWP 9397)]
[New Thread -1275155552 (LWP 9395)]
[New Thread -1266762848 (LWP 9394)]
[New Thread -1258370144 (LWP 9393)]
[New Thread -1249584224 (LWP 9392)]
[New Thread -1239868512 (LWP 9390)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72930

Thread 1 (Thread -1232935248 (LWP 9375))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 870
#3 <signal handler called>
#4 IA__g_type_check_instance_cast
at gtype.c line 3146
#5 ORBit_try_connection_T
at corba-object.c line 283
#6 ORBit_object_get_connection
at corba-object.c line 324
#7 ORBit_small_invoke_stub
at orbit-small.c line 631
#8 ORBit_small_invoke_stub_n
at orbit-small.c line 575
#9 ORBit_c_stub_invoke
at poa.c line 2643
#10 GNOME_Evolution_Addressbook_BookView_start
at Evolution-DataServer-Addressbook-stubs.c line 46
#11 e_book_view_start
at e-book-view.c line 225
#12 start_view
at e-contact-store.c line 668
#13 query_contact_source
at e-contact-store.c line 779
#14 e_contact_store_set_query
at e-contact-store.c line 986
#15 update_completions_on_idle_cb
at e-name-selector-entry.c line 503
#16 g_idle_dispatch
at gmain.c line 3926
#17 IA__g_main_context_dispatch
at gmain.c line 2045
#18 g_main_context_iterate
at gmain.c line 2677
#19 IA__g_main_loop_run
at gmain.c line 2881
#20 bonobo_main
at bonobo-main.c line 311
#21 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-25 20:00:47 UTC

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

Comment 2 Marc Harter 2009-04-16 15:04:13 UTC

Evolution MAPI is really buggy for me. I haven't got a apport crash report to popup but whenever I click on a Calendar Event in my Inbox Evolution crashes. It also will be unable to connect to the MAPI server after using it for maybe 3 minutes. I have to kill all the processes in order to run it again. It also give me an error whenever I try to send a message saying that it couldn't send the message although it "really" did.

Comment 3 André Klapper 2009-07-24 17:46:53 UTC

This crash report has been submitted against Evolution version 2.10 (or earlier).
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.26.

Can you please check again whether this issue still happens in Evolution 2.24 or 2.26 and update this report by adding a comment and changing the "Version" field?
Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.

Comment 4 Marc Harter 2009-07-24 18:06:59 UTC

Andre, I'm using Ubuntu 9.04 with Gnome 2.26.1 (and hence Evolution 2.26.1) and I am still seeing this issue (I'm unfamiliar with how to update the "Version", it seems as though I don't have enough permissions).  Let me know if there is anything I can do to help debug (test).

Comment 5 André Klapper 2009-07-24 19:57:06 UTC

Thanks.

Comment 6 Bharath Acharya 2010-03-25 05:41:05 UTC

Hello Marc,

The traces mentioned in comment #1 has some modules which we no longer use in 2.30.x

So please test for the crash against 2.28.x or 2.30.x and kindly update the crash traces in here. If it is MAPI specific, then let us move it against the right product :) NEEDINFO'ed

Comment 7 Akhil Laddha 2010-05-07 04:54:05 UTC

Closing this bug report as no further information has been provided. Please 
feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.30.0 or later, thanks.