Issue 50144 - OOo now starts without Java by default, making it inaccessible by default
Summary: OOo now starts without Java by default, making it inaccessible by default
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: ui
Classification: Code
Component: AccessBridge (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@ui
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-31 18:23 UTC by korn
Modified: 2005-06-01 14:20 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

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

Note You need to log in before you can comment on or make changes to this issue.
Description korn 2005-05-31 18:23:19 UTC 
On JDS Cinnabar 36 configure desktop for accessibility.  Java 1.5.0_03 is
already configured for accesibility.
Now launch SO8.  It is not accessible.  You need to go to Java Options in order
to select the 1.5.0_03 JRE and restart StarOffice before you can use it.  This
will be an insurmountable barrier for users with disabilities, who won't be able
to manipulate the GUI in order to make this configuration change.  

At a minimum when the desktop accessibility flag it set, SO8/OOo should *always*
use the accessible Java if it can find it.  This is a regression.
Comment 1 malte_timmermann 2005-06-01 09:21:15 UTC 
Latest versions of SO8 come with Java 1.5.0.3, so please try with build m106...
Comment 2 eric.savary 2005-06-01 09:26:56 UTC 
ES->OBR: please evaluate if this is an SO or JDS bug. At least this issue should
remain assigned to RU.
Comment 3 Olaf Felka 2005-06-01 09:31:19 UTC 
On a fresh installed Cinnabar 36 with a new user I can't reproduce: the 'use
Java'  checkbox is checked and Java 1.5.0_03 is selected fur use.
Comment 4 eric.savary 2005-06-01 13:44:41 UTC 
Sorry I meant "this issue should NOT remain assigned to RU". Thus reassigning to me.

->Peter: try to reproduce it. We cannot reproduce it here.
Comment 5 eric.savary 2005-06-01 13:45:19 UTC 
.
Comment 6 eric.savary 2005-06-01 13:45:42 UTC 
.
Comment 7 korn 2005-06-01 14:20:39 UTC 
I'm not able to reproduce the problem as a new user.  In my test case, I kept my
/home directory and upgraded to a new version of SO for an existing previous SO
user (had preferences files from a previous build of SO 8).  I recall now that I
was surprised I had to go through the registration dialogs when I launched SO.

So even if this bug can be reproduced, this is not a real end-user case.  Sorry
for the fire drill.