emifreq-applet crashed with SIGSEGV in free()

[XANA]

Binary package hint: emifreq-applet

I was turning off the computer getting ready to restart it when EmiFreq closed.

XUBUNTU 7.10 Gutsy Gibbon

I was not expecting this to happen when shutting down.
When it was shutting down, (since I have run Startup Manager, and selected the "text during boot" option) the text said:

Unmounting local filesystems failed

but everything else went okay and the system restarted and I was able to get in to XUBUNTU fine.

ProblemType: Crash
Architecture: i386
Date: Sat Mar 1 12:15:39 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/emifreq-applet/emifreq-applet
NonfreeKernelModules: cdrom
Package: emifreq-applet 0.18-3ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/emifreq-applet/emifreq-applet --oaf-activate-iid=OAFIID:GNOME_EmiFreqApplet_Factory --oaf-ior-fd=37
ProcCwd: /
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: emifreq-applet
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 g_free () from /usr/lib/libglib-2.0.so.0
 g_ptr_array_free () from /usr/lib/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: emifreq-applet crashed with SIGSEGV in free()
Uname: Linux xana-usb-laptop 2.6.22-14-rt #1 SMP PREEMPT RT Tue Feb 12 09:57:10 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:free () from /lib/tls/i686/cmov/libc.so.6
IA__g_free (mem=0x2) at /build/buildd/glib2.0-2.14.1/glib/gmem.c:187
IA__g_ptr_array_free (array=0x835d0a0, free_segment=1)
free_internal () at ef-backend.c:244
ef_backend_reload () at ef-backend.c:353

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Did this happen more than once? Thanks in advance.

[Charlie Kravetz (cjkgeek)]

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!