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: _g_log_abort executable: /usr/libexec/dleyna-server-service global_pid: 32161 kernel: 4.0.0-0.rc3.git0.1.fc22.x86_64 runlevel: unknown type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Mon 2015-03-02 17:20:29 GMT, end at Tue 2015-03-24 12:36:52 GMT. -- Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:315 #3 g_variant_valist_new_nnp at gvariant.c:4690 #4 g_variant_valist_new_leaf at gvariant.c:4846 #5 g_variant_valist_new at gvariant.c:5028 #7 g_variant_new_va at gvariant.c:5256 #8 g_variant_new at gvariant.c:5191 #9 dls_task_complete at task.c:673 #10 prv_async_task_complete at server.c:609 #11 dls_async_task_complete at async.c:76 #16 dleyna_main_loop_start at libdleyna/core/main-loop.c:155
Created attachment 1005826 [details] File: backtrace
Created attachment 1005827 [details] File: cgroup
Created attachment 1005828 [details] File: core_backtrace
Created attachment 1005829 [details] File: dso_list
Created attachment 1005830 [details] File: environ
Created attachment 1005831 [details] File: limits
Created attachment 1005832 [details] File: maps
Created attachment 1005833 [details] File: mountinfo
Created attachment 1005834 [details] File: namespaces
Created attachment 1005835 [details] File: open_fds
Created attachment 1005836 [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 1901731 ***