Version-Release number of selected component: dleyna-renderer-0.4.0-4.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 3 cmdline: /usr/libexec/dleyna-renderer-service executable: /usr/libexec/dleyna-renderer-service global_pid: 32214 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 mer. 2014-09-24 22:11:24 CEST, end at jeu. 2015-04-16 21:22:55 CEST. -- Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 g_hash_table_lookup_node at ghash.c:375 #2 g_hash_table_insert_internal at ghash.c:1226 #3 prv_device_chain_end at upnp.c:85 #4 prv_free_cb at libdleyna/core/task-processor.c:103 #5 g_hash_table_remove_all_nodes at ghash.c:548 #7 g_hash_table_unref at ghash.c:1097 #8 dleyna_task_processor_free at libdleyna/core/task-processor.c:136 #9 prv_context_free at libdleyna/core/main-loop.c:108 #10 dleyna_main_loop_start at libdleyna/core/main-loop.c:167
Created attachment 1018766 [details] File: backtrace
Created attachment 1018767 [details] File: cgroup
Created attachment 1018768 [details] File: core_backtrace
Created attachment 1018769 [details] File: dso_list
Created attachment 1018770 [details] File: environ
Created attachment 1018771 [details] File: limits
Created attachment 1018772 [details] File: maps
Created attachment 1018773 [details] File: mountinfo
Created attachment 1018774 [details] File: namespaces
Created attachment 1018775 [details] File: open_fds
Created attachment 1018776 [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 ***
*** This bug has been marked as a duplicate of bug 1813662 ***