Bug 1068930

Summary: [abrt] gedit: g_type_check_instance_cast(): gedit killed by SIGSEGV
Product: [Fedora] Fedora Reporter: D. Charles Pyle <dcharlespyle>
Component: geditAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/f890bf589bbabbc2b248998b2497c994cf2c7822
Whiteboard: abrt_hash:13ccea4a6a1b19bca8f8fae8efe2691aa14ce01c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:03:37 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description D. Charles Pyle 2014-02-23 10:34:49 UTC 
Description of problem:
Tried to open a file with gedit inside an archive opened with Archive manager.  IT crashed and threw this error.

Version-Release number of selected component:
gedit-3.11.90-2.fc21

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        gedit /home/dcpyle/.cache/.fr-KsUPi4/lightdm-1.9.8.tar-1
crash_function: g_type_check_instance_cast
executable:     /usr/bin/gedit
kernel:         3.14.0-0.rc3.git5.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_type_check_instance_cast at gtype.c:4002
 #1 remove_tab at gedit/gedit-tab.c:569
 #2 remove_tab_idle at gedit/gedit-tab.c:963
 #6 g_main_context_iteration at gmain.c:3773
 #7 g_application_run at gapplication.c:2113
Comment 1 D. Charles Pyle 2014-02-23 10:34:52 UTC 
Created attachment 866619 [details]
File: backtrace
Comment 2 D. Charles Pyle 2014-02-23 10:34:54 UTC 
Created attachment 866620 [details]
File: cgroup
Comment 3 D. Charles Pyle 2014-02-23 10:34:55 UTC 
Created attachment 866621 [details]
File: core_backtrace
Comment 4 D. Charles Pyle 2014-02-23 10:34:57 UTC 
Created attachment 866622 [details]
File: dso_list
Comment 5 D. Charles Pyle 2014-02-23 10:34:59 UTC 
Created attachment 866623 [details]
File: environ
Comment 6 D. Charles Pyle 2014-02-23 10:35:01 UTC 
Created attachment 866624 [details]
File: exploitable
Comment 7 D. Charles Pyle 2014-02-23 10:35:02 UTC 
Created attachment 866625 [details]
File: limits
Comment 8 D. Charles Pyle 2014-02-23 10:35:04 UTC 
Created attachment 866626 [details]
File: maps
Comment 9 D. Charles Pyle 2014-02-23 10:35:06 UTC 
Created attachment 866627 [details]
File: open_fds
Comment 10 D. Charles Pyle 2014-02-23 10:35:08 UTC 
Created attachment 866628 [details]
File: proc_pid_status
Comment 11 D. Charles Pyle 2014-02-23 10:35:10 UTC 
Created attachment 866630 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 15:31:17 UTC 
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
Comment 13 Fedora End Of Life 2016-07-19 11:03:37 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.