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
Same as bug #1362608.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: network-
ProcVersionSign
Uname: Linux 3.16.0-
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Aug 29 21:43:02 2014
EcryptfsInUse: Yes
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 2013-10-17 (315 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IpRoute:
default via 192.168.8.1 dev wlan0 proto static
192.168.8.0/24 dev wlan0 proto kernel scope link src 192.168.8.110 metric 9
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
ProcCmdline: nm-applet
SegvAnalysis:
Segfault happened at: 0x429e2c: mov 0x50(%r13),%esi
PC (0x00429e2c) ok
source "0x50(%r13)" (0x00000050) not located in a known VMA region (needed readable region)!
destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-
StacktraceTop:
?? ()
?? ()
?? ()
g_main_
?? () from /lib/x86_
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: nm-applet crashed with SIGSEGV in g_main_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip disk fuse libvirtd lpadmin plugdev sambashare sudo vboxusers
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.8 connected enabled enabled enabled enabled disabled
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 #1257025, 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.