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
Created attachment 866619 [details] File: backtrace
Created attachment 866620 [details] File: cgroup
Created attachment 866621 [details] File: core_backtrace
Created attachment 866622 [details] File: dso_list
Created attachment 866623 [details] File: environ
Created attachment 866624 [details] File: exploitable
Created attachment 866625 [details] File: limits
Created attachment 866626 [details] File: maps
Created attachment 866627 [details] File: open_fds
Created attachment 866628 [details] File: proc_pid_status
Created attachment 866630 [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
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.