nmcli crashed with SIGSEGV in g_ptr_array_foreach()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashed at system-testing
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-manager 0.9.8.0-0ubuntu16
ProcVersionSign
Uname: Linux 3.10.0-6-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Wed Jul 31 14:18:30 2013
ExecutablePath: /usr/bin/nmcli
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-07-31 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130731)
IpRoute:
default via 192.168.1.254 dev wlan0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.1 metric 9
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nmcli dev list
SegvAnalysis:
Segfault happened at: 0x41321e: mov 0x8(%rbp),%edi
PC (0x0041321e) ok
source "0x8(%rbp)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
?? ()
g_ptr_
do_devices ()
?? ()
g_main_
Title: nmcli crashed with SIGSEGV in g_ptr_array_
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 8f819ae0-
misko9-3 f3d4d9f4-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet unavailable /org/freedeskto
wlan0 802-11-wireless connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.0 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 #1155139, 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.