test

Solaris 8 (SPARC Platform Edition) 2/02 Release Notes

Chapter 2 Solaris Runtime Issues

This chapter describes known runtime problems.

Note -

The name of this product is Solaris 8 2/02 , but code and path or package path names might use Solaris 2.8 or SunOS 5.8. Always follow the code or path as it is written.

Power Management Bugs

Power Management Resume Crashes After USB Devices Are Hot-Plugged (4507408)

If you hot-plug a USB device and then suspend your system, the system might crash during the resume phase.

Workaround: If a USB device has been hot-plugged, reboot the system before you perform a power management suspend.

USB Issues

Audio Applications Might Stop Working After a USB Audio Device Is Hot-Unplugged (4424286)

If you hot-unplug a USB audio device the links to /dev/audio are broken. As a result, some audio applications might not recognize audio devices, including on-board audio. Rebooting the system or hot-plugging the USB audio device has no effect.

Workaround: Perform the following steps after a USB audio device is hot-unplugged.

  1. Become superuser.

  2. Correct the broken links by typing the following on a command line.


    # rm /dev/audio*
# /usr/sbin/devfsadm -c audio

For more information see devfsadm(1M).

USB Speakers Might Not Produce Sound

Third-party USB speakers might not produce sound after the USB driver is attached. Increasing the speaker volume or hot-plugging the device might not have any effect.

Workaround: Power cycle the USB speakers.

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.

  1. Use rlogin to connect to the system on which the ocfserv process terminated.

  2. Kill the dtsession process by typing the following in a terminal window.


    % pkill dtsession

The ocfserv process restarts and smart card login and functionality will be restored.

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

The Edit Config File menu item in the Smart Cards 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 Smart Cards Management Console. For information on smart card configuration, see Solaris Smart Cards Administration Guide.

Common Desktop Environment (CDE) Issues

Compiling Motif Programs on the Solaris 8 Operating Environment

A problem occurs when you compile a Motif program in the Solaris 8 operating environment under the following circumstances. When 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, 2.6 operating environments, which should run correctly in the Solaris 8 operating environment.

Workaround: If an older shared library links directly to the Motif library, and if you are compiling a program in the Solaris 8 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 this line, program is the name of the program you are compiling.

Common Desktop Environment Bugs

OpenWindows File Manager Fails to Mount Diskette (4329368)

The OpenWindowsTM File Manager fails to display a File Manager view that lists the contents of a floppy disk in certain circumstances. The problem occurs when you insert a floppy disk into the drive on a system that also has a SCSI removable media device. When you select Check for Floppy from the File menu in File Manager, File Manager mounts the floppy disk in the /floppy directory, but fails to display a File Manager view that lists the floppy disk contents.

Workaround: Choose one of the following workarounds.

To prevent this problem, apply patch 109463-01.

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.

System Administration Bugs

Remote Display of Solaris Management Console Hangs (4488117)

When you remotely display the Solaris Management Console on the Solaris 8 7/01, or 2/02 operating environment, opening a dialog box in the console causes the console, including the open dialog box, to hang.

Workaround: Use the Solaris Management Console on your local system to connect to, and manage, a system running the Solaris 8 7/01, or 2/02 operating environment. Follow these steps.

  1. Close the hung console window.

  2. Start the Solaris Management Console on your local system.

  3. Select Open Toolbox from the console menu.

  4. Click the Server Toolbox tab and select, or enter, the name of the remote system you want to manage.

  5. Click the Open button.

You can now use the console to manage the remote system.

Web-Based Enterprise Management (WBEM) HTTP Service Does Not Automatically Start (4486999)

The WBEM HTTP service in the Solaris 8 operating environment does not automatically start. If you want to use HTTP to connect to WBEM, you must manually start the WBEM HTTP service.

Workaround: To manually start the WBEM HTTP service, follow these steps.

  1. Become superuser.

  2. Stop the WBEM server if it is running.


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

  3. Set your classpath to include the following .jar files.


    # CLASSPATH=/usr/sadm/lib/wbem/cimapi.jar:/usr/sadm/lib/xml.jar:\
  /usr/sadm/lib/wbem/cimom.jar
# export CLASSPATH

  4. Start the HTTP service.


    # java com.sun.wbem.client.HttpService &

  5. Start the Common Information Model (CIM) Object Manager service.


    # /usr/sadm/lib/wbem/wbemconfig &

WBEM Event Delivery Fails When Lowercase Is Used (4441369)

If a Solaris provider generates indications and the class name is set to lowercase, the event delivery fails.

Workaround: Use uppercase characters to define indication class names.

Incorrect Error Message When Using flarcreate -e and -E (4404811)

If you run the flarcreate command with both the -e and -E options an error is encountered. The following message is displayed. 


ERROR: Options -D and -f are mutually exclusive

The message should read as follows.


ERROR: Options -E and -e are mutually exclusive

Workaround: Ignore the error message. Do not use the -e and -E options together.

Obsolete Files Still Present in Help System (4339515)

After selecting Help -> Information from the Front Panel, a list of obsolete files is returned. The correct file is S8FCSreleasenotes.

CIM_ERR_LOW_ON_MEMORY Error Occurs When Trying to Add Data With WBEM (4312409)

The following error message is displayed when memory is low:


CIM_ERR_LOW_ON_MEMORY
You cannot add more entries when the CIM Object Manager has run low on memory. You must reset the CIM Object Manager Repository.

Workaround: To reset the CIM Object Manager Repository, follow these steps.

  1. Become superuser.

  2. Stop the CIM Object Manager.


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

  3. Remove the JavaSpaces log directory. 


    # /bin/rm -rf /var/sadm/wbem/logr

  4. Restart the CIM Object Manager. 


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

    Note -

    You lose any proprietary definitions in your datastore. You must recompile the MOF files that contain those definitions by using the mofcomp command. For example: 


    # /usr/sadm/bin/mofcomp -u root -p root_password your_mof_file

Java Runtime Bugs

libjvm.so Does Not Function Correctly When Using dlopen (4270715)

libjvm.so does not function correctly if it is brought into the process using dlopen. It must be linked into the executable when that object is created.

Workaround: Explicitly name libjvm.so (-ljvm) and libjava.so (-ljava) as dependencies when you create an executable.

AnswerBook2 Bugs

The ab2admin Command Intermittently Indicates command failed Even Though the Command Succeeded (4242577)

If the ab2admin command fails, the error message contains additional information besides command failed. For example, it might also include path not found or invalid ID.

Workaround: If the message command failed is displayed, ensure that the operation failed. For example, if the command you submitted should have deleted a collection from the AnswerBook2TM database, type the following command to verify that the collection is displayed in the database.


# ab2admin -o list
You can frequently ignore the message command failed when no additional information is provided.

ab2cd Script Displays an Erroneous Error Message (4256516)

During the startup of an AnswerBook2 server, the ab2cd script might display the following erroneous error message. 


sort: can't read /tmp/ab1_sort.XXX: No such file or directory

This error message states that the ab2cd script has not located any of the AnswerBook (Display PostScriptTM) collections on the CD.

Workaround: Ignore the error message.

Localization Issues

Use Font Downloader to Print From Any Non-ISO8859-1 Locale

Perform the following steps to print from any non-ISO8859-1 locale by using the Font Downloader.

  1. Log in to CDE.

  2. Type fdl at the command line to start the Font Downloader.

  3. Specify the printer by selecting Add from the Printer menu.

  4. Select Font Bundle from the Download menu.

    The font bundles are then downloaded to the specified printer, depending on what codeset is needed for printing.

Runtime Localization Bugs

The Euro Currency Symbol Is Not Adequately Supported in the UTF-8 and Greek Locales (4363812, 4305075)

The euro currency symbol is not generated when you press ALTGr+E in the UTF-8 locales.

Workaround: Choose one of the following workarounds.

Note -

In the Greek locale type, dumpcs at the console prompt. Then copy and paste the euro currency symbol.

kkcv.sh Dumps Core In Japanese Locale (4394340)

kkcv is an input method server for Japanese 4.x Binary Compatibility( BCP) applications. When LDAP is used, kkcv dumps core repeatedly with the error message:


cssd: The process "kkcv.sh" has been killed by sig#134, core dumped

This problem occurs in all locales when 'ja' locale is installed by using the Languages CD.

Workaround: If you do not need to use the Japanese BCP feature, configure your system not to start input method servers for BCP applications:

  1. Copy /usr/lib/css.d/cs00.sh to /etc/css.d.


    # cp -p /usr/lib/css.d/cs00.sh /etc/css.d

  2. Edit /etc/css.conf and comment out the line of /usr/lib/css.d with `#'.


    # /etc/css.conf

  3. Restart the CS monitor daemon.


    # sh /etc/init.d/loc.ja.cssd stop
# sh /etc/init.d/loc.ja.cssd start

Warning Messages Might Appear When Launching Java Applications From Any UTF-8 Locale (4342801)

LucidaSansLat4 font aliases are not available, so related error messages might appear when you launch a Java application from any UTF-8 locale.

Workaround: Log in to the ISO-1 equivalent of the locale and launch the Java application from there.

Some Greek Characters Are Not Available in CDE (4179411)

Some dead-key combinations do not work correctly in CDE. Also, names of months do not function correctly in the Calendar Manager in the Greek locale.

Cannot Print Extended Characters in Calendar Manager in All Partial Locales (4285729)

If you attempt to print extended characters when you use Calendar Manager in a partial locale, the extended characters do not print correctly.

Cutting and Pasting Text Between Arabic and UTF-8 English Does Not Work (4287746)

You cannot cut or paste Arabic text between an application or window that is running under en_US.UTF-8 in Arabic input mode and an application or window running under ar_EY.ISO8859-6 in Arabic input mode.

The CDE Extras Drop-Down Menu Is Not Available for European Locales (4298547)

When you right-click in any CDE application for a European locale, the CDE Extras drop-down menu does not display any options.

CTL Is Not Supported in Japanese and Asian UTF-8 Locales (4300239)

Complex Text Language (CTL) support for entering Hebrew, Arabic, or Thai has been implemented in en_US.UTF-8 and European UTF-8 locales, but is not supported in ja_JP.UTF-8, ko.UTF-8, also known as ko_KR.UTF-8, zh.UTF-8, which is also known as zh_CH.UTF-8, and zh_TW.UTF-8 locales.

Workaround: Use the en_US.UTF-8 locale if you need to enter Thai, Arabic, or Hebrew by using CTL. If you want to enter those languages in Asian and Japanese UTF-8 locales, do the following.

  1. Create a symbolic link to common CTL modules. In the instance of ja_JP.UTF-8, use the following commands.:


    	# cd /usr/lib/locale/ja_JP.UTF-8
	# mkdir LO_LTYPE ; cd LO_LTYPE
	# ln -s ../../common/LO_LTYPE/umle.layout.so.1 \
   ja_JP.UTF-8.layout.so.1
	# mkdir sparcv9 ; cd sparcv9
	# ln -s ../../../common/LO_LTYPE/sparcv9/umle.layout.so.1 \ 
   ja_JP.UTF-8.layout.so.1

  2. Edit the /usr/openwin/lib/locale/ja_JP.UTF-8/XLC_LOCALE file by commenting out the load_option delay_nocheck line from Thai, Arabic, or Hebrew entries. For example, in the Thai language, use the following.


    # fs14 class (Thai)
 	fs14    {
        charset         TIS620.2533-0:GR
        font {
            # load_option delay_nocheck  <--- comment out
            primary     TIS620.2533-0:GR
        }
}

Cannot Add, Remove, or Modify Users in Solstice AdminTool in the Greek Locale (4302983)

The Add, Modify, and Remove User screens are blank in the Greek locale of the Solstice AdminTool software.

Workaround: In superuser mode, copy the following file.


# cp /usr/openwin/lib/locale/C/app-defaults/Admin \
  /usr/openwin/lib/locale/el_GR.ISO8859-7/app-defaults/Admin
You can now add, remove, and modify user information in the Greek locale.

Font Downloader Add and Cancel Buttons Are Incorrectly Labeled in the Italian Locale (4303549)

When you are in the Italian locale and you are using the Font Downloader, both the Add and Cancel buttons in the Add Printer dialog box are incorrectly labeled. Both buttons are labeled A.

Missing Arabic Characters and Incompatibility Between the Sun Arabic Keyboard and the Microsoft Arabic Keyboard (4303879)

The following table describes the differences between the Sun Solaris Arabic keyboard and the Microsoft Arabic keyboard.

Table 2-1 Differences Between Sun and Microsoft Arabic Keyboards

Key 

Sun Keyboard Layout 

Microsoft Keyboard Layout 

T 

T 

Arabic Lam_alef with Hamza below 

U 

U 

Right single quotation mark 

I 

I 

Arabic multiplication sign 

O 

O 

Arabic division sign 

A 

; 

Arabic Kasra 

S 

S 

Arabic Kasratan 

Z 

Z 

Tilde 

X 

X 

Arabic Sukun 

C 

Arabic Kasratan 

Left curly brace 

V 

Arabic Kasra 

Right curly brace 

M 

Sukun 

Single low quotation mark 

< 

< 

Arabic comma 

Sorting in the European UTF-8 Locales Does Not Function Correctly (4307314)

Sorting in the European UTF-8 locales produces unexpected results.

Workaround: Before you attempt to sort in a FIGGS UTF-8 locale, set the LC_COLLATE variable to the ISO-1 equivalent.


# echo $LC_COLLATE
>  es_ES.UTF-8
# setenv LC_COLLATE es_ES.IS08859-1
Then start sorting.

Applications Not Fully Localized (4304495, 4306619)

The following applications are not fully localized. Some parts are not fully translated.