Version-Release number of selected component: NetworkManager-0.9.8.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_settings_connection_update_timestamp executable: /usr/sbin/NetworkManager kernel: 3.8.2-206.fc18.x86_64 uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 nm_settings_connection_update_timestamp at nm-settings-connection.c:1459 #1 nm_device_state_changed at nm-device.c:5156 #7 g_object_notify_by_spec_internal at gobject.c:1135 #8 g_object_notify at gobject.c:1177 #9 nm_active_connection_set_state at nm-active-connection.c:110 #10 nm_vpn_connection_set_vpn_state at nm-vpn-connection.c:212 #14 g_signal_emit_by_name at gsignal.c:3393 #15 nm_device_state_changed at nm-device.c:5114 #16 internal_activate_device at nm-manager.c:2438 #17 nm_manager_activate_connection at nm-manager.c:2955
Created attachment 711057 [details] File: backtrace
Created attachment 711058 [details] File: cgroup
Created attachment 711059 [details] File: core_backtrace
Created attachment 711060 [details] File: dso_list
Created attachment 711061 [details] File: environ
Created attachment 711062 [details] File: limits
Created attachment 711063 [details] File: maps
Created attachment 711064 [details] File: open_fds
Created attachment 711065 [details] File: proc_pid_status
Created attachment 711066 [details] File: var_log_messages
Karnelij, do you experience the crash with a newer NetworkManager? The problem is that req is NULL in nm_device_state_changed(), causing problems in next code. But the real issue my be Mar 16 16:48:06 localhost NetworkManager[769]: (nm-device.c:5038):nm_device_state_changed: runtime check failed: (in_state_changed == FALSE)
Не, у новым NetworkManager такое не паўтаралася.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.