evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()

Bug #267576 reported by Antono Vasiljev
6
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: evolution

Evo crashed while checking for new mail

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/evolution/2.24/evolution-alarm-notify
Package: evolution 2.23.91-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/evolution/2.24/evolution-alarm-notify
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/libedataserver-1.2.so.11
 ?? () from /usr/lib/libORBit-2.so.0
 ?? () from /usr/lib/libORBit-2.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
Title: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.27-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare stapdev stapusr video

Tags: apport-crash
Revision history for this message
Antono Vasiljev (antono) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:connection_listen_cb (object=0x8c1ead0, user_data=0xb5f03850) at e-component-listener.c:48
link_connection_emit_broken (cnx=0x8c1ead0, callbacks=0x1) at linc-connection.c:146
link_connection_broken_idle (dummy=0x0) at linc-connection.c:183
g_idle_dispatch (source=0x8c8c340, callback=0, user_data=0x0) at /build/buildd/glib2.0-2.18.0/glib/gmain.c:4232
IA__g_main_context_dispatch (context=0x8c236a8) at /build/buildd/glib2.0-2.18.0/glib/gmain.c:2142

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in evolution:
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.