Description of problem: No particular steps here. Happened during autocompletion when editing C++ code. Version-Release number of selected component: anjuta-3.6.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: anjuta crash_function: update_completion executable: /usr/bin/anjuta kernel: 3.8.1-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 update_completion at gtksourcecompletion.c:3180 #5 gtk_text_buffer_emit_insert at gtktextbuffer.c:926 #6 gtk_text_buffer_insert_interactive at gtktextbuffer.c:1018 #7 gtk_text_buffer_insert_interactive_at_cursor at gtktextbuffer.c:1056 #8 gtk_text_view_commit_text at gtktextview.c:8073 #9 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004 #10 _g_closure_invoke_va at gclosure.c:840 #12 g_signal_emit_by_name at gsignal.c:3393 #13 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004 #14 _g_closure_invoke_va at gclosure.c:840 Potential duplicate: bug 830995
Created attachment 707468 [details] File: backtrace
Created attachment 707469 [details] File: cgroup
Created attachment 707471 [details] File: core_backtrace
Created attachment 707472 [details] File: dso_list
Created attachment 707474 [details] File: environ
Created attachment 707475 [details] File: limits
Created attachment 707476 [details] File: maps
Created attachment 707477 [details] File: open_fds
Created attachment 707478 [details] File: proc_pid_status
Created attachment 707479 [details] File: var_log_messages
Thanks for your report! We tracked this down to a bug in gtksourceview recently which is at least fixed in the development version of gtksourceview.
Anjuta crashed while working on a C++ Makefile project. I do not remember what I actually did at the time of the crash. backtrace_rating: 4 cmdline: anjuta crash_function: update_completion executable: /usr/bin/anjuta kernel: 3.8.5-201.fc18.x86_64 package: anjuta-3.6.2-1.fc18 reason: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1 xsession_errors:
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.