Description of problem: This issue was reported after wake up from hybernation. The computer was previously connected in different network. 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_error_free executable: /usr/sbin/NetworkManager kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (5 frames) #6 g_error_free at gerror.c:476 #7 g_clear_error at gerror.c:643 #8 on_proxy_acquired at bluez-manager/nm-bluez-device.c:932 #9 g_simple_async_result_complete at gsimpleasyncresult.c:777 #10 complete_in_idle_cb at gsimpleasyncresult.c:789
Created attachment 845952 [details] File: backtrace
Created attachment 845953 [details] File: cgroup
Created attachment 845954 [details] File: core_backtrace
Created attachment 845955 [details] File: dso_list
Created attachment 845956 [details] File: environ
Created attachment 845957 [details] File: limits
Created attachment 845958 [details] File: maps
Created attachment 845959 [details] File: open_fds
Created attachment 845960 [details] File: proc_pid_status
Created attachment 845961 [details] File: var_log_messages
NetworkManager-0.9.9.0-23.git20131003.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-23.git20131003.fc20
Package NetworkManager-0.9.9.0-23.git20131003.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.9.0-23.git20131003.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0294/NetworkManager-0.9.9.0-23.git20131003.fc20 then log in and leave karma (feedback).
NetworkManager-0.9.9.0-23.git20131003.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.