Description of problem: Starting Totem without specifying a file to load, for example by launching it from the command line with no arguments, causes a crash every time. I've tried deleting all the files in my home folder it opens before the crash, but that had no effect. Version-Release number of selected component: totem-3.16.4-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/totem --gapplication-service crash_function: browse_cb executable: /usr/bin/totem global_pid: 6978 kernel: 4.1.7-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #4 browse_cb at totem-grilo.c:694 #5 queue_process at grl-source.c:2089 #9 g_main_context_iteration at gmain.c:3869 #10 g_application_run at gapplication.c:2308 Potential duplicate: bug 1171390
Created attachment 1077663 [details] File: backtrace
Created attachment 1077664 [details] File: cgroup
Created attachment 1077665 [details] File: core_backtrace
Created attachment 1077666 [details] File: dso_list
Created attachment 1077667 [details] File: environ
Created attachment 1077668 [details] File: limits
Created attachment 1077669 [details] File: maps
Created attachment 1077670 [details] File: mountinfo
Created attachment 1077671 [details] File: namespaces
Created attachment 1077672 [details] File: open_fds
Created attachment 1077673 [details] File: proc_pid_status
Created attachment 1077674 [details] File: var_log_messages
Happens when launching from command line, or after a delay when launching Totem without a file generally (I think this may be related to it trying to thumbnail videos) May be related to https://bugzilla.redhat.com/show_bug.cgi?id=1208915 https://bugzilla.redhat.com/show_bug.cgi?id=1200559
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.