bluetooth-applet crashed with SIGSEGV - Mutter and Bluetooth applet both died at same time. On asus 1000h usb stick live demo (not installed yet)

[TxRx]

Binary package hint: gnome-bluetooth

Using 10.10 nbr on usb stick in usb2.0 port of asus 1000h with live demo on it.

Enabled bluetooth was browsing bbc website for news (rss link used) to test firefox, went full screen firefox, etc, no problem, reduced back to normal firefox window and I think that's just before it crashed, hope this helps, probably will hold off updating from 9.10 on this laptop till I test 10.10 a little longer.

Love the unity interface but what the hell is mutter?

Cheers

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-bluetooth 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Tue Oct 12 09:41:37 2010
ExecutablePath: /usr/bin/bluetooth-applet
LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: bluetooth-applet
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xcedf4b: movsbl (%edx),%eax
 PC (0x00cedf4b) ok
 source "(%edx)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: bluetooth-applet crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #634964, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.