Description of problem: Resumed from suspend to RAM. Version-Release number of selected component: dleyna-server-0.4.0-7.fc22 Additional info: reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: /usr/libexec/dleyna-server-service crash_function: g_hash_table_insert_internal executable: /usr/libexec/dleyna-server-service global_pid: 8018 kernel: 4.1.2-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (7 frames) #0 g_hash_table_insert_internal at /lib64/libglib-2.0.so.0 #1 prv_device_chain_end at /usr/lib64/dleyna-server/libdleyna-server-1.0.so.1 #2 prv_free_cb at /lib64/libdleyna-core-1.0.so.3 #3 g_hash_table_remove_all_nodes.part at /lib64/libglib-2.0.so.0 #4 g_hash_table_unref at /lib64/libglib-2.0.so.0 #5 dleyna_task_processor_free at /lib64/libdleyna-core-1.0.so.3 #6 dleyna_main_loop_start at /lib64/libdleyna-core-1.0.so.3
Created attachment 1055771 [details] File: backtrace
Created attachment 1055772 [details] File: cgroup
Created attachment 1055773 [details] File: core_backtrace
Created attachment 1055774 [details] File: dso_list
Created attachment 1055775 [details] File: environ
Created attachment 1055776 [details] File: limits
Created attachment 1055777 [details] File: maps
Created attachment 1055778 [details] File: mountinfo
Created attachment 1055779 [details] File: namespaces
Created attachment 1055780 [details] File: open_fds
Created attachment 1055781 [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 1205574 ***