SIGABRT

Bug #303157 reported by Brian J. Murrell
2
Affects Status Importance Assigned to Milestone
evolution-jescs (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: evolution-jescs

When I try to delete a meeting from a jescs calendar the evolution-jescs process aborts with the following stack:

Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb6095b90 (LWP 25534)]
0xb7f2e430 in __kernel_vsyscall ()
(gdb) where
#0 0xb7f2e430 in __kernel_vsyscall ()
#1 0xb6cf7880 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb6cf9248 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb6d3510d in __libc_message () from /lib/tls/i686/cmov/libc.so.6
#4 0xb6d3b3f4 in malloc_printerr () from /lib/tls/i686/cmov/libc.so.6
#5 0xb6d3d456 in free () from /lib/tls/i686/cmov/libc.so.6
#6 0xb6f04c06 in IA__g_free (mem=0x87fd718)
    at /build/buildd/glib2.0-2.18.2/glib/gmem.c:190
#7 0xb6ef9ee7 in IA__g_list_foreach (list=0x888a4c0,
    func=0x80540a8 <g_free@plt>, user_data=0x0)
    at /build/buildd/glib2.0-2.18.2/glib/glist.c:789
#8 0xb7ed45f0 in _e_cal_backend_send_objects (backend=0x86f6f18,
    cal=0x86f7cc0,
    calobj=0x8dffbc9 "BEGIN:VEVENT\nUID:20081015T114556Z-9294-1001-1-0@pc20081128T130000Z\nDTSTAMP:20081015T115633Z\nSUMMARY:HP status concall\nDTSTART;TZID=/softwarestudio.org/Tzfile/America/Toronto:20081128T080000\nDTEND;TZID"...)
    at e-cal-backend-sync.c:817
#9 0xb7eccb48 in e_cal_backend_send_objects (backend=0x86f6f18,
    cal=0x86f7cc0,
    calobj=0x8dffbc9 "BEGIN:VEVENT\nUID:20081015T114556Z-9294-1001-1-0@pc20081128T130000Z\nDTSTAMP:20081015T115633Z\nSUMMARY:HP status concall\nDTSTART;TZID=/softwarestudio.org/Tzfile/America/Toronto:20081128T080000\nDTEND;TZID"...)
    at e-cal-backend.c:1002
#10 0xb7ed86b1 in impl_Cal_sendObjects (servant=0x86f7cd4,
    calobj=0x8dffbc9 "BEGIN:VEVENT\nUID:20081015T114556Z-9294-1001-1-0@pc20081128T130000Z\nDTSTAMP:20081015T115633Z\nSUMMARY:HP status concall\nDTSTART;TZID=/softwarestudio.org/Tzfile/America/Toronto:20081128T080000\nDTEND;TZID"...,
    ev=0xb6095258) at e-data-cal.c:383
#11 0xb7ec7db1 in _ORBIT_skel_small_GNOME_Evolution_Calendar_Cal_sendObjects (
    _o_servant=0x86f7cd4, _o_retval=0x0, _o_args=0xb6095100,
    _o_ctx=0xb6095188, _o_ev=0xb6095258,
    _impl_sendObjects=0xb7ed8670 <impl_Cal_sendObjects>)
    at Evolution-DataServer-Calendar-common.c:132
#12 0xb7860527 in ORBit_POAObject_invoke (pobj=0x8846ef8, ret=0x0,
    args=0xb6095100, ctx=0xb6095188, data=0xb6095208, ev=0xb6095258)
    at poa.c:1148
#13 0xb7866b25 in ORBit_OAObject_invoke (adaptor_obj=0x8846ef8, ret=0x0,
    args=0xb6095100, ctx=0xb6095188, data=0xb6095208, ev=0xb6095258)
    at orbit-adaptor.c:340
#14 0xb7852e0e in ORBit_small_invoke_adaptor (adaptor_obj=0x8846ef8,
    recv_buffer=0x8895790, m_data=0x808a080, data=0xb6095208, ev=0xb6095258)
    at orbit-small.c:846
#15 0xb7864639 in ORBit_POAObject_handle_request (pobj=0x8846ef8,
    opname=0x86f55c4 "sendObjects", ret=0x0, args=0x0, ctx=0x0,
    recv_buffer=0x8895790, ev=0xb6095258) at poa.c:1357
#16 0xb7864d12 in ORBit_POAObject_invoke_incoming_request (pobj=0x8846ef8,
    recv_buffer=0x8895790, opt_ev=0x0) at poa.c:1427
#17 0xb784b555 in giop_thread_queue_process (tdata=0x87eae80) at giop.c:792
#18 0xb784b988 in giop_request_handler_thread (data=0x87eae80, user_data=0x0)
    at giop.c:502
#19 0xb6f286c6 in g_thread_pool_thread_proxy (data=0x869c9a8)
    at /build/buildd/glib2.0-2.18.2/glib/gthreadpool.c:265
#20 0xb6f2702f in g_thread_create_proxy (data=0x8886358)
    at /build/buildd/glib2.0-2.18.2/glib/gthread.c:635
#21 0xb7c4350f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#22 0xb6dad7ee in clone () from /lib/tls/i686/cmov/libc.so.6

I couldn't find anywhere to report this upstream however.

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :
Daniel T Chen (crimsun)
Changed in evolution-jescs:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.