Bug 22015 – Java Jdk (1.2.2 .....) compatibility problems

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 22015 - Java Jdk (1.2.2 .....) compatibility problems

Summary:	Java Jdk (1.2.2 .....) compatibility problems

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	glibc (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i586 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jakub Jelinek
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-12-10 05:51 EST by Need Real Name
Modified:	2016-11-24 09:55 EST (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-12-11 13:30:21 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2000-12-10 05:51:55 EST

Jdk 1.2.2 (Sun) is not compatible anymore with Linux Red Hat 7.0 (!!!)

It crashes (Segmentation fault) when javac or java are run in the command line.
(It is ok with Linux Red Hat 6.2)

Jdk 1.3 can be run normally.

But products like JBuilder 4 (working with Jdk 1.3), ok with red hat 6.2, can't be installed (Segmentation fault again) with red hat 7.0

Comment 1 Bill Nottingham 2000-12-10 12:21:25 EST

Almost certainly a glibc issue. Make sure you install the errata glibc package.

Comment 2 Jakub Jelinek 2000-12-11 13:30:18 EST

There was a bug fixed in glibc which was seen by JDK segfaults.
What does rpm -q glibc say? You should use glibc-2.2-5.

Comment 3 Jakub Jelinek 2001-02-23 07:55:19 EST

Closed due to inactivity.

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