NetworkManager crashed with SIGSEGV in nm_device_get_unmanaged_flag()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
NA
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu4
Uname: Linux 4.3.0-040300rc4
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Tue Oct 13 20:44:52 2015
ExecutablePath: /usr/sbin/
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-10-11 (1 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
IpRoute:
default via 192.168.1.1 dev wlxc412f52dbaf9 proto static metric 600
169.254.0.0/16 dev wlxc412f52dbaf9 scope link metric 1000
192.168.1.0/24 dev wlxc412f52dbaf9 proto kernel scope link src 192.168.1.6 metric 600
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: /usr/sbin/
SegvAnalysis:
Segfault happened at: 0x4515eb <nm_device_
PC (0x004515eb) ok
source "%ebx" ok
destination "0xd4(%rax)" (0x000000d4) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
nm_device_
?? ()
?? ()
g_main_
?? () from /lib/x86_
Title: NetworkManager crashed with SIGSEGV in nm_device_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-
Wired connection 1 b4bf2457-
PK 94d9ca69-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
wlxc412f52dbaf9 wifi connected /org/freedeskto
enp4s0f1 ethernet unavailable /org/freedeskto
lo loopback unmanaged /org/freedeskto
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 #1500399, 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.