Bug 527165 – crash in Evolution Mail and Calendar: I had just clicked on th...

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 527165 - crash in Evolution Mail and Calendar: I had just clicked on th...


Summary:	crash in Evolution Mail and Calendar: I had just clicked on th...


Status:	RESOLVED DUPLICATE of bug 512605

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.22.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:	2008-04-09 15:49 UTC by Thomas E. Vaughan
Modified:	2008-04-10 08:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description Thomas E. Vaughan 2008-04-09 15:49:22 UTC

What were you doing when the application crashed?
I had just clicked on the line for a meeting request message in the top pane, which was displaying my MS Exchange Inbox.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 71139328 vsize: 71139328 resident: 16551936 share: 10227712 rss: 16551936 rss_rlim: 4294967295
CPU usage: start_time: 1207752049 rtime: 117 utime: 106 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage'

[Thread debugging using libthread_db enabled]
[New Thread 0xb66b5960 (LWP 3835)]
[New Thread 0xb641cb90 (LWP 3837)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 194738

Thread 1 (Thread 0xb66b5960 (LWP 3835))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 __assert_fail
from /lib/i686/cmov/libc.so.6
#10 ber_flush2
from /usr/lib/liblber-2.4.so.2
#11 ldap_int_flush_request
from /usr/lib/libldap_r-2.4.so.2
#12 ldap_send_server_request
from /usr/lib/libldap_r-2.4.so.2
#13 ldap_send_initial_request
from /usr/lib/libldap_r-2.4.so.2
#14 ldap_ntlm_bind
from /usr/lib/libldap_r-2.4.so.2
#15 connect_ldap
at e2k-global-catalog.c line 243
#16 gc_search
#17 e2k_global_catalog_lookup
at e2k-global-catalog.c line 796
#18 get_message
#19 connection_handler
at mail-stub.c line 271
#20 ??
from /usr/lib/libglib-2.0.so.0
#21 ??
#22 ??
#23 ??
#24 ??
from /usr/lib/libglib-2.0.so.0
#25 ??
#26 ??
#27 ??
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(evolution:4147): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:4147): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:4147): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:4147): libecal-WARNING **: e-cal.c:318: Unexpected response
** Message: Response 1
[modules.Network     ][DEBUG  ] Remote host 'tevaugha-lt' removed (Client.py:68)
[modules.Network     ][DEBUG  ] Remote host 'tevaugha-lt' removed (Client.py:68)
(evolution:4147): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:4147): libecal-WARNING **: e-cal.c:318: Unexpected response
--------------------------------------------------

Comment 1 André Klapper 2008-04-10 08:03:31 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 512605 ***