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 326355 - Crash while trying to accept an appointment
Crash while trying to accept an appointment
Status: RESOLVED DUPLICATE of bug 272632
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-01-09 22:36 UTC by agaudio
Modified: 2006-01-10 14:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description agaudio 2006-01-09 22:36:11 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: Evolution
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Crash while trying to accept an appointment
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I'm trying to accept an appointment update which was created by an MS
Outlook user, transferred to my box using fetchmail, then served up by a
local IMAP server.

I first tried to accept the update without having accepted the original
appointment. Evolution crashed. 
Then I tried to accept the original appointment, and that worked. When I
tried to accept the update, evolution crashed, leading me to believe
that there's something in particular about this update that is causing
it to crash.

The difference between the original and the update is that the update
contains an attachment. I'll post some of the email headers under
"additional information" below.

Steps to reproduce the crash:
1. Try to accept an appointment with an attachment (I don't know if all
such appointments will crash the application, but I suspect it is the
attachment for this appointment in particular which is causing it).
2. 
3. 

Expected Results:
The appointment is accepted/updated.

How often does this happen?
Has happened twice with this particular appointment (two attempt to
accept it). I've had this happen to me twice in the past with a similar
appointment, and I believe that also had an attachment.

Additional Information:

Here are some of the mail headers. They are not complete due to
confidentiality concerns:

Received: from localhost (rockhopper [127.0.0.1])
        by localhost.localdomain (8.13.4/8.12.5) with ESMTP id
k09JaLwW008095
        for <agaudio@localhost>; Mon, 9 Jan 2006 14:36:21 -0500
Received: from MS_EXCHANGE_HOSTNAME_REMOVED [IP_REMOVED]
        by localhost with IMAP (fetchmail-6.2.5.5)
        for agaudio@localhost (single-drop); Mon, 09 Jan 2006 14:36:21
-0500 (EST)
Received: from HOSTNAME_REMOVED ([IP REMOVED]) by
MS_EXCHANGE_HOSTNAME_REMOVED with Microsoft SMTPSVC(IP_REMOVED); Mon, 9
Jan 2006 14:35:45 -0500

MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="----_=_NextPart_001_01C61553.E24FFE80"
Content-class: urn:content-classes:calendarmessage
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
X-OriginalArrivalTime: 09 Jan 2006 19:35:45.0915 (UTC)
FILETIME=[E2DB9CB0:01C61553]

Date: Mon, 9 Jan 2006 14:35:42 -0500
Message-ID: <C79EF91C923DF24189CEDA1950F7278901C5B99A@HOSTNAME_REMOVED>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:

Content-Length: 44664
Lines: 658

This is a multi-part message in MIME format.

------_=_NextPart_001_01C61553.E24FFE80
Content-Type: multipart/alternative;
        boundary="----_=_NextPart_002_01C61553.E24FFE80"


------_=_NextPart_002_01C61553.E24FFE80
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

... (html content of appointment notice) ...

------_=_NextPart_002_01C61553.E24FFE80
Content-class: urn:content-classes:calendarmessage
Content-Type: text/calendar;
        method=REQUEST;
        name="meeting.ics"
Content-Transfer-Encoding: 8bit

... (vcalendar content of appointment) ...

------_=_NextPart_002_01C61553.E24FFE80--

------_=_NextPart_001_01C61553.E24FFE80
Content-Type: application/msword;
        name="LoggingAndPersistencySOW.doc"
Content-Transfer-Encoding: base64
Content-ID: <049e01c61553$fa2f26c4$_CDOEX>
Content-Description: LoggingAndPersistencySOW.doc
Content-Disposition: attachment;
        filename="LoggingAndPersistencySOW.doc"

... (word doc attachment) ...

------_=_NextPart_001_01C61553.E24FFE80--

(EOF)


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208498496 (LWP 9458)]
[New Thread -1391543376 (LWP 9590)]
[New Thread -1297106000 (LWP 9503)]
[New Thread -1286616144 (LWP 9502)]
[New Thread -1276126288 (LWP 9500)]
[New Thread -1265636432 (LWP 9498)]
[New Thread -1243194448 (LWP 9496)]
[New Thread -1255146576 (LWP 9495)]
[New Thread -1232704592 (LWP 9493)]
[New Thread -1222198352 (LWP 9491)]
[New Thread -1221735504 (LWP 9461)]
[New Thread -1211245648 (LWP 9460)]
(no debugging symbols found)
0x00807402 in __kernel_vsyscall ()

Thread 1 (Thread -1208498496 (LWP 9458))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 camel_mime_part_get_filename
    from /usr/lib/libcamel-1.2.so.0
  • #6 em_utils_temp_save_part
    from /usr/lib/evolution/2.2/components/libevolution-mail.so
  • #7 ??
    from /usr/lib/evolution/2.2/plugins/liborg-gnome-itip-formatter.so
  • #8 ??
    from /usr/lib/evolution/2.2/plugins/liborg-gnome-itip-formatter.so
  • #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_stop_emission
    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 itip_view_get_type
    from /usr/lib/evolution/2.2/plugins/liborg-gnome-itip-formatter.so
  • #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_stop_emission
    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_stop_emission
    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_stop_emission
    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_screen_get_setting
    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_check
    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



-- 
Aaron Gaudio           agaudio @ eng.mc.xerox.com           585-422-6876

                           Tu Modo Ursom Edis,
                           Te Modo Ursus Edit.




------- Bug created by bug-buddy at 2006-01-09 22:36 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.

Comment 1 madcap 2006-01-09 23:25:33 UTC
This just happened again with another appointment with an attachment on it, so I'm pretty sure it's the attachments that are mucking things up.
Comment 2 Chenthill P 2006-01-10 05:45:22 UTC
This has been fixed. Please use the latest stable version evolution-2.4.x.

*** This bug has been marked as a duplicate of 272632 ***
Comment 3 madcap 2006-01-10 14:46:50 UTC
I'm using Fedora Core 4, which currently has evolution 2.2 and I don't have the willpower to rebuild evo 2.4 and all its dependancies right now.

Is evo 2.2 end-of-lifed, or is there some chance of getting the fix backported to 2.2 (since I assume FC4 is not going to upgrade to evo 2.4)?