Chapter 2

Solaris Runtime Issues

This chapter describes runtime issues that are known to be problems. For late-breaking Solaris runtime issues that were identified too late to be included in these release notes, refer to the Solaris 9 (SPARC Platform Edition) Release Notes in the Solaris 9 Release and Installation Collection on http://docs.sun.com.

Smart Card Bugs

System Does Not Respond to Smart Card (4415094)

If ocfserv terminates and the display is locked, the system remains locked even when a smart card is inserted or removed.

Workaround: Perform the following steps to unlock your system.

Perform a remote login to the machine on which the ocfserv process terminated.
Become superuser.
Kill the dtsession process by typing the following in a terminal window.
% pkill dtsession

ocfserv restarts and smart card login and capability are restored.

Edit Config File Menu Item in Smartcards Management Console Does Not Work (4447632)

The Edit Config File menu item in the Smartcards Management Console does not edit smart card configuration files that are located in /etc/smartcard/opencard.properties. If the menu item is selected, a warning is displayed that indicates not to continue unless requested by technical support.

Workaround: Do not use the Edit Config File menu item in the Smartcards Management Console. For information on smart card configuration, see Solaris Smartcard Administration Guide.

Common Desktop Environment (CDE) Issues

Compiling Motif Programs on the Solaris 9 Operating Environment

A problem occurs when you compile a Motif program in the Solaris 9 operating environment under the following circumstances.

You link to a shared library that has been compiled in the Solaris 2.4, 2.5, 2.5.1 or 2.6 operating environments
The older library also uses the Motif application programming interface (API).

The Motif program uses Motif version 2.1 and the old shared library uses Motif version 1.2. A core dump occurs. This is not a binary compatibility problem for applications that were compiled in the Solaris 2.4, 2.5, 2.5.1, and 2.6 operating environments, which should run correctly in the Solaris 9 operating environment.

Workaround: If you have an older shared library that links directly to the Motif library, and if you want to compile a program in the Solaris 9 operating environment that links to both Motif and that older shared library, use a line such as the following to compile:
cc foo.c -o program -DMOTIF12_HEADERS -I/usr/openwin/include -I/usr/dt/include -lXm12 -lXt -lX11
In the previous example, program is the name of the program you are compiling.

Common Desktop Environment (CDE) Bugs

CDE Mailer Appears to Hang While Displaying Email With Long Lines (4418793)

If you try to read an email message with many long lines in any of the Solaris 9 Unicode or UTF-8 locales, CDE Mailer (dtmail) appears to hang, and the message does not display immediately.

Workaround: Choose one of the following workarounds.

Enlarge the dtmail Mailbox window to accommodate 132 columns.
Disable the Complex Text Layout feature by following these steps.
1. Become superuser.
2. Change directories to your system's locale directory.
  # cd /usr/lib/locale/locale-name
  In the previous example, locale-name refers to the name of your system's Solaris 9 Unicode or UTF-8 locale.
3. Rename the locale layout engine category.
  # mv LO_LTYPE LO_LTYPE-
  Note - Rename the locale layout engine category to the original name (LO_LTYPE) before you apply any patches to the locale layout engine.

PDASync Cannot Delete Last Entry From the Desktop (4260435)

After you delete the last item from the desktop, the item is restored from the handheld device to the desktop when you synchronize your handheld device. Examples of items that you might delete and have restored are the last appointment in your Calendar or the last address in the Address Manager.

Workaround: Manually delete the last entry from the handheld device prior to synchronization.

PDASync Does Not Support Data Exchange With the Multibyte Internationalized PDA Device (4263814)

If you exchange multibyte data between a PDA device and Solaris CDE, the data might be corrupted in both environments.

Workaround: Back up your data on your personal computer with the PDA backup utility before you run the PDASync application. If you accidentally exchange multibyte data and corrupt that data, restore your data from the backup.

Java Runtime Issue

Experimental `-Xoptimize` Option With Java 2 SDK, Version 1.2.2 Not Recommended for Use

Do not use the experimental -Xoptimize command-line option with Java 2 SDK, version 1.2.2. If you use the -Xoptimize option, the Java Virtual Machine (JVM) might fail or suffer from poor performance. This option might not be supported in future update versions of the Java 2 SDK 1.2.2, and is not supported in Java 2 SDK, versions 1.3.1 or 1.4.

System Administration Bugs

Solaris WBEM Services 2.5 Daemon Cannot Locate `com.sun` Application Programming Interface Providers (4619576)

The Solaris WBEM Services 2.5 daemon cannot locate providers that are written to the com.sun.wbem.provider interface or to the com.sun.wbem.provider20 interface. Even if you create a Solaris_ProviderPath instance for a provider that is written to these interfaces, the Solaris WBEM Services 2.5 daemon does not locate the provider.

Workaround: To enable the daemon to locate such a provider, stop and restart the Solaris WBEM Services 2.5 daemon.

# /etc/init.d/init.wbem stop

# /etc/init.d/init.wbem start

Note - If you use the javax API to develop your provider, you do not need to stop and restart the Solaris WBEM Services 2.5 daemon, as the daemon dynamically recognizes javax providers.

Some `com.sun` Application Programming Interface Method Invocations Fail Under XML/HTTP Transport Protocol (4497393, 4497399, 4497406, 4497411)

If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only CIM remote method invocation (RMI) is fully supported. Other protocols, such as XML/HTTP, are not guaranteed to work completely with the com.sun application programming interface.

The following table lists examples of invocations that execute successfully under RMI, but fail under XML/HTTP.

Method Invocation	Error Message
`CIMClient.close()`	`NullPointerException`
`CIMClient.execQuery()`	`CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED`
`CIMClient.getInstance()`	`CIM_ERR_FAILED`
`CIMClient.invokeMethod()`	`XMLERROR: ClassCastException`

Cannot Modify File System Mount Properties With Solaris Management Console Mounts and Shares Tool (4466829)

The Solaris Management Console Mounts and Shares tool cannot modify mount options on system-critical file systems such as / (root), /usr, and /var.