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

Bug #1161350 reported by Eilthalearin Kheru
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-geoip (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Software updater crashed (actually stopped responding) and this message popped up.
Unpacking linux image generic 3.8.0-15 ... (short) from 3.8.0-15.25_amd64.deb

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
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Thu Mar 28 11:48:25 2013
ExecutablePath: /usr/lib/ubuntu-geoip/ubuntu-geoip-provider
InstallationDate: Installed on 2013-03-21 (6 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130321)
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: 0x7f2c6bebfed7: mov %rdx,(%rax)
 PC (0x7f2c6bebfed7) ok
 source "%rdx" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing 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
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
Title: ubuntu-geoip-provider crashed with SIGSEGV in dbus_connection_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Eilthalearin Kheru (ekheru) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_list_unlink (list=list@entry=0x7fff1c3430d8, link=link@entry=0x15c8c98) at ../../dbus/dbus-list.c:499
 _dbus_list_remove_link (list=list@entry=0x7fff1c3430d8, link=link@entry=0x15c8c98) at ../../dbus/dbus-list.c:519
 _dbus_object_tree_dispatch_and_unlock (tree=0x1585a70, message=message@entry=0x15ec3a0, found_object=found_object@entry=0x7fff1c3431b4) at ../../dbus/dbus-object-tree.c:902
 dbus_connection_dispatch (connection=connection@entry=0x1586d90) at ../../dbus/dbus-connection.c:4672
 message_queue_dispatch (source=source@entry=0x1589d30, callback=<optimized out>, user_data=<optimized out>) at dbus-gmain.c:90

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
summary: - ubuntu-geoip-provider crashed with SIGSEGV in dbus_connection_dispatch()
+ ubuntu-geoip-provider crashed with SIGSEGV in _dbus_list_unlink()
tags: removed: need-amd64-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
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
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.