Bug 1266754

Summary: [abrt] totem: browse_cb(): totem killed by SIGABRT
Product: [Fedora] Fedora Reporter: James Legg <lankyleggy>
Component: totemAssignee: Bastien Nocera <bnocera>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bnocera, cfergeau, thub, wilf, xhueco408
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ae32e7d5bafc36027385c35bc724af5a0041a0b0
Whiteboard: abrt_hash:de0be700ad6496b78c741593c705196c897ac096;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:02:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description James Legg 2015-09-27 12:30:39 UTC 
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
Comment 1 James Legg 2015-09-27 12:30:43 UTC 
Created attachment 1077663 [details]
File: backtrace
Comment 2 James Legg 2015-09-27 12:30:45 UTC 
Created attachment 1077664 [details]
File: cgroup
Comment 3 James Legg 2015-09-27 12:30:46 UTC 
Created attachment 1077665 [details]
File: core_backtrace
Comment 4 James Legg 2015-09-27 12:30:48 UTC 
Created attachment 1077666 [details]
File: dso_list
Comment 5 James Legg 2015-09-27 12:30:49 UTC 
Created attachment 1077667 [details]
File: environ
Comment 6 James Legg 2015-09-27 12:30:51 UTC 
Created attachment 1077668 [details]
File: limits
Comment 7 James Legg 2015-09-27 12:30:54 UTC 
Created attachment 1077669 [details]
File: maps
Comment 8 James Legg 2015-09-27 12:30:56 UTC 
Created attachment 1077670 [details]
File: mountinfo
Comment 9 James Legg 2015-09-27 12:30:57 UTC 
Created attachment 1077671 [details]
File: namespaces
Comment 10 James Legg 2015-09-27 12:30:58 UTC 
Created attachment 1077672 [details]
File: open_fds
Comment 11 James Legg 2015-09-27 12:31:00 UTC 
Created attachment 1077673 [details]
File: proc_pid_status
Comment 12 James Legg 2015-09-27 12:31:01 UTC 
Created attachment 1077674 [details]
File: var_log_messages
Comment 13 Wilf 2015-12-23 15:28:11 UTC 
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
Comment 14 Fedora End Of Life 2016-07-19 18:02:27 UTC 
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.