Bug 651859

Summary: [abrt] anjuta-1:2.31.90.0-1.fc14: raise: Process /usr/bin/anjuta was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Martin Putniorz <mputniorz>
Component: anjutaAssignee: Debarshi Ray <debarshir>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: allen, debarshir, jhs, rpandit
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:05b80c307b0c69f9fabea241c344409ec99ba576
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-13 16:18:48 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: backtrace none

Description Martin Putniorz 2010-11-10 13:43:05 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: anjuta
component: anjuta
crash_function: raise
executable: /usr/bin/anjuta
kernel: 2.6.35.6-48.fc14.x86_64
package: anjuta-1:2.31.90.0-1.fc14
rating: 4
reason: Process /usr/bin/anjuta was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289396301
uid: 500

How to reproduce
-----
1. Execute Anjuta IDE
Comment 1 Martin Putniorz 2010-11-10 13:43:07 UTC 
Created attachment 459443 [details]
File: backtrace
Comment 2 allen 2010-11-30 20:00:24 UTC 
Package: anjuta-1:2.31.90.0-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Installed Fedora 14 under VirtualBox
2. Installed Anjuta, intltool, libtool, and g++
3. Attempted to run Anjuta and it crashed
Comment 3 Johannes Schmid 2010-12-09 09:51:16 UTC 
Most likely related to bug #658471
Comment 4 Johannes Schmid 2010-12-13 16:18:48 UTC 
Sorry for marking as duplicate of a higher bug number but the other bug has a lot more information on that issue!



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** This bug has been marked as a duplicate of bug 658471 ***