ubuntu-geoip-provider crashed with SIGABRT in __kernel_vsyscall()

[Bartosz Porosinski]

Crashed some time after login or after closing time&date settings from indicator-datetime.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: geoclue-ubuntu-geoip 0.0.2-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CheckboxSubmission: 408d605ae91dda29ff72ddd998139108
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
Date: Sun Apr 17 08:57:44 2011
ExecutablePath: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: ubuntu-geoip
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/libtalloc.so.2
 _talloc_free () from /usr/lib/libtalloc.so.2
Title: ubuntu-geoip-provider crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to natty on 2011-04-01 (15 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 talloc_abort (reason=0x9a6ed0 "Bad talloc magic value - access after free") at ../talloc.c:210
 talloc_abort_access_after_free (ptr=0xb6f06438, location=0x11f7cd6 "../lib/util/params.c:571") at ../talloc.c:229

[Brian Murray (brian-murray)]

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 529714, 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.