Description of problem: Totem just stop playing video in dlna, and then logon screen appear - x11 crached Version-Release number of selected component: dleyna-server-0.4.0-7.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/dleyna-server-service crash_function: g_type_check_instance executable: /usr/libexec/dleyna-server-service global_pid: 13524 kernel: 4.1.5-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 g_type_check_instance at gtype.c:4136 #3 g_socket_client_emit_event at gsocketclient.c:934 #4 g_socket_client_connected_callback at gsocketclient.c:1512 #5 g_task_return_now at gtask.c:1088 #6 g_task_return at gtask.c:1146 #7 g_socket_connection_connect_callback at gsocketconnection.c:236 #8 socket_source_dispatch at gsocket.c:3276 #13 dleyna_main_loop_start at libdleyna/core/main-loop.c:155
Created attachment 1068241 [details] File: backtrace
Created attachment 1068242 [details] File: cgroup
Created attachment 1068243 [details] File: core_backtrace
Created attachment 1068244 [details] File: dso_list
Created attachment 1068245 [details] File: environ
Created attachment 1068246 [details] File: limits
Created attachment 1068247 [details] File: maps
Created attachment 1068248 [details] File: mountinfo
Created attachment 1068249 [details] File: namespaces
Created attachment 1068250 [details] File: open_fds
Created attachment 1068251 [details] File: proc_pid_status
Created attachment 1068252 [details] File: var_log_messages
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.