Bug 1031357

Summary: [abrt] mate-file-archiver-1.6.1-0.1.git95ebd69.fc21: g_type_check_instance_cast: Process /usr/bin/engrampa was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Christopher Meng <i>
Component: mate-file-archiverAssignee: Dan Mashal <dan.mashal>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dan.mashal, fedora, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a3297aa6c0146baf981371522316d0d6b7337307
Whiteboard: abrt_hash:6185f469d4d67e5628d2d86fa19d48e33e18c353
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-17 21:24:40 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Christopher Meng 2013-11-17 07:25:19 UTC 
Description of problem:
Open an archive from Open buttom and then it crashed.

Version-Release number of selected component:
mate-file-archiver-1.6.1-0.1.git95ebd69.fc21

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/engrampa /home/rpmaker/Desktop/cdk-5.0-20131107.tgz
crash_function: g_type_check_instance_cast
executable:     /usr/bin/engrampa
kernel:         3.12.0-1.fc21.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 g_type_check_instance_cast at gtype.c:4009
 #1 close__step2 at fr-window.c:689
 #7 gtk_main at gtkmain.c:1257
Comment 1 Christopher Meng 2013-11-17 07:25:29 UTC 
Created attachment 825082 [details]
File: backtrace
Comment 2 Christopher Meng 2013-11-17 07:25:34 UTC 
Created attachment 825083 [details]
File: cgroup
Comment 3 Christopher Meng 2013-11-17 07:25:38 UTC 
Created attachment 825084 [details]
File: core_backtrace
Comment 4 Christopher Meng 2013-11-17 07:25:42 UTC 
Created attachment 825085 [details]
File: dso_list
Comment 5 Christopher Meng 2013-11-17 07:25:48 UTC 
Created attachment 825086 [details]
File: environ
Comment 6 Christopher Meng 2013-11-17 07:25:52 UTC 
Created attachment 825087 [details]
File: exploitable
Comment 7 Christopher Meng 2013-11-17 07:25:56 UTC 
Created attachment 825088 [details]
File: limits
Comment 8 Christopher Meng 2013-11-17 07:26:01 UTC 
Created attachment 825089 [details]
File: maps
Comment 9 Christopher Meng 2013-11-17 07:26:05 UTC 
Created attachment 825090 [details]
File: open_fds
Comment 10 Christopher Meng 2013-11-17 07:26:09 UTC 
Created attachment 825091 [details]
File: proc_pid_status
Comment 11 Christopher Meng 2013-11-17 07:26:13 UTC 
Created attachment 825092 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-11-17 21:24:40 UTC 
Sorry,
f20 isn't released and you post a report against rawhide.
I can't confim this in f20.
Do you really expect that upstream or me works on fedora rawhide report now?
You are a fedora packager and you should be able to fix the code for yourself.
Or check your VM for issues.

sigh
Comment 13 Christopher Meng 2013-11-18 01:26:43 UTC 
(In reply to Wolfgang Ulbrich from comment #12)
> Sorry,
> f20 isn't released and you post a report against rawhide.
> I can't confim this in f20.
> Do you really expect that upstream or me works on fedora rawhide report now?
> You are a fedora packager and you should be able to fix the code for
> yourself.
> Or check your VM for issues.
> 
> sigh

Yes, I can fix the code by myself when I have time. It isn't hard for me. 

Thanks.