Bug 1306493

Summary: [abrt] totem: gtk_tree_model_get_valist(): totem killed by SIGSEGV
Product: [Fedora] Fedora Reporter: yucef sourani <youssef.m.sourani>
Component: totemAssignee: Bastien Nocera <bnocera>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: bnocera, cfergeau, ilya.gradina, youssef.m.sourani
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/128da06ef5c26eb80ca888b2d6b7af4b68ff2414
Whiteboard: abrt_hash:a1017d710d894094acf377224765eac0d851458a;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-22 12:41:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description yucef sourani 2016-02-11 01:48:49 UTC 
Version-Release number of selected component:
totem-3.19.3-2.fc24

Additional info:
reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        /usr/bin/totem --gapplication-service
crash_function: gtk_tree_model_get_valist
executable:     /usr/bin/totem
global_pid:     15724
kernel:         4.5.0-0.rc3.git1.1.fc24.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 gtk_tree_model_get_valist at gtktreemodel.c:1797
 #1 gtk_tree_model_get at gtktreemodel.c:1759
 #2 browse_cb at totem-grilo.c:688
 #3 queue_process at grl-source.c:2095
 #7 g_main_context_iteration at gmain.c:3901
 #8 g_application_run at gapplication.c:2363

Potential duplicate: bug 1210994
Comment 1 yucef sourani 2016-02-11 01:48:57 UTC 
Created attachment 1123066 [details]
File: backtrace
Comment 2 yucef sourani 2016-02-11 01:48:58 UTC 
Created attachment 1123067 [details]
File: cgroup
Comment 3 yucef sourani 2016-02-11 01:49:00 UTC 
Created attachment 1123068 [details]
File: core_backtrace
Comment 4 yucef sourani 2016-02-11 01:49:03 UTC 
Created attachment 1123069 [details]
File: dso_list
Comment 5 yucef sourani 2016-02-11 01:49:05 UTC 
Created attachment 1123070 [details]
File: environ
Comment 6 yucef sourani 2016-02-11 01:49:08 UTC 
Created attachment 1123071 [details]
File: exploitable
Comment 7 yucef sourani 2016-02-11 01:49:10 UTC 
Created attachment 1123072 [details]
File: limits
Comment 8 yucef sourani 2016-02-11 01:49:18 UTC 
Created attachment 1123073 [details]
File: maps
Comment 9 yucef sourani 2016-02-11 01:49:20 UTC 
Created attachment 1123074 [details]
File: mountinfo
Comment 10 yucef sourani 2016-02-11 01:49:23 UTC 
Created attachment 1123075 [details]
File: open_fds
Comment 11 yucef sourani 2016-02-11 01:49:25 UTC 
Created attachment 1123076 [details]
File: proc_pid_status
Comment 12 yucef sourani 2016-02-11 01:49:28 UTC 
Created attachment 1123077 [details]
File: var_log_messages
Comment 13 Jan Kurik 2016-02-24 14:29:27 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 14 Bastien Nocera 2016-09-21 16:23:45 UTC 
Do you have a way to reproduce this problem? Did it happen later on?
Comment 15 Bastien Nocera 2016-09-21 16:25:27 UTC 
*** Bug 1293025 has been marked as a duplicate of this bug. ***
Comment 16 yucef sourani 2016-09-21 21:36:41 UTC 
(In reply to Bastien Nocera from comment #14)
> Do you have a way to reproduce this problem? Did it happen later on?

i dont remember ,i think the problem   soloved later.
Comment 17 Bastien Nocera 2016-09-22 12:41:04 UTC 
Thanks for the update. I'll close this bug now, let me know if you hit it again, and we'll try to root-cause the problem.