gconftool-2 crashed with SIGABRT in __kernel_vsyscall()

[DaveSaunders]

using live disk natty i386. system reported a bug

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gconf2 2.32.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Tue May 3 21:45:47 2011
ExecutablePath: /usr/bin/gconftool-2
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gconftool-2 --unset /desktop/gnome/volume_manager/automount_media
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: gconf
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gconftool-2 crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[DaveSaunders (luvking)]

No idea what this error report stuf means but first time I tried to boot from live natty i386 disk just kinda froze so had to shut down and restart. next time got bug report whatever it means. similar problem with my old advent 8475 651mhz coppermine 320mb mem which installed natty off live disk when ubuntu studio 10.10 already on (but managed to render 10.10 useless). when I wiped disk could boot live disk but not install, even with swapfile to boost memory. current machine is dell xps 2ghz duo 3gb mem so plenty of juice there.

[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 #752214, 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.