Version-Release number of selected component: NetworkManager-0.9.9.0-22.git20131003.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: _g_log_abort executable: /usr/sbin/NetworkManager kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at gmessages.c:255 #5 build_rtnl_addr at platform/nm-linux-platform.c:2244 #6 ip6_address_add at platform/nm-linux-platform.c:2282 #7 nm_platform_ip6_address_add at platform/nm-platform.c:1108 #8 nm_platform_ip6_address_sync at platform/nm-platform.c:1326 #9 nm_ip6_config_commit at nm-ip6-config.c:156 #10 nm_vpn_connection_apply_config at vpn-manager/nm-vpn-connection.c:666 #11 nm_vpn_connection_config_maybe_complete at vpn-manager/nm-vpn-connection.c:712 #12 nm_vpn_connection_ip6_config_get at vpn-manager/nm-vpn-connection.c:1108 #13 marshal_dbus_message_to_g_marshaller at dbus-gproxy.c:1736
Created attachment 843097 [details] File: backtrace
Created attachment 843098 [details] File: cgroup
Created attachment 843099 [details] File: core_backtrace
Created attachment 843100 [details] File: dso_list
Created attachment 843101 [details] File: environ
Created attachment 843102 [details] File: limits
Created attachment 843103 [details] File: maps
Created attachment 843104 [details] File: open_fds
Created attachment 843105 [details] File: proc_pid_status
Created attachment 843106 [details] File: var_log_messages
Another user experienced a similar problem: Enabled openconnect VPN (ipv6-enabled) on IPv6-enabled WLAN. According to messages log, the vpn0 interface setup went fine, but some unexpected situation occurred and it crashed in an assertion failure (maybe when setting interface MTU?): Dec 30 11:32:50 dhcp-79 NetworkManager: SIOCSIFMTU: Operation not permitted Dec 30 11:32:50 dhcp-79 NetworkManager: ** Dec 30 11:32:50 dhcp-79 NetworkManager: ERROR:platform/nm-linux-platform.c:2244:build_rtnl_addr: assertion failed: (!nle) I had not tried openconnect before, so I don't know if this has worked in the past. Disabling IPv6 identity in VPN settings did not seem to help. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: _g_log_abort executable: /usr/sbin/NetworkManager kernel: 3.12.5-302.fc20.i686+PAE package: NetworkManager-0.9.9.0-22.git20131003.fc20 reason: NetworkManager killed by SIGABRT (SIOCSIFMTU failure, platform/nm-linux-platform.c:2244:build_rtnl_addr assertion failure) runlevel: N 5 type: CCpp uid: 0
I can confirm that it was working in the past, at least with: NetworkManager-0.9.9.0-19.git20131003.fc20.x86_64. Now it crash in the same manner. More info: https://bugzilla.redhat.com/show_bug.cgi?id=1047462
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.