nm-applet crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash notification on login.
Running Ubuntu Vivid.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: network-
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
Date: Fri Mar 27 21:36:44 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-09 (76 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
IpRoute:
default via 117.232.166.190 dev wwan0 proto static metric 1024
117.232.166.188/30 dev wwan0 proto kernel scope link src 117.232.166.189
169.254.0.0/16 dev wwan0 scope link metric 1000
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
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-
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
g_main_
Title: nm-applet crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
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.