Bug 894579

Summary: [abrt] anjuta-3.4.4-1.fc17: book_tree_find_book: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: gzor.ka
Component: anjutaAssignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jhs, kalevlember, mclasen, rakesh.pandit
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:b2404b0cd87e822ba9d09a4e3f781d51c9f7e845
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 04:39:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description gzor.ka 2013-01-12 12:39:06 UTC
Description of problem:
Problem appear then using devhelper as plugin inside anjuta window.
Till typing first letter anjuta stuck.


Version-Release number of selected component:
anjuta-3.4.4-1.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        anjuta
crash_function: book_tree_find_book
kernel:         3.6.11-1.fc17.i686

truncated backtrace:
:Thread no. 1 (7 frames)
: #0 book_tree_find_book at dh-book-tree.c:266
: #1 book_tree_add_book_to_store at dh-book-tree.c:408
: #2 g_cclosure_marshal_VOID__OBJECT at gmarshal.c:1272
: #7 book_manager_add_from_filepath at dh-book-manager.c:756
: #8 book_manager_new_possible_book_cb at dh-book-manager.c:371
: #13 g_main_context_iteration at gmain.c:3207
: #14 g_application_run at gapplication.c:1499

Comment 1 gzor.ka 2013-01-12 12:39:09 UTC
Created attachment 677285 [details]
File: core_backtrace

Comment 2 gzor.ka 2013-01-12 12:39:11 UTC
Created attachment 677286 [details]
File: environ

Comment 3 gzor.ka 2013-01-12 12:39:13 UTC
Created attachment 677287 [details]
File: limits

Comment 4 gzor.ka 2013-01-12 12:39:16 UTC
Created attachment 677288 [details]
File: backtrace

Comment 5 gzor.ka 2013-01-12 12:39:18 UTC
Created attachment 677289 [details]
File: cgroup

Comment 6 gzor.ka 2013-01-12 12:39:20 UTC
Created attachment 677290 [details]
File: smolt_data

Comment 7 gzor.ka 2013-01-12 12:39:22 UTC
Created attachment 677291 [details]
File: executable

Comment 8 gzor.ka 2013-01-12 12:39:25 UTC
Created attachment 677292 [details]
File: maps

Comment 9 gzor.ka 2013-01-12 12:39:27 UTC
Created attachment 677293 [details]
File: dso_list

Comment 10 gzor.ka 2013-01-12 12:39:29 UTC
Created attachment 677294 [details]
File: proc_pid_status

Comment 11 gzor.ka 2013-01-12 12:39:31 UTC
Created attachment 677295 [details]
File: var_log_messages

Comment 12 gzor.ka 2013-01-12 12:39:34 UTC
Created attachment 677296 [details]
File: open_fds

Comment 14 Fedora End Of Life 2013-07-04 00:42:10 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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.

Comment 15 Fedora End Of Life 2013-08-01 04:39:54 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.