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

Bug #257472 reported by aleneguou
48
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

This happened today when I started a gnome session.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/evolution/2.24/evolution-alarm-notify
Package: evolution 2.23.6-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/evolution/2.24/evolution-alarm-notify
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_slice_alloc () from /usr/lib/libglib-2.0.so.0
 g_list_append () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
Title: evolution-alarm-notify crashed with SIGSEGV in g_slice_alloc()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev powerdev sambashare saned scanner tape video

Tags: apport-crash
Revision history for this message
aleneguou (alexandergould) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_list_append (list=0x0, data=0x9532808) at /build/buildd/glib2.0-2.17.6/glib/glist.c:122
_gdk_event_queue_append (display=0x952f0c0, event=0x9532808)
_gdk_events_queue (display=0x952f0c0) at /build/buildd/gtk+2.0-2.13.6/gdk/x11/gdkevents-x11.c:2297
gdk_event_dispatch (source=0x95362f0, callback=0, user_data=0x0)
IA__g_main_context_dispatch (context=0x9536338) at /build/buildd/glib2.0-2.17.6/glib/gmain.c:2072

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in evolution:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Felix Yan (felixonmars) wrote :

I have the same problem, lol

Revision history for this message
disturbedsaint (disturbedsaint) wrote :

Same problem.
Just surfing using Firefox, not doing anything else.

Since I don't know what caused it/how to reproduce it it seems kind of difficult to make a decent Valgrind log.
Would it be usefull to just start the Valgrind log and wait/hope it crashes?

Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in evolution:
status: Incomplete → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

could can run the binary until getting the issue again if you have no specific way to trigger the crash

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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