571455 – JRE_HOME environment variable set to a wrong value in /etc/profile.d/alljava.sh

Bug 571455 - JRE_HOME environment variable set to a wrong value in /etc/profile.d/alljava.sh

Summary: JRE_HOME environment variable set to a wrong value in /etc/profile.d/alljava.sh

Status:	RESOLVED DUPLICATE of bug 549395

Alias:	None

Product:	openSUSE 11.2
Classification:	openSUSE
Component:	Basesystem (show other bugs)
Version:	Final
Hardware:	x86-64 openSUSE 11.2

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Ruediger Oertel
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2010-01-17 11:30 UTC by Christopher Schuster
Modified:	2010-02-14 22:59 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

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

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

Description Christopher Schuster 2010-01-17 11:30:30 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.64 Safari/532.5

With installed Java the environment variables JAVA_HOME, JDK_HOME are set correctly, however the JRE_HOME variable is set to a wrong value.

> echo $JAVA_HOME
/usr/lib/jvm/java

> echo $JDK_HOME
/usr/lib/jvm/java 

> echo $JRE_HOME
/usr//jvm/jre


Reproducible: Always

Steps to Reproduce:
1.Install any version of java
2.Log into a valid user account
3.echo $JRE_HOME
Actual Results:  
/usr//jvm/jre

Expected Results:  
/usr/lib/jvm/jre

Comment 1 Christopher Schuster 2010-01-17 11:38:27 UTC

This can easily be fixed by changing line 21 of /etc/profile.d/alljava.sh of the aaa_base package from

  export JRE_HOME=/usr/$_libdir/jvm/jre

to

  export JRE_HOME=/usr/$__libdir/jvm/jre

Comment 2 Ruediger Oertel 2010-02-14 22:59:38 UTC

ah, okay. fixed already. marking as duplicate of bnc#549395

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