NetworkManager crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
crash during normal operation after several hours
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu4
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Tue Oct 13 16:39:49 2015
ExecutablePath: /usr/sbin/
IpRoute:
default via 10.85.3.65 dev enx801f02f8383b proto static metric 600
10.85.3.0/24 dev enx801f02f8383b proto kernel scope link src 10.85.3.99 metric 600
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
LANGUAGE=en_GB:en
TERM=linux
PATH=(custom, no user)
LANG=en_GB.UTF-8
SegvAnalysis:
Segfault happened at: 0x497b77: mov (%rax),%rsi
PC (0x00497b77) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
?? ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: NetworkManager crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
mtime.conffile.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
| Boris (boris-woerner) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1496741, 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.