Description of problem: Everytime when i click reload on a tab, nautilus crashes. Version-Release number of selected component: nautilus-3.16.2-2.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: nautilus /mnt/vdo crash_function: vasprintf executable: /usr/bin/nautilus global_pid: 5425 kernel: 4.1.9-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 vasprintf at /usr/include/bits/stdio2.h:210 #3 g_vasprintf at gprintf.c:316 #4 g_strdup_vprintf at gstrfuncs.c:507 #5 g_strdup_printf at gstrfuncs.c:533 #6 ref_to_path at accessible-register.c:181 #7 spi_register_object_to_path at accessible-register.c:300 #8 emit_event at event.c:500 #9 state_event_listener at event.c:699 #13 atk_object_notify_state_change at atkobject.c:1218 #14 map_cb at a11y/gtkwidgetaccessible.c:100 Potential duplicate: bug 988200
Created attachment 1079661 [details] File: backtrace
Created attachment 1079662 [details] File: cgroup
Created attachment 1079663 [details] File: core_backtrace
Created attachment 1079664 [details] File: dso_list
Created attachment 1079665 [details] File: environ
Created attachment 1079666 [details] File: limits
Created attachment 1079667 [details] File: maps
Created attachment 1079668 [details] File: mountinfo
Created attachment 1079669 [details] File: namespaces
Created attachment 1079670 [details] File: open_fds
Created attachment 1079671 [details] File: proc_pid_status
Created attachment 1079672 [details] File: var_log_messages
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.