Description of problem: I had several .pdf documents open, including a fill-in one. I asked for a new evince window. I selected a file, and boom. Version-Release number of selected component: evince-3.30.2-2.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: evince /home/hugh/29donino/14brookfield/tlab2019mar29/8ccd-Form-13_02-0066-2017-12-Participant-Statement_Fillable.pdf crash_function: atk_object_notify_state_change executable: /usr/bin/evince journald_cursor: s=984b08f01be3462796b94e4598d371cf;i=2c5b78;b=f8bd89db3514491d88bbbf47de37b4b9;m=35696013fa;t=5869753bf401a;x=4ecf86d77a788911 kernel: 5.0.6-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1104 Truncated backtrace: Thread no. 1 (10 frames) #0 atk_object_notify_state_change at ../atk/atkobject.c:1214 #1 ev_view_accessible_set_focused_element at ev-view-accessible.c:614 #2 _ev_view_set_focused_element at ev-view.c:2233 #3 _ev_view_focus_form_field at ev-view.c:2757 #4 ev_view_button_press_event at ev-view.c:2799 #5 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:129 #6 _g_closure_invoke_va at gclosure.c:873 #9 gtk_widget_event_internal at gtkwidget.c:7744 #10 gtk_widget_event at gtkwidget.c:7314 #11 propagate_event_up at gtkmain.c:2582
Created attachment 1555346 [details] File: backtrace
Created attachment 1555347 [details] File: cgroup
Created attachment 1555348 [details] File: core_backtrace
Created attachment 1555349 [details] File: cpuinfo
Created attachment 1555350 [details] File: dso_list
Created attachment 1555351 [details] File: environ
Created attachment 1555352 [details] File: exploitable
Created attachment 1555353 [details] File: limits
Created attachment 1555354 [details] File: maps
Created attachment 1555355 [details] File: mountinfo
Created attachment 1555356 [details] File: open_fds
Created attachment 1555357 [details] File: proc_pid_status
Created attachment 1555358 [details] File: var_log_messages
The cloud corefile analyzer failed so I had to allow ABRT to download tonnes of debug RPMs. Odd.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.