Version-Release number of selected component: dleyna-server-0.4.0-7.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 3 cmdline: /usr/libexec/dleyna-server-service executable: /usr/libexec/dleyna-server-service global_pid: 25240 kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at dim 2015-05-31 12:49:49 EDT, end at lun 2015-06-01 15:23:52 EDT. -- Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 g_hash_table_lookup_node at ghash.c:375 #2 g_hash_table_lookup at ghash.c:1147 #3 prv_server_available_cb at upnp.c:176 #4 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 #5 _g_closure_invoke_va at gclosure.c:831 #8 create_and_report_device_proxy at gupnp-control-point.c:320 #9 process_device_list at gupnp-control-point.c:475 #10 description_loaded at gupnp-control-point.c:519 #11 got_description_url at gupnp-control-point.c:571 Potential duplicate: bug 1187724
Created attachment 1036539 [details] File: backtrace
Created attachment 1036540 [details] File: cgroup
Created attachment 1036541 [details] File: core_backtrace
Created attachment 1036542 [details] File: dso_list
Created attachment 1036543 [details] File: environ
Created attachment 1036544 [details] File: limits
Created attachment 1036545 [details] File: maps
Created attachment 1036546 [details] File: mountinfo
Created attachment 1036547 [details] File: namespaces
Created attachment 1036548 [details] File: open_fds
Created attachment 1036549 [details] File: proc_pid_status
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 ***