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 534082 - Attempt to "Open" a previously accepted invite dumped core
Attempt to "Open" a previously accepted invite dumped core
Status: RESOLVED DUPLICATE of bug 460204
Product: evolution
Classification: Applications
Component: Calendar
2.22.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-20 17:53 UTC by Paul Smith
Modified: 2008-10-01 15:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Paul Smith 2008-05-20 17:53:49 UTC 
Steps to reproduce:
Not sure if it can be reproduced but this is how I produced it

1. I have a meeting scheduled in my calendar which was an Exchange invite that I accepted last week sometime
2. The invite also has an attached document
3. I right-clicked on it and selected "Open"

Evolution crashed.


Stack trace:
Program terminated with signal 11, Segmentation fault.
[New process 18185]
[New process 18506]
[New process 18504]
[New process 18291]

+ Trace 198245

Thread 1 (process 18185)

  • #0 camel_header_set_param
    at ../../../evolution-data-server/camel/camel-mime-utils.c line 2170
  • #1 camel_content_type_set_param
    at ../../../evolution-data-server/camel/camel-mime-utils.c line 2230
  • #2 camel_mime_part_set_filename
    at ../../../evolution-data-server/camel/camel-mime-part.c line 451
  • #3 set_attachment_list
    at ../../../../../evolution/calendar/gui/dialogs/comp-editor.c line 2433
  • #4 fill_widgets
    at ../../../../../evolution/calendar/gui/dialogs/comp-editor.c line 2456
  • #5 real_edit_comp
    at ../../../../../evolution/calendar/gui/dialogs/comp-editor.c line 2525
  • #6 event_editor_edit_comp
    at ../../../../../evolution/calendar/gui/dialogs/event-editor.c line 690
  • #7 comp_editor_edit_comp
    at ../../../../../evolution/calendar/gui/dialogs/comp-editor.c line 2675
  • #8 open_event_with_flags
    at ../../../../evolution/calendar/gui/e-calendar-view.c line 1998
  • #9 e_calendar_view_edit_appointment
    at ../../../../evolution/calendar/gui/e-calendar-view.c line 2043
  • #10 on_edit_appointment
    at ../../../../evolution/calendar/gui/e-calendar-view.c line 1206
  • #11 ep_activate
    at ../../../evolution/e-util/e-popup.c line 305
  • #12 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
  • #16 ??
  • #2 camel_mime_part_set_filename
    at ../../../evolution-data-server/camel/camel-mime-part.c line 451 
446     
447             camel_medium_set_header (CAMEL_MEDIUM (mime_part),
448                                      "Content-Disposition", str);
449             g_free(str);
450     
451             camel_content_type_set_param (((CamelDataWrapper *) mime_part)->mime_type, "name", filename);
452             str = camel_content_type_format (((CamelDataWrapper *) mime_part)->mime_type);
453             camel_medium_set_header (CAMEL_MEDIUM (mime_part), "Content-Type", str);
454             g_free (str);
455     }
(gdb) p *((CamelDataWrapper *) mime_part)
$2 = {parent_object = {klass = 0x853c428, magic = 2007188717, hooks = 0x0, ref_count = 1, flags = 0, next = 0x0, prev = 0x0}, priv = 0x8e0a1c8, encoding = CAMEL_TRANSFER_ENCODING_DEFAULT, mime_type = 0x0, stream = 0x0, offline = 0}

I don't know why it would be NULL though.

I still have the core etc. if you'd like me to do more debugging.
Comment 1 Paul Smith 2008-05-20 18:50:02 UTC 
FYI, the coredump happens every time I try to "Open" this meeting.
Comment 2 Srinivasa Ragavan 2008-05-21 16:26:07 UTC 
Paul, can you strip the confidential/sensitive contents and attach that mail/appt? This is one of our hitlist bugs in mailer with the same trace.
Comment 3 Milan Crha 2008-10-01 15:49:11 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should work fine with 2.22.3.1 or even better with 2.24.0.

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