Version-Release number of selected component: totem-3.11.91-1.fc21 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: totem crash_function: magazine_chain_pop_head executable: /usr/bin/totem kernel: 3.14.0-0.rc7.git1.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:544 #1 magazine_chain_prepare_fields at gslice.c:617 #2 magazine_cache_push_magazine at gslice.c:691 #3 thread_memory_magazine2_unload at gslice.c:809 #4 g_slice_free1 at gslice.c:1094 #5 g_type_free_instance at gtype.c:1938 #6 gtk_widget_real_destroy at gtkwidget.c:11522 #11 gtk_widget_dispose at gtkwidget.c:11354 #13 gtk_box_forall at gtkbox.c:2541 #14 gtk_container_destroy at gtkcontainer.c:1410
Created attachment 877601 [details] File: backtrace
Created attachment 877602 [details] File: cgroup
Created attachment 877603 [details] File: core_backtrace
Created attachment 877604 [details] File: dso_list
Created attachment 877605 [details] File: environ
Created attachment 877606 [details] File: exploitable
Created attachment 877607 [details] File: limits
Created attachment 877608 [details] File: maps
Created attachment 877609 [details] File: open_fds
Created attachment 877610 [details] File: proc_pid_status
Created attachment 877611 [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
Another user experienced a similar problem: I started to play a film. reporter: libreport-2.5.0 backtrace_rating: 4 cmdline: /usr/bin/totem --gapplication-service crash_function: magazine_chain_pop_head executable: /usr/bin/totem global_pid: 4895 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 package: totem-3.16.0-1.fc22 reason: totem killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.