Description of problem: Start totem. Version-Release number of selected component: totem-3.11.90-2.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: totem crash_function: find_media executable: /usr/bin/totem kernel: 3.13.3-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 find_media at totem-grilo.c:1101 #1 content_changed at totem-grilo.c:1130 #2 content_changed_cb at totem-grilo.c:1184 #7 grl_source_notify_change_list at grl-source.c:4433 #8 container_changed_cb at grl-upnp.c:329 #9 emit_notification at gupnp-service-proxy.c:1742 #10 emit_notifications_for_doc at gupnp-service-proxy.c:1773 #11 emit_notifications at gupnp-service-proxy.c:1823 #15 g_main_context_iteration at gmain.c:3773 #16 grl_wait_for_async_operation_complete at grl-sync.c:36
Created attachment 866789 [details] File: backtrace
Created attachment 866790 [details] File: cgroup
Created attachment 866791 [details] File: core_backtrace
Created attachment 866792 [details] File: dso_list
Created attachment 866793 [details] File: environ
Created attachment 866794 [details] File: exploitable
Created attachment 866795 [details] File: limits
Created attachment 866796 [details] File: maps
Created attachment 866797 [details] File: open_fds
Created attachment 866798 [details] File: proc_pid_status
Created attachment 866799 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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.