NetworkManager crashed with SIGSEGV in nm_device_uses_assumed_connection()

Bug #1554265 reported by Volkmar Eckardt
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

I dont know

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: network-manager 1.0.4-0ubuntu10
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 7 19:41:52 2016
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-03-06 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
IpRoute:
 default via 192.168.178.1 dev wlx74ea3a8e3b2d proto static metric 600
 169.254.0.0/16 dev wlx74ea3a8e3b2d scope link metric 1000
 192.168.178.0/24 dev wlx74ea3a8e3b2d proto kernel scope link src 192.168.178.23 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: /usr/sbin/NetworkManager --no-daemon
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SegvAnalysis:
 Segfault happened at: 0x44cc19 <nm_device_uses_assumed_connection+25>: cmpq $0x0,0x108(%rbx)
 PC (0x0044cc19) ok
 source "$0x0" ok
 destination "0x108(%rbx)" (0x00000108) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_device_uses_assumed_connection ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in nm_device_uses_assumed_connection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlx74ea3a8e3b2d wifi connected /org/freedesktop/NetworkManager/Devices/1 folkiwlan 1 c1765c93-3c24-4ca0-a3d0-37f9f200a547 /org/freedesktop/NetworkManager/ActiveConnection/0
 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
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
Volkmar Eckardt (eckifolki) 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 #1545804, 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.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.