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 7/01 Documentation CD and in the Installation Kiosk on the Solaris 8 7/01 Installation CD.
The name of this product is Solaris 8 7/01, 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.
If you are running the Solaris 2.6, Solaris 7, or Solaris 8 operating environments a local or remote attacker might gain root access to the NIS domain master server. There may be no symptoms that the server has been exploited to gain unauthorized access.
Workaround: Apply one of the following patches to fix the potential security issue.
If you are running the Solaris 2.6 operating environment, apply patch 106303-03.
If you are running the Solaris 7 operating environment, apply patch 111590-02.
If you are running the Solaris 8 operating environment, apply patch 111596-02.
If a user initiates a log out and removes their smart card, but then clicks the Cancel button in the log out confirmation dialog, the screen will not lock when the smart card is removed.
Workaround: Choose one of the following workarounds.
Turn off the Logout Confirmation Dialog in the Startup Style Manager.
If the screen does not lock when the smart card is removed the user should log out and log in. The session will be restored and the screen will lock when the smart card is removed.
If you change the smart card authentication defaults 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 login.
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.
rlogin to the machine 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 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 Smart Cards Management Console. For information on smart card configuration, see Solaris Smart Cards Administration Guide.
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 |
where program is the name of the program you are compiling.
If you insert a diskette into its 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 diskette 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 diskette, 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 diskette, follow these steps:
Unmount the diskette.
% volrmmount -e floppy0 |
Format the diskette.
% fdformat floppy0 |
To create a new file system on a diskette, follow these steps:
If you have already unmounted the diskette, go to step 2 of this workaround.
Unmount the diskette.
% volrmmount -e floppy0 |
Create the appropriate file system on the diskette.
To create a new UFS file system on the diskette, use the newfs command:
% newfs /vol/dev/aliases/floppy0 |
To create a PCFS file system on the diskette, use the mkfs command:
% mkfs -F pcfs /vol/dev/aliases/floppy0 |
Mount the diskette.
% volrmmount -i floppy0 |
To eject the diskette, use the eject command.
% eject floppy0 |
To prevent this problem, apply patch 109463-01.
After deleting the last item from the desktop (for example, the last appointment in your Calendar or the last address in the Address Manager), it is restored from the handheld device to the desktop when you synchronize your handheld device.
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 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.
If the 64-bit SUNWpppdx package is installed and and you switch to 32-bit mode, pkgrm will fail when you attempt to remove SUNWpppdx. The following message is displayed.
WARNING:The <SUNWpppdu> package"Solaris PPP 4.0 daemon and utilities" depends on the package currently being removed. Dependency checking failed. Do you want to continue with the removal of this package [y,n,?,q] |
Workaround: Choose one of the following workarounds.
Answer y when pkgrm asks Do you want to continue with the removal of this package [y,n,?,q]
To remove the SUNWpppdx 64-bit package, type the following on a command line.
#pkgrm -f SUNWpppdx |
Before removing SUNWpppdx, comment out the R SUNWpppdu Solaris PPP 4.0 daemon and utilities line of /var/sadm/pkg/SUNWpppdx/install/depend
If a Solaris provider generates indications and the class name is set to uppercase, the event delivery fails.
Workaround: Use uppercase 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.
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:
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 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 |
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.
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.
kkcv is an input method server for Japanese BCP (4.x Binary Compatibility) 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 using the Languages CD.
Workaround: If you do not need to use Japanese BCP feature, configure your system not to start input method servers for BCP applications:
Copy /usr/lib/css.d/cs00.sh to /etc/css.d.
# cp -p /usr/lib/css.d/cs00.sh /etc/css.d |
Edit /etc/css.conf and comment out the line of /usr/lib/css.d with `#'.
# /etc/css.conf |
Restart the CS monitor daemon.
# sh /etc/init.d/loc.ja.cssd stop # sh /etc/init.d/loc.ja.cssd start |
The Euro is not accessible in any UTF-8 locale using the standard key sequence ALTGr+E.
Workaround: Login 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 launching a Java application from any UTF-8 locale.
Workaround: Log into 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 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 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 |
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 |
The following applications are not fully localized. Some parts will not be fully translated.
Smart Card application (4304495)
SEAM application messages (4306619)