Version-Release number of selected component: dleyna-renderer-0.4.0-4.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/dleyna-renderer-service crash_function: g_hash_table_lookup_node executable: /usr/libexec/dleyna-renderer-service global_pid: 4464 kernel: 4.0.2-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at mer. 2014-10-01 16:40:41 CEST, end at mar. 2015-05-12 19:13:19 CEST. -- Truncated backtrace: Thread no. 1 (9 frames) #4 g_hash_table_lookup_node at ghash.c:373 #5 g_hash_table_insert_internal at ghash.c:1226 #6 prv_device_chain_end at upnp.c:85 #7 prv_free_cb at libdleyna/core/task-processor.c:103 #8 g_hash_table_remove_all_nodes at ghash.c:548 #10 g_hash_table_unref at ghash.c:1097 #11 dleyna_task_processor_free at libdleyna/core/task-processor.c:136 #12 prv_context_free at libdleyna/core/main-loop.c:108 #13 dleyna_main_loop_start at libdleyna/core/main-loop.c:167
Created attachment 1024697 [details] File: backtrace
Created attachment 1024698 [details] File: cgroup
Created attachment 1024699 [details] File: core_backtrace
Created attachment 1024700 [details] File: dso_list
Created attachment 1024701 [details] File: environ
Created attachment 1024702 [details] File: limits
Created attachment 1024703 [details] File: maps
Created attachment 1024704 [details] File: mountinfo
Created attachment 1024705 [details] File: namespaces
Created attachment 1024706 [details] File: open_fds
Created attachment 1024707 [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 1360209 ***