ubuntu-geoip-provider crashed with SIGSEGV

Bug #1155870 reported by Rainer Rohde
702
This bug affects 165 people
Affects Status Importance Assigned to Milestone
Ubuntu GeoIP
Confirmed
Undecided
Unassigned
ubuntu-geoip (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Just happened; not sure what triggered it.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: geoclue-ubuntu-geoip 1.0.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
Uname: Linux 3.8.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Fri Mar 15 23:03:26 2013
EcryptfsInUse: Yes
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)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fdd4418dd3c: mov (%rax),%rdx
 PC (0x7fdd4418dd3c) ok
 source "(%rax)" (0x00abcdef) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown 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
 ?? () 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
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 link_before (link=0xbc2418, before_this_link=0xabcdef, list=0x7fdd2c001fd0) at ../../dbus/dbus-list.c:120
 _dbus_list_prepend_link (list=list@entry=0x7fdd2c001fd0, link=link@entry=0xbc2418) at ../../dbus/dbus-list.c:325
 _dbus_list_append_link (list=list@entry=0x7fdd2c001fd0, link=link@entry=0xbc2418) at ../../dbus/dbus-list.c:307
 _dbus_message_add_counter_link (message=message@entry=0x7fdd2c001f60, link=link@entry=0xbc2418) at ../../dbus/dbus-message.c:304
 _dbus_message_add_counter (message=0x7fdd2c001f60, counter=0xb7dc50) at ../../dbus/dbus-message.c:338

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ubuntu-geoip (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-geoip (Ubuntu):
status: New → Confirmed
Revision history for this message
dwnoutnodessa (dwnoutnodessa) wrote :

just happens don't know why

Revision history for this message
Humberto F. da Luz Jr. (humbfdljr-l) wrote :

Same here, just happened when I opened Ubuntu Software Center.

Revision history for this message
Jason Robinson (jaywink) wrote :

Had this happen just after login after a reboot. No idea if it could be caused by something messed up after ppa-purging Unity Smart Scopes PPA. Everything seems to work fine. Including ubuntu-bug output for 'ubuntu-bug --save=geoclue-ubuntu.ubuntu-bug geoclue-ubuntu-geoip'

Changed in ubuntu-geoip:
status: New → Confirmed
Revision history for this message
James Conley (jpconleyiv) wrote :

This to just happened to me after an update, reboot and then login. Everything does seem to be ok but unsure why it's happening.

Revision history for this message
Willem Holleder (raice-f4h) wrote :

same problem here! But I can still login normally and even do some work. It just happens randomly.

Revision history for this message
Hugo Venhorst (yougo) wrote :

i've been having this bug at every single boot since I don't know when. I couldn't make a decent bug report, because Apport for some reason won't follow through with the reporting part.

today I found out about apport-bug and apport-collect, so let's see if i can conjure up some results.

Revision history for this message
Hugo Venhorst (yougo) wrote :

well, that just sucks. apport-bug collects the info, gets me to this page for me to subscribe, and then attaches nothing.

apport-collect tells me this bug is not mine and i should file a new bug with apport-bug and then mark it duplicate to this one :-|

should i make that duplicate bug, or is there any other sensible way of adding info to this bug?

Revision history for this message
Jason Bell (13l0y-jason) wrote :

Same problem. Any news on a fix yet?

Revision history for this message
Mevin Babu C. (mevinbabuc) wrote :

This bug is still there in Ubuntu 14.04 . Happens to me every time i boot. Very annoying

Revision history for this message
Stan Williams (stanwmusic) wrote :

Same problem as described.

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.