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

Bug #1162837 reported by S. Patrikios
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-geoip (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just found the error message on the desktop, after opening the Software Center

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: geoclue-ubuntu-geoip 1.0.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Mon Apr 1 18:05:41 2013
ExecutablePath: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
InstallationDate: Installed on 2013-04-01 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130321)
MarkForUpload: True
ProcCmdline: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
SegvAnalysis:
 Segfault happened at: 0x7fcd3c5727c3: movzbl (%rax),%eax
 PC (0x7fcd3c5727c3) ok
 source "(%rax)" (0x000000ab) 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 lpadmin plugdev sambashare sudo

Revision history for this message
S. Patrikios (sipatrik-m) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.