Version-Release number of selected component: NetworkManager-0.9.9.0-33.git20131003.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: g_slist_find executable: /usr/sbin/NetworkManager kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 g_slist_find at gslist.c:727 #1 g_object_notify_queue_add at gobject.c:305 #2 g_object_notify_by_spec_internal at gobject.c:1135 #3 g_object_notify at gobject.c:1183 #4 foreach_property_cb at nm-wifi-ap.c:460 #5 g_hash_table_foreach at ghash.c:1526 #6 nm_ap_new_from_properties at nm-wifi-ap.c:495 #7 supplicant_iface_new_bss_cb at devices/nm-device-wifi.c:1990 #8 ffi_call_unix64 at ../src/x86/unix64.S:76 #9 ffi_call at ../src/x86/ffi64.c:522
Created attachment 879632 [details] File: backtrace
Created attachment 879633 [details] File: cgroup
Created attachment 879634 [details] File: core_backtrace
Created attachment 879635 [details] File: dso_list
Created attachment 879636 [details] File: environ
Created attachment 879637 [details] File: exploitable
Created attachment 879638 [details] File: limits
Created attachment 879639 [details] File: maps
Created attachment 879640 [details] File: open_fds
Created attachment 879641 [details] File: proc_pid_status
Created attachment 879642 [details] File: var_log_messages
Hmm, strange, a problem in notifying an AP strength property. g_object_notify (G_OBJECT (ap), NM_AP_STRENGTH); Arcadiy, are you able to reproduce this bug at all?
Nope, I don't even really know how it happened, I just saw an abrt message.
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.