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 6/00 Documentation CD and in the Installation Kiosk on the Solaris 8 6/00 Installation CD.
The name of this product is Solaris 8 6/00, but code and path or package path names may use Solaris 2.8 or SunOS 5.8. Always follow the code or path as it is written.
A problem occurs when compiling a Motif program in the Solaris 8 operating environment 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 and 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 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 you have an older shared library that links directly to the Motif library, and if you want to compile a program in the Solaris 8 operating environment that links to both Motif and that older shared library, use a line like this to compile:
cc foo.c -o program -DMOTIF12_HEADERS -I/usr/openwin/include -I/usr/dt/include -lXm12 -lXt -lX11 |
If you select an item from the Options menu in dtmail, leave that window open, and then select any item from the dtmail Options menu, the CDE Workspace Manager fails.
Workaround: To correct the dtmail Options menu behavior, apply patch 109613-01 immediately after you install the Solaris 8 6/00 operating environment.
If you insert a floppy disk into a floppy disk drive on a system with SCSI removable media devices and then select Check for Floppy from the File menu in OpenWindowsTM File Manager, File Manager mounts the floppy disk in the /floppy directory, but fails to display a File Manager view listing the disk contents. The Format Floppy and Eject Floppy options do not appear in the File menu of File Manager.
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 109463-01.
Problems might occur when CDE File Manager attempts to reuse a cached Removable Media Manager file view. This can happen when you close the Removable Media Manager or when you use the Open New View from the View menu in File Manager.
The problems occur under the following conditions:
If you open a File Manager view from the CDE Front Panel after opening and closing the Removable Media Manager, File Manager fails and the following error dialog box displays:
The request to service this action has failed for the following reason: TT_ERR_PROCID The process id passwd is not valid. |
If you open a new File Manager view by selecting Open New View from the View menu after opening and closing the Removable Media Manager, File Manager quits immediately.
Workaround: Choose one of the following workarounds:
If you receive the error message listed previously, follow these steps:
Close the error dialog box.
Click on the File Manager icon in the CDE Front Panel.
File Manager will open.
If File Manager fails without displaying the error dialog box, launch File Manager in standalone mode.
% dtfile -standalone |
After deleting the last item from the desktop (for example, the last appointment in your Calendar or the last address in the Address Manager) when you synchronize the handheld device, the last entry is restored from the handheld device to the desktop.
Workaround: Delete the last entry from the handheld device.
If you exchange multibyte data between a PDA device and Solaris CDE, the data may 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.
The following error message is displayed when memory is low:
CIM_ERR_LOW_ON_MEMORY |
Workaround: To reset the CIM Object Manager Repository:
Become superuser.
Stop the CIM Object Manager.
# /etc/init.d/init.wbem stop |
Remove the JavaSpaces log directory.
# /bin/rm -rf /var/sadm/wbem/log |
Restart the CIM Object Manager.
# /etc/init.d/init.wbem start |
You will lose any proprietary definitions in your datastore. You must recompile the MOF files that contain those definitions using the mofcomp command. For example:
# /usr/sadm/bin/mofcomp -u root -p root_password your_mof_file |
If you enumerate instances of the Solaris_FileSystem class by using CIM WorkShop or the WBEM APIs, then the CIMOM no longer runs and the following error message is displayed:
Attempted to complete RMI action enumInstances and received exception java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.io.EOFException |
Workaround: In superuser mode, restart the CIMOM by typing the following command:
# /etc/init.d/init.wbem start |
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 have 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 Users Guide that is available from http://www.sun.com/solaris/netscape/jpis/usersguide_java_plugin.html.
If you run Java software in a UTF-8 locale of the Solaris 8 or Solaris 8 6/00 operating environment, the Java software may fail.
Workaround: Apply patch 108652-08 to ensure proper interaction between UTF-8 locales and Java software.
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.
If the ab2admin command fails, the error message contains additional information besides command failed. For example, it may also include path not found or invalid ID.
Workaround: If the message command failed is displayed, make sure that the operation failed. For example, if the command you submitted should have deleted a collection from the AnswerBook2 database, type the following command to verify that the collection is displayed in the database.
# ab2admin -o list |
During the startup of an AnswerBook2TM server, the ab2cd script may 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 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.
Some dead-key combinations do not work correctly in CDE. Also, names for months do not function correctly in the Calendar Manager in the Greek locale.
If you attempt to print extended characters when using 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 running under en_US.UTF-8 in Arabic input mode and one 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 using CTL. If you want to enter those languages in Asian and Japanese UTF-8 locales:
Create a symbolic link to common CTL modules. In the case of ja_JP.UTF-8:
# 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 case of Thai:
# fs14 class (Thai) fs14 { charset TIS620.2533-0:GR font { # load_option delay_nocheck <--- comment out primary TIS620.2533-0:GR }} |
The applications SmartCard, AnswerBook2, Solaris PDASync, Printer Administrator, Removable Media Manager, Graphical Workspace Manager, and Hotkey Editor are not fully localized.
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 using the Font Downloader, both the Add and Cancel buttons in the Add Printer dialog box are incorrectly labeled; they are both 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 bracket |
V |
Arabic Kasra |
Right curly bracket |
M |
Sukun |
Single low quotation mark |
< |
< |
Arabic comma |
SEAM uses some of the resource files in the Solaris 8 operating environment, but only when the Kerberos settings are selected during an installation.
The Euro currency symbol is not generated when pressing 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 does not work properly.
Workaround: Before you attempt to sort in a FIGGS UTF-8 locale, set the LC_COLLATE variable to the ISO1 equivalent.
# echo $LC_COLLATE > es_ES.UTF-8 # setenv LC_COLLATE es_ES.IS08859-1 |