nm-applet crashed with SIGSEGV

Bug #1204289 reported by Tim Lunn
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

This crashed testing ubuntu GNOME alpha2 candidate image.

nm-applet crash shorty after logging into live session.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-manager-gnome 0.9.8.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CasperVersion: 1.335
Date: Tue Jul 23 23:10:57 2013
Disassembly: => 0x7fc5990839dc: Cannot access memory at address 0x7fc5990839dc
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 172.16.34.2 dev eth0 proto static
 172.16.34.0/24 dev eth0 proto kernel scope link src 172.16.34.142 metric 1
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130723.1)
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
RfKill:

SegvAnalysis:
 Segfault happened at: 0x7fc5990839dc: Cannot access memory at address 0x7fc5990839dc
 PC (0x7fc5990839dc) ok
 SP (0x7fff61ccbef0) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: network-manager-applet
Stacktrace:
 #0 0x00007fc5990839dc in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff61ccbef0
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 3 (LWP 2630):
 #0 0x00007fc5970e73cd in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fc58d418b80
Title: nm-applet crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Wired connection 1 8342aa14-463e-4b7c-a885-1c32b36e526c 802-3-ethernet 1374620989 Tue 23 Jul 2013 11:09:49 PM UTC yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

Revision history for this message
Tim Lunn (darkxst) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fc5990839dc in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff61ccbef0
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 3 (LWP 2630):
 #0 0x00007fc5970e73cd in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fc58d418b80

Changed in network-manager-applet (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libexpat1: package version 2.1.0-4 dbgsym version 2.1.0-2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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/1204289

tags: added: iso-testing
Revision history for this message
Tim Lunn (darkxst) wrote :

This also seems to be crashing in libindicator, probably due to a missing indicator

Program terminated with signal 11, Segmentation fault.
#0 0xb6e9bb8e in g_type_check_instance_is_a ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
(gdb) bt
#0 0xb6e9bb8e in g_type_check_instance_is_a ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#1 0xb743fc55 in gtk_status_icon_set_visible ()
   from /usr/lib/i386-linux-gnu/libgtk-3.so.0
#2 0x08057ba4 in ?? ()
#3 0xb778afe7 in app_indicator_dispose (object=0x9488888)
    at ../../../src/app-indicator.c:646
#4 0xb6e7c3f8 in g_object_unref ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#5 0x0805c5a7 in ?? ()
#6 0xb6e7c488 in g_object_unref ()
   from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
#7 0x08054d6a in main ()

information type: Private → Public
Tim Lunn (darkxst)
Changed in network-manager-applet (Ubuntu):
status: Invalid → 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.