Description of problem: I upgrade NetworkManager to version 0.9.9.0-13.git20131001.fc20.x86_64. After restart NetworkManager (systemctl restart NetworkManager.service), service while crash. I sea in logs "ERROR:bluez-manager/nm-bluez-device.c:249:pan_connection_check_create:" When i disable bluetooth (systemctl disable bluetooth.service) and restart NetworkManager, is running again Version-Release number of selected component: NetworkManager-0.9.9.0-13.git20131001.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: _g_log_abort executable: /usr/sbin/NetworkManager kernel: 3.11.2-301.fc20.x86_64 runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 _g_log_abort at /lib64/libglib-2.0.so.0 #3 g_assertion_message at /lib64/libglib-2.0.so.0 #4 g_assertion_message_expr at /lib64/libglib-2.0.so.0 #5 check_emit_usable #6 adapter_properties_changed #7 ffi_call_unix64 at /lib64/libffi.so.6 #8 ffi_call at /lib64/libffi.so.6 #9 g_cclosure_marshal_generic at /lib64/libgobject-2.0.so.0 #10 g_closure_invoke at /lib64/libgobject-2.0.so.0 #11 signal_emit_unlocked_R at /lib64/libgobject-2.0.so.0
Created attachment 806655 [details] File: backtrace
Created attachment 806656 [details] File: cgroup
Created attachment 806657 [details] File: core_backtrace
Created attachment 806658 [details] File: dso_list
Created attachment 806659 [details] File: environ
Created attachment 806660 [details] File: limits
Created attachment 806661 [details] File: maps
Created attachment 806662 [details] File: open_fds
Created attachment 806663 [details] File: proc_pid_status
Created attachment 806664 [details] File: var_log_messages
I managed to reproduce. The problem was as incorrect assertion. Thomas has fixed that upstream: f4557256ea9d0912dbd292c5431c41a2073e2cdc bluez: fix creation of NAP connection for bluez device
You can find a test build (scratch-build) at http://koji.fedoraproject.org/koji/taskinfo?taskID=6020781 . This test version contains the mentioned patch f4557256ea9d0912dbd292c5431c41a2073e2cdc. Btw. a temporary workaround would be to create the connection for the bluetooth device on disk, so that NetworkManager does not try to create one (and does not crash). Something like below (adjust 'bdaddr' accordingly): [connection] id=Bluetooth Network uuid=eea8516c-b73f-43c0-9dcf-f18f03979fd3 type=bluetooth autoconnect=false [bluetooth] bdaddr=00:11:22:33:44:55 type=panu [ipv6] method=auto [ipv4] method=auto may-fail=false
Created attachment 807091 [details] [PATCH] koji commit for NetworkManager-0.9.9.0-13test.git20131001.fc20.src.rpm (In reply to Thomas Haller from comment #13) This is the patch for the koji build of the before mentioned scratch build.
NetworkManager-0.9.9.0-14.git20131003.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-14.git20131003.fc20
Package NetworkManager-0.9.9.0-14.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-14.git20131003.fc20' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18316/NetworkManager-0.9.9.0-14.git20131003.fc20 then log in and leave karma (feedback).
NetworkManager-0.9.9.0-14.git20131003.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1015543 has been marked as a duplicate of this bug. ***