Version-Release number of selected component: anjuta-3.11.4-1.fc21 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: anjuta crash_function: g_type_check_instance_is_a executable: /usr/bin/anjuta kernel: 3.14.0-0.rc1.git0.2.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_a at gtype.c:3969 #1 gtk_widget_set_visible at gtkwidget.c:8400 #2 _g_closure_invoke_va at gclosure.c:833 #5 gtk_toggle_button_toggled at gtktogglebutton.c:512 #6 gtk_toggle_button_clicked at gtktogglebutton.c:619 #7 _g_closure_invoke_va at gclosure.c:833 #10 object_set_property at gobject.c:1377 #11 g_object_set_property at gobject.c:2305 #12 g_settings_binding_key_changed at gsettings.c:2482 #17 g_settings_real_change_event at gsettings.c:280
Created attachment 860620 [details] File: backtrace
Created attachment 860621 [details] File: cgroup
Created attachment 860622 [details] File: core_backtrace
Created attachment 860623 [details] File: dso_list
Created attachment 860624 [details] File: environ
Created attachment 860625 [details] File: exploitable
Created attachment 860626 [details] File: limits
Created attachment 860627 [details] File: maps
Created attachment 860628 [details] File: open_fds
Created attachment 860629 [details] File: proc_pid_status
Created attachment 860630 [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.