ubuntu-geoip-provider crashed with SIGSEGV in dbus_message_get_reply_serial()

[ubername]

Don't know exactly what caused the crash - I had just double clicked on the ubuntu 12.04 skype deb downladed from the skype website, Software centre opened and error crash report came up simultaneously

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: geoclue-ubuntu-geoip 1.0.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Fri Mar 29 12:20:35 2013
ExecutablePath: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
MarkForUpload: True
ProcCmdline: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fd6a0e667c3: movzbl (%rax),%eax
 PC (0x7fd6a0e667c3) ok
 source "(%rax)" (0x000000d8) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntu-geoip
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_message_get_reply_serial () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: ubuntu-geoip-provider crashed with SIGSEGV in dbus_message_get_reply_serial()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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