gnome-settings-daemon crashed with SIGSEGV in __erand48_r()

[John Lenton]

this blew up

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-settings-daemon 3.1.3-0ubuntu2
ProcVersionSignature: Ubuntu 3.0-3.4-generic-pae 3.0.0-rc5
Uname: Linux 3.0-3-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Mon Jul 4 17:35:48 2011
Disassembly: => 0xb3b59a70: Cannot access memory at address 0xb3b59a70
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb3b59a70: Cannot access memory at address 0xb3b59a70
 PC (0xb3b59a70) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? ()
 __erand48_r (xsubi=0x0, buffer=0xb7049324, result=0x1) at erand48_r.c:43
 lrand48_r (buffer=0x0, result=0xbfcbd824) at lrand48_r.c:31
 __gconv_open (toset=0x0, fromset=0x0, handle=0x0, flags=134522976) at gconv_open.c:197
 _start ()
Title: gnome-settings-daemon crashed with SIGSEGV in __erand48_r()
UpgradeStatus: Upgraded to oneiric on 2011-04-20 (76 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 __erand48_r (xsubi=0x0, buffer=0xb7049324, result=0x1) at erand48_r.c:43
 lrand48_r (buffer=0x0, result=0xbfcbd824) at lrand48_r.c:31
 __gconv_open (toset=0x0, fromset=0x0, handle=0x0, flags=134522976) at gconv_open.c:197
 _start ()

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 805654, so it 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.