Description of problem: Tried to open a non-existent file by entering its location in the chooser. Version-Release number of selected component: gedit-3.15.1-1.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: gedit crash_function: build_recent_info executable: /usr/bin/gedit kernel: 3.20.0-0.rc0.git7.2.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (7 frames) #0 build_recent_info at gtkrecentmanager.c:1117 #1 gtk_recent_manager_get_items at gtkrecentmanager.c:1322 #2 gedit_recent_get_items at gedit/gedit-recent.c:219 #3 get_recent_files_list at gedit/gedit-open-document-selector-store.c:496 #4 update_list_dispatcher at gedit/gedit-open-document-selector-store.c:629 #5 g_task_thread_pool_thread at gtask.c:1215 #7 g_thread_proxy at gthread.c:764
Created attachment 993416 [details] File: backtrace
Created attachment 993417 [details] File: cgroup
Created attachment 993418 [details] File: core_backtrace
Created attachment 993419 [details] File: dso_list
Created attachment 993420 [details] File: environ
Created attachment 993421 [details] File: limits
Created attachment 993422 [details] File: maps
Created attachment 993423 [details] File: open_fds
Created attachment 993424 [details] File: proc_pid_status
Created attachment 993425 [details] File: var_log_messages
Typeahead seems to be broken when opening files (need another bug for this), so I did Ctrl+L and began entering a filename in. When I pressed enter gedit disappeared.
Typeahead being broken is bug 1215559.
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.