Bug 1420244 - [abrt] [faf] NetworkManager: __strchr_sse42(): /usr/sbin/NetworkManager killed by 11
Summary: [abrt] [faf] NetworkManager: __strchr_sse42(): /usr/sbin/NetworkManager kille...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL: http://faf.lab.eng.brq.redhat.com/faf...
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-08 09:43 UTC by Beniamino Galvani
Modified: 2017-08-01 09:22 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.8.0-0.2.git20170215.1d40c5f4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-01 09:22:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2299 0 normal SHIPPED_LIVE Moderate: NetworkManager and libnl3 security, bug fix and enhancement update 2017-08-01 12:40:28 UTC

Description Beniamino Galvani 2017-02-08 09:43:37 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/9034de81597017544fdc0f909f43588777f67dfc/

#0  __strchr_sse42 at ../sysdeps/x86_64/multiarch/strchr.S:134
#1  update_connection at devices/nm-device-bond.c:169
#2  nm_device_generate_connection at devices/nm-device.c:3380
#3  recheck_assume_connection at nm-manager.c:1696
#4  recheck_assume_connection at nm-manager.c:1813
#5  _g_closure_invoke_va at gclosure
#6  g_signal_emit_valist at gsignal.c:3292
#7  g_signal_emit at gsignal.c:3439
#8  nm_device_emit_recheck_assume at devices/nm-device.c:3590
#9  g_main_context_dispatch at gmain.c:3152
#10 g_main_context_dispatch at gmain.c:3767
#11 g_main_context_iterate at gmain.c:3838
#12 g_main_loop_run at gmain.c:4032
#13 main at main.c:411

Comment 3 errata-xmlrpc 2017-08-01 09:22:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.