nm-applet crashed with SIGSEGV in g_main_context_dispatch()

Bug #1425653 reported by Dan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
Undecided
Unassigned

Bug Description

...

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: network-manager-gnome 0.9.10.1-0ubuntu1
Uname: Linux 3.18.3-031803-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Wed Feb 25 21:02:16 2015
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-01-16 (40 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
IpRoute:
 default via 10.0.0.1 dev ppp0 proto static metric 1024
 10.0.0.1 dev ppp0 proto kernel scope link src 10.132.195.118
 169.254.0.0/16 dev ppp0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: nm-applet
SegvAnalysis:
 Segfault happened at: 0x4327a0: mov 0x18(%r14),%rdi
 PC (0x004327a0) ok
 source "0x18(%r14)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nm-applet crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to vivid on 2015-02-13 (11 days ago)
UserGroups:

nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
Dan (danutz-1200) 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 #1418260, 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.