This chapter describes known runtime problems.
The following runtime bug descriptions have been added to this chapter since this document was published on the Solaris 8 10/01 Documentation CD and in the Installation Kiosk on the Solaris 8 10/01 Installation CD.
"USB Device Might Not Be Recognized When Hot-Plugged (4500963)"
"Audio Applications Might Stop Working After a USB Audio Device Is Hot-Unplugged (4424286)"
"Remote Display of Solaris Management Console Hangs (4488117)"
The name of this product is Solaris 8 10/01, 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.
If a system is booted without the reconfiguration option and no USB keyboard or mouse is connected, USB drivers are not automatically attached. The system will not recognize hot-plugged USB devices.
Workaround: To make the system recognize hot-plugged USB devices, choose one of the following workarounds.
Add the following line to /etc/system and reboot the system.
forceload:drv/uhci |
Type the following on a command line.
# devfsadm -i uhci |
For more information see devfsadm(1M).
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.
Become superuser.
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).
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: Powercycle the USB speakers.
If you change the authentication defaults for a smart card and the PIN authentication mechanism is not included, access to the smart card is denied. Subsequent authentication mechanisms are inaccessible and the smart card user cannot log in.
Workaround: Choose one of the following workarounds.
Do not modify the default authentication settings.
If you modify default authentication settings, you must include and configure the PIN authentication mechanism.
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.
Use rlogin to connect to the system on which the ocfserv process terminated.
Kill the dtsession process by typing the following in a terminal window.
% pkill dtsession |
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.
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.
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 view the contents of a floppy disk, follow these steps:
Click on the / folder in the File Manager Iconic Path.
Double-click on the floppy folder in the / display window.
Double-click on the floppy0 folder in the /floppy display window.
To format a floppy disk, follow these steps:
Unmount the floppy disk..
% volrmmount -e floppy0 |
Format the floppy disk.
% fdformat floppy0 |
To create a new file system on a floppy disk, follow these steps:
If you have already unmounted the floppy disk, go to step 2 of this workaround.
Unmount the floppy disk.
% volrmmount -e floppy0 |
Create the appropriate file system on the floppy disk.
To create a new UFS file system on the floppy disk, use the newfs command:
% newfs /vol/dev/aliases/floppy0 |
To create a PCFS file system on the floppy disk, use the mkfs command:
% mkfs -F pcfs /vol/dev/aliases/floppy0 |
Mount the floppy disk.
% volrmmount -i floppy0 |
To eject the floppy disk, use the eject command.
% eject floppy0 |
To prevent this problem, apply patch 109464-01.
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.
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.
When you remotely display the Solaris Management Console on the Solaris 8 7/01, or 10/01 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 10/01, operating environment. Follow these steps.
Close the hung console window.
Start the Solaris Management Console on your local system.
Select Open Toolbox from the console menu.
Click the Server Toolbox tab and select, or enter, the name of the remote system you want to manage.
Click the Open button.
You can now use the console to manage the remote system.
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.
Become superuser.
Stop the WBEM server if it is running.
# /etc/init.d/init.wbem stop |
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 |
Start the HTTP service.
# java com.sun.wbem.client.HttpService & |
Start the Common Information Model (CIM) Object Manager service.
# /usr/sadm/lib/wbem/wbemconfig & |
If a Solaris provider generates indications and the class name is set to uppercase, the event delivery fails.
Workaround: Use uppercase characters to define indication class names.
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.
After selecting Help -> Information from the Front Panel, a list of obsolete files is returned. The correct file is S8FCSreleasenotes.
The following error message is displayed when memory is low:
CIM_ERR_LOW_ON_MEMORY |
Workaround: To reset the CIM Object Manager Repository, follow these steps.
Become superuser.
Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop |
Remove the JavaSpaces log directory.
# /bin/rm -rf /var/sadm/wbem/logr |
Restart the CIM Object Manager.
# /etc/init.d/init.wbem start |
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 Plug-in 1.2 is the default plug-in that runs Java 2 applets but not all Java 1.1 applets. If you require the Java Plug-in 1.1, you can download it from http://www.sun.com/solaris/netscape.
If you choose to install both Java Plug-in 1.1 and Java Plug-in 1.2 on the same system, you must follow the instructions for how to install Java Plug-in 1.1 and then configure your environment accordingly.
This procedure is outlined in the "Installing Java Plug-in" section of the Java Plug-in for Solaris User's Guide that is available from http://www.sun.com/solaris/netscape/jpis/usersguide_java_plugin.html.
By default, the Solaris ata device driver has the DMA feature disabled for ATA/ATAPI devices.
This feature has been disabled to avoid problems on some systems that do not properly support DMA on ATA/ATAPI drives. Most of the problems are related to an outdated system BIOS.
To enable (or disable) DMA for the ata driver after an installation of the Solaris 8 operating environment, do the following.
Run the Solaris (Intel Platform Edition) Device Configuration Assistant from the boot diskette or the installation CD (if your system supports CD-ROM booting).
When you boot from the boot diskette, the new ata-dma-enabled property value is preserved on the diskette. Therefore, the changed value is in effect when you reuse the boot diskette.
Press F2_Continue to scan for devices.
Press F2_Continue to display a list of boot devices.
Press F4_Boot Tasks and select View/Edit Property Settings.
Press F2_Continue.
Change the value of the ata-dma-enabled property to 1 to enable DMA (a value of 0 disables DMA):
Select the ata-dma-enabled property from the list and press F3_Change.
Type 1 and press F2_Continue to enable (type 0 and press F2_Continue to disable).
Press F2_Back, then F3_Back to return to the Boot Solaris menu.
Select the device from which you want to install (network adapter or CD-ROM drive) and press F2_Continue.
If any problems occur after enabling DMA, disable DMA by setting the ata-dma-enabled property to 0 and using the previous procedure. Update your system with the latest BIOS from your hardware manufacturer, and then re-enable DMA.
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 |
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.
Perform the following steps to print from any non-ISO8859-1 locale by using the Font Downloader.
Log in to CDE.
Type fdl at the command line to start the Font Downloader.
Specify the printer by selecting Add from the Printer menu.
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.
The Euro is not accessible in any UTF-8 locale by using the standard key sequence ALTGr+E.
Workaround: Log in to any ISO8859-15 locale and use Alt+E to access the Euro.
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 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.
If you attempt to print extended characters when you use Calendar Manager in a partial locale, the extended characters do not print correctly.
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.
When you right-click in any CDE application for a European locale, the CDE Extras drop-down menu does not display any options.
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.
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 |
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 } } |
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 |
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.
The left button should be labeled Aggiungi (Add).
The right button should be labeled Annulla (Cancel).
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 |
The euro currency symbol is not generated when you press AltGr+E in the UTF-8 locale.
Workaround: Perform the following steps to enter the euro currency symbol in the UTF-8 locale:
Select Lookup in the UTF-8 Input Mode Selection window.
Select Currency Symbols.
Select the Euro symbol.
In the Greek locale type, dumpcs at the console prompt. Then copy and paste the euro currency symbol.
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 |
The following applications are not fully localized. Some parts are not fully translated.
Smart Card application (4304495)
SEAM application messages (4306619)