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 326894 - Crash when updating the calendar
Crash when updating the calendar
Status: RESOLVED DUPLICATE of bug 272632
Product: evolution
Classification: Applications
Component: Calendar
2.2.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-13 19:51 UTC by Trevin Beattie
Modified: 2006-01-15 04:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Trevin Beattie 2006-01-13 19:51:10 UTC
Distribution: My Linux release 3.5 (Rainbow)
Package: Evolution
Severity: major
Version: GNOME2.10.1 2.2.x
Gnome-Distributor: GNOME.Org
Synopsis: Crash when updating the calendar
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.2.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I was simply trying to accept a meeting invitation.  Accepting meetings
has usually (though not always) worked before.  This invite included an
attached document, if it makes any difference.

Steps to reproduce the crash:
1. Connect to an Exchange mailbox using IMAP.
2. Have someone invite you to a meeting (the sender is using MS Outlook)
and attach a file to the invitation.
3. Accept the invitation, saving it to your personal (local) calendar.

Expected Results:
The meeting should have been added to my calendar.

How often does this happen?
About 5% of the time I get an error stating that it could not access my
calendar.
About 2% of the time, evolution crashes.

Additional Information:
Running gnome 2.10, which was built from source last May.  Evolution
2.2.2 was built from source last June.



Debugging Information:

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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1218672960 (LWP 25629)]
[New Thread -1306326096 (LWP 27194)]
[New Thread -1285108816 (LWP 25649)]
[New Thread -1274541136 (LWP 25642)]
[New Thread -1264051280 (LWP 25641)]
[New Thread -1253561424 (LWP 25640)]
[New Thread -1232077904 (LWP 25639)]
[New Thread -1242567760 (LWP 25637)]
[New Thread -1219720272 (LWP 25635)]
0x007447a2 in _dl_sysinfo_int80 () at rtld.c:577
577	relocate_doit (void *a)

Thread 1 (Thread -1218672960 (LWP 25629))

  • #0 _dl_sysinfo_int80
    at rtld.c line 577
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 428
  • #4 <signal handler called>
  • #5 camel_mime_part_get_filename
    at camel-mime-part.c line 419
  • #6 em_utils_temp_save_part
    at em-utils.c line 1172
  • #7 update_item
    at itip-formatter.c line 744
  • #8 view_response_cb
    at itip-formatter.c line 1175
  • #9 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 button_clicked_cb
    at itip-view.c line 665
  • #15 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #20 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_button_get_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #28 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_button_set_relief
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_has_handler_pending
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #36 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 gdk_event_get_graphics_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #40 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #41 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #42 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #43 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #44 main
    at main.c line 610

    arg = 0x0, val = 0, descrip = 0x0, argDescrip = 0x0}}
	uri_list = (GSList *) 0x0
	popt_context_value = {g_type = 0, data = {{v_int = 0, v_uint = 0, 
      v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, 
      v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long =
0, 
      v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0,

      v_pointer = 0x0}}}
	program = (GnomeProgram *) 0x8d60ed0
	popt_context = 0x0
	args = (const char **) 0x0
	evolution_directory = 0x0
	icon_list = (GList *) 0x0




------- Bug created by bug-buddy at 2006-01-13 19:51 -------

Comment 1 Karsten Bräckelmann 2006-01-15 04:32:09 UTC
Looks like the same stacktrace as in bug 272632.


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