indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

Bug #1630551 reported by Paul W
54
This bug affects 12 people
Affects Status Importance Assigned to Milestone
indicator-network (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Crash on startup

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic i686
ApportVersion: 2.20.3-0ubuntu7
Architecture: i386
Date: Wed Oct 5 12:38:48 2016
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb779beba <do_lookup_x+42>: mov 0x4(%eax),%ebx
 PC (0xb779beba) ok
 source "0x4(%eax)" (0x00000074) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-network
Stacktrace:
 #0 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 <do_lookup_x+1689>, flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361
         n = <error reading variable n (Cannot access memory at address 0x74)>
         list = <optimised out>
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 <do_lookup_x+1689>, flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361
 ?? ()
Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
UpgradeStatus: Upgraded to yakkety on 2016-09-26 (8 days ago)
UserGroups:

Revision history for this message
Paul W (dp-wilkinson) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 <do_lookup_x+1689>, flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361
         n = <error reading variable n (Cannot access memory at address 0x74)>
         list = <optimized out>
 #1 0x00000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 <do_lookup_x+1689>, flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361
   [Error: dl-lookup.c was not found in source tree]
 #1 0x00000000 in ?? ()
StacktraceTop:
 do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 <do_lookup_x+1689>, flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Charles Kerr (charlesk)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-network (Ubuntu):
status: New → Confirmed
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1630551

tags: added: iso-testing
Revision history for this message
Paul White (paulw2u) wrote :

Marking as a duplicate of bug 1632275 which although reported later is now showing as "Fix Released".

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.