Bug 417340 – crash in Evolution: a) Trying to send a mail...

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 417340 - crash in Evolution: a) Trying to send a mail...


Summary:	crash in Evolution: a) Trying to send a mail...


Status:	RESOLVED DUPLICATE of bug 378057

Product:	evolution
Classification:	Applications
Component:	general
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:

Depends on:
Blocks:

Reported:	2007-03-12 04:26 UTC by V Sridhar
Modified:	2007-04-02 01:07 UTC

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

Attachments
Calendar Crash Report (5.92 KB, text/plain) 2007-03-12 08:59 UTC, V Sridhar	Details

Description V Sridhar 2007-03-12 04:26:00 UTC

What were you doing when the application crashed?
a) Trying to send a mail. The LDAP autofill died. 
b) But the message which came back was that Calendar backend is offline.
c) At around this time - I have a meeting reminder due to come up. Possibly that tinkered with this and gave this error.


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

Memory status: size: 338436096 vsize: 0 resident: 338436096 share: 0 rss: 83066880 rss_rlim: 0
CPU usage: start_time: 1173668432 rtime: 0 utime: 14652 stime: 0 cutime:13990 cstime: 0 timeout: 662 it_real_value: 0 frequency: 0

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 -1233418576 (LWP 7565)]
[New Thread -1376527456 (LWP 7640)]
[New Thread -1368134752 (LWP 7638)]
[New Thread -1359742048 (LWP 7596)]
[New Thread -1351349344 (LWP 7591)]
[New Thread -1342956640 (LWP 7586)]
[New Thread -1334170720 (LWP 7584)]
[New Thread -1325778016 (LWP 7583)]
[New Thread -1317385312 (LWP 7580)]
[New Thread -1281496160 (LWP 7578)]
[New Thread -1263248480 (LWP 7575)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 117902

Thread 1 (Thread -1233418576 (LWP 7565))

#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 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#6 ORBit_object_peek_connection
from /usr/lib/libORBit-2.so.0
#7 ORBit_object_get_connection
from /usr/lib/libORBit-2.so.0
#8 ORBit_small_invoke_stub
from /usr/lib/libORBit-2.so.0
#9 ORBit_small_invoke_stub_n
from /usr/lib/libORBit-2.so.0
#10 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#11 GNOME_Evolution_Addressbook_BookView_start
at Evolution-DataServer-Addressbook-stubs.c line 46
#12 e_book_view_start
at e-book-view.c line 225
#13 start_view
at e-contact-store.c line 668
#14 query_contact_source
at e-contact-store.c line 779
#15 e_contact_store_set_query
at e-contact-store.c line 986
#16 update_completions_on_idle_cb
at e-name-selector-entry.c line 503
#17 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#21 bonobo_main
from /usr/lib/libbonobo-2.so.0
#22 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 V Sridhar 2007-03-12 08:59:20 UTC

Created attachment 84416 [details]
Calendar Crash Report

Hi,

Got the dual-crash again. The first crash generates a file-save dialog. Then Calendars will not work till you restart message comes. Then the bug buddy submission crash report comes.

Submitting the first crash file.

Comment 2 André Klapper 2007-04-02 01:07:43 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 378057 ***