notify-osd crashed with SIGSEGV in IA__g_slice_alloc()

[Broomer68]

Binary package hint: notify-osd

crash was reported after resume from suspend with keyboard suspend hotkey on msi-wind with current jaunty netbook updates

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/notify-osd/notify-osd
Package: notify-osd 0.9.7-0ubuntu1
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 IA__g_slice_alloc (mem_size=160)
 IA__g_slice_alloc0 (mem_size=160)
 IA__g_type_create_instance (type=137436368)
 g_object_constructor (type=137436368,
 IA__g_object_newv (object_type=137436368, n_parameters=0,
Title: notify-osd crashed with SIGSEGV in IA__g_slice_alloc()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:IA__g_slice_alloc (mem_size=160)
IA__g_slice_alloc0 (mem_size=160)
IA__g_type_create_instance (type=137436368)
g_object_constructor (type=137436368,
IA__g_object_newv (object_type=137436368, n_parameters=0,

[Sebastien Bacher (seb128)]

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.

[David Barth (dbarth)]

There are a lot of similar crashers, outside of notify-osd. There should be a pattern there to try to find the origin of the bug.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.