Name: gm110360 Date: 08/05/2002


FULL PRODUCT VERSION :
java version "1.4.1-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-beta-b14)
Java HotSpot(TM) Client VM (build 1.4.1-beta-b14, mixed mode)

FULL OPERATING SYSTEM VERSION : Linux tux 2.4.9-31 #1 Tue
Feb 26 07:11:02 EST 2002 i686 unknown

ADDITIONAL OPERATING SYSTEMS : Red Hat Linux release 7.1 (Seawolf)
glibc-2.2.4-24

Solaris 2.8



DESCRIPTION OF THE PROBLEM :
After installing J2SDK 1.4.1 beta as root, and then running
(as a normal user) a (swing-based) JAR, I received a
complaint in the shell (see the error message text) from
java.util.prefs.FileSystemPreferences

The first two of these four lines are repeated each time the
application is run until the problem is fixed (see
work-around). I am unclear about what functions of the Java
environment are affected by this (the new 1.4 preferences
api?) or is it just an annoyance?

Note: my application does not explicitly instantiate any
object in the java.util.prefs.* package, though I create
java.io.File objects, ZipFile, various streams, etc.

The problem is also reproduicble on Solaris 2.8 using JDK1.4.0, 1.4.1

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. As 'root' user: install j2sdk
2. As normal user: run a java app


EXPECTED VERSUS ACTUAL BEHAVIOR :
Installer .bin script should have either created the
appropriate files, or issued a prominent message to the
(root) user to run some Java application as root to cause
these system files to be created.



ERROR MESSAGES/STACK TRACES THAT OCCUR :
Jul 24, 2002 5:40:43 PM java.util.prefs.FileSystemPreferences$3 run
WARNING: Could not create system preferences directory. System preferences are
unusable.
Jul 24, 2002 5:41:17 PM java.util.prefs.FileSystemPreferences
checkLockFile0ErrorCode
WARNING: Could not lock System prefs.Unix error code 1217854024.
Jul 24, 2002 5:41:17 PM java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException:
Couldn't get file lock.

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER WORKAROUND :
Run a Java app that exhibits this problem as a priviliged
user (hmmm, a bit of a security risk)
(Review ID: 159882)
======================================================================

Name: rl43681 Date: 09/25/2002


FULL OPERATING SYSTEM VERSION :
Linux 2.4.18-6mdk #1 Fri Mar 15 02:59:08 CET 2002 i686 unknown

ADDITIONAL OPERATING SYSTEMS :
glibc-2.2.4-25mdk


EXTRA RELEVANT SYSTEM CONFIGURATION :
J2SE 1.4.1 beta installation directory is writable for
'root' user only. Running application under normal
(non-root) user identity.

A DESCRIPTION OF THE PROBLEM :
Running Java application which uses Swing results in
following printed to console:

Jul 17, 2002 9:41:54 AM
java.util.prefs.FileSystemPreferences$3 run
WARNING: Could not create system preferences directory.
System preferences are unusable.

...


Jul 17, 2002 9:42:26 AM
java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode
WARNING: Could not lock System prefs.Unix error code 1246886104.
Jul 17, 2002 9:42:26 AM
java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush system prefs:
java.util.prefs.BackingStoreException: Couldn't get file lock.
Jul 17, 2002 9:42:56 AM
java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode
WARNING: Could not lock System prefs.Unix error code 1246886104.
Jul 17, 2002 9:42:56 AM
java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush system prefs:
java.util.prefs.BackingStoreException: Couldn't get file lock.
...
and so it goes until Java stops

REGRESSION. Last worked in version 1.4

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Start any Java Swing application that runs for a while
(e.g. NetBeans)
2. Check console output

EXPECTED VERSUS ACTUAL BEHAVIOR :
I expect that none of the warnings above to be printed to
console.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Jul 17, 2002 9:41:54 AM java.util.prefs.FileSystemPreferences$3 run
WARNING: Could not create system preferences directory. System preferences are
unusable.

...


Jul 17, 2002 9:42:26 AM java.util.prefs.FileSystemPreferences
checkLockFile0ErrorCode
WARNING: Could not lock System prefs.Unix error code 1246886104.
Jul 17, 2002 9:42:26 AM java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException:
Couldn't get file lock.
Jul 17, 2002 9:42:56 AM java.util.prefs.FileSystemPreferences
checkLockFile0ErrorCode
WARNING: Could not lock System prefs.Unix error code 1246886104.
Jul 17, 2002 9:42:56 AM java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException:
Couldn't get file lock.

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
import javax.swing.JDialog;
class Test {
  public static void main(String[] params) throws Exception {
    final JDialog dlg = new JDialog();
    dlg.setModal(true);
    dlg.show();
  }
}
---------- END SOURCE ----------
(Review ID: 159450)
======================================================================

Name: rl43681 Date: 09/25/2002


FULL OPERATING SYSTEM VERSION :
Debian GNU/Linux
Kernel version 2.4.18
 - from "kernel-image-2.4.18-k7" package
Glibc version 2.2.5
 - from "libc6" package
Libstdc++ version 2.9-glibc2.1
 - from "libstdc++2.9-glibc2.1" package

A DESCRIPTION OF THE PROBLEM :
Something within the font management part of AWT is dying on
me when I try to use the "CDox"
 ( http://sammael.tabu.stw-bonn.de:8081/cdox/Show ).

It could be my setup though.
Thing is, this CDox program is the first I've ever used that
actually employed heavyweight AWT gear. So the first time I
ran it I found out the hard way that the libfontmanager.so
native code has to link against libstdc++-libc6.1-1.so.2.
Unfortunately this is an old library as far as Debian is
concerned, with libstdc++-libc6.1-2.so.3 being the version
that recent binary Debian packages depend on.

I don't know enough about the whole GNU/Linux libc/libstdc++
insanity to work out whether this is the actual problem,
rather then a bug in AWT. It could be that the old deb
package which provides the version of libstdc++ that
libfontmanager needs doesn't actually sit properly with
glibc-2.2 and the more modern versions of libstdc++ that are
used by 99% of modern Debian packages.



STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Install the CDox package
2. Invoke the CDox program


EXPECTED VERSUS ACTUAL BEHAVIOR :
When invoked (see error messages below), the program's
splash screen comes up and the progress bar in the splash
screen shows it working through its startup routine.

It goes through a few steps of the startup routine, and at
the stage called "Examining local fonts" it dies with an
assertion failure inside native code for AWT.



ERROR MESSAGES/STACK TRACES THAT OCCUR :
2:24pm bungley ~ -> java -jar /usr/share/java/cdox.jar
Jul 19, 2002 2:24:49 PM java.util.prefs.FileSystemPreferences$3 run
WARNING: Could not create system preferences directory. System preferences are
unusable.
java: ../../../src/share/native/sun/awt/font/t2k/t1.c:2166:
tsi_T1GetGlyphIndexFromAdobeCode: Assertion `0' failed.
Abort



REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
Source files for the CDox program are available from it's homepage (see URL in
description).

---------- END SOURCE ----------
(Review ID: 159656)
======================================================================