Description of problem: I created a new project. It shows the standard "hello world" program. Then pressed F3 to no avail, a few times. Finally, I pressed F9 to compile the program and immediately the program disappeared. Apparrantly the SIGSEGV. I haven't repeated yet, but will in a moment. The steps I took were: 1. Start up Anjuta, without any project open. 2. Create a new project for a C generic program without special libraries. 3. Wait for the "hello world" program 3. F3 a few times 4. F9 --> SIGSEGV results. Version-Release number of selected component: anjuta-3.10.2-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/anjuta crash_function: build_configuration_get_name executable: /usr/bin/anjuta kernel: 3.13.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 build_configuration_get_name at configuration-list.c:394 #1 build_configure_dialog at build.c:1143 #6 _gtk_action_emit_activate at deprecated/gtkaction.c:906 #7 closure_accel_activate at deprecated/gtkaction.c:1861 #12 gtk_accel_group_activate at gtkaccelgroup.c:910 #13 gtk_accel_groups_activate at gtkaccelgroup.c:948 #14 gtk_window_activate_key at gtkwindow.c:11239 #15 anjuta_window_key_press_event at anjuta-window.c:783 #16 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85 #21 gtk_widget_event_internal at gtkwidget.c:7168 Potential duplicate: bug 1010459
Created attachment 880369 [details] File: backtrace
Created attachment 880370 [details] File: cgroup
Created attachment 880371 [details] File: core_backtrace
Created attachment 880372 [details] File: dso_list
Created attachment 880373 [details] File: environ
Created attachment 880374 [details] File: exploitable
Created attachment 880375 [details] File: limits
Created attachment 880376 [details] File: maps
Created attachment 880377 [details] File: open_fds
Created attachment 880378 [details] File: proc_pid_status
Created attachment 880379 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.