Bug 578364 - [abrt] crash in java-1.6.0-openjdk-1:1.6.0.0-36.b17.fc12: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in java-1.6.0-openjdk-1:1.6.0.0-36.b17.fc12: Process /usr/lib/jv...
Keywords:
Status: CLOSED DUPLICATE of bug 551835
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Andrew Haley
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:74d9175904377ef2035a2d9381c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-31 02:54 UTC by Engle
Modified: 2013-01-10 23:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-15 20:16:31 UTC


Attachments (Terms of Use)
File: backtrace (65.49 KB, text/plain)
2010-03-31 02:54 UTC, Engle
no flags Details

Description Engle 2010-03-31 02:54:29 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: java -cp .:jars/jxplorer.jar:jars/help.jar:jars/jhall.jar:jars/junit.jar com.ca.directory.jxplorer.JXplorer
component: java-1.6.0-openjdk
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java
kernel: 2.6.32.9-70.fc12.i686
package: java-1.6.0-openjdk-1:1.6.0.0-36.b17.fc12
rating: 3
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Engle 2010-03-31 02:54:34 UTC
Created attachment 403646 [details]
File: backtrace

Comment 2 Paul Nittel 2010-04-08 19:17:57 UTC

How to reproduce
-----
1. Download groovy 1.7.2
2. Define JAVA_HOME to be OpenJDK 1.6
3. Run groovyConsole by double-clicking in file manager


Comment
-----
The groovy GUI comes up for a few seconds then disappears.
UseThisJava is a symbolic link to the openjdk.

Comment 3 Omair Majid 2010-07-15 20:16:31 UTC

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


Note You need to log in before you can comment on or make changes to this bug.