Version-Release number of selected component: dleyna-server-0.4.0-7.fc22 Additional info: reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: /usr/libexec/dleyna-server-service crash_function: gupnp_context_manager_manage_control_point executable: /usr/libexec/dleyna-server-service global_pid: 17769 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at ven 2015-04-03 13:12:00 EDT, end at ven 2015-04-03 15:16:29 EDT. -- Truncated backtrace: Thread no. 1 (8 frames) #0 gupnp_context_manager_manage_control_point at gupnp-context-manager.c:647 #1 prv_on_context_available at upnp.c:363 #5 g_signal_emit_by_name at gsignal.c:3401 #6 create_context_for_device at gupnp-network-manager.c:265 #7 ap_proxy_new_cb at gupnp-network-manager.c:288 #8 g_simple_async_result_complete at gsimpleasyncresult.c:763 #9 complete_in_idle_cb at gsimpleasyncresult.c:775 #14 dleyna_main_loop_start at libdleyna/core/main-loop.c:155 Potential duplicate: bug 1205940
Created attachment 1010708 [details] File: backtrace
Created attachment 1010709 [details] File: cgroup
Created attachment 1010710 [details] File: core_backtrace
Created attachment 1010711 [details] File: dso_list
Created attachment 1010712 [details] File: environ
Created attachment 1010713 [details] File: limits
Created attachment 1010714 [details] File: maps
Created attachment 1010715 [details] File: mountinfo
Created attachment 1010716 [details] File: namespaces
Created attachment 1010717 [details] File: open_fds
Created attachment 1010718 [details] File: proc_pid_status
I think this happened when I turned bluetooth on/off too fast with the button in the gnome-control-centre. This happened, because when you turn wifi off/on it *doesn't* remember your setting so you have to go and manually turn bluetooth back *off* each time. I wish I had never bought a laptop with bluetooth. Easier to buy a USB dongle and plug it in each time, instead of constantly fighting with the settings :( That is related to: https://bugzilla.redhat.com/show_bug.cgi?id=570073 and/or https://bugzilla.redhat.com/show_bug.cgi?id=1082099 HTH! Cheers, James
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.
*** This bug has been marked as a duplicate of bug 1289735 ***