This chapter describes known runtime problems. You may also want to refer to the online runtime_bugs file in the SUNWrdm package on the Solaris CD for additional runtime problems.
The information in this chapter supplements any information listed in the runtime_bugs file that is part of the SUNWrdm package on the Solaris 7 CD. If you boot from the Solaris 7 CD, the runtime_bugs file is located in the directory:
/cdrom/sol_7_x86/s2/Solaris_2.7/Docs/release_info/C
The default installed location for the runtime_bugs file is the directory:
/usr/share/release_info/Solaris_2.7/C
The name of this product is Solaris 7 but code and path or package path names may use Solaris 2.7 or SunOS 5.7. Always follow the code or path as it is written.
If you log in as root in the Arabic or Hebrew locale, you cannot add or modify users with the SolsticeTM AdminToolsTM. The Add User window is displayed but is blank. This problem occurs whenever you add or modify information about the user in all subwindows.
Workaround: Use root to add or modify information about users.
If applications are using custom fonts rather than system fonts, the XServer may crash on x86 platforms. The problem occurs because some characters in the font are exceeding the height limitation specified with the font.
Workaround: Provide an unhinted version of the offending font. The height of unhinted versions is usually lower.
If you use Arabic 16-bit proportional fonts in the Solaris 7 operating environment, the characters are only partially displayed on the screen.
Workaround: Only use monospace fonts.
Static text, such as icon text and Workspace panel text, has not been enabled for Complex Text Layout. Therefore, the Arabic and Hebrew translations of English static text do not display correctly.
OW is not supported as a desktop option in the following locales and partial locales:
Table 3-1 Desktop Options Not Supported
Desktop Option |
Name of Country |
---|---|
en_GB.ISO8859-15 |
Britain |
de.ISO8859-15 |
Germany |
fr.ISO8859-15 |
France |
it.ISO8859-15 |
Italy |
es.ISO8859-15 |
Spain |
sv.ISO8859-15 |
Sweden |
da.ISO8859-15 |
Denmark |
de_AT.ISO8859-15 |
Austria |
en_IE.ISO8859-15 |
Ireland |
pt.ISO8859-15 |
Portugal |
nl_BE.ISO8859-15 |
Belgium |
nl.ISO8859-15 |
Netherlands |
fr_BE.ISO8859-15 |
Belgium |
fi.ISO8859-15 |
Finland |
el_EURO |
Greece |
th |
Thailand |
th_TH |
Thailand |
he |
Israel |
ar |
Egypt |
de.UTF-8 |
Germany |
fr.UTF-8 |
France |
it.UTF-8 |
Italy |
es.UTF-8 |
Spain |
sv.UTF-8 |
Sweden |
en_EU.UTF-8 |
Europe |
ja_JP.UTF-8 |
Japan |
ja_JP.PCK |
Japan |
ko.UTF-8 |
Korea |
zh.GBK |
PRC |
zh_TW.BIG5 |
Taiwan |
If there are Wide Small Computer System Interface (SCSI) targets attached to the Symbios adapter but your boot device is not one of these targets, then the Solaris driver does not successfully negotiate Wide SCSI data transfer and the devices do not operate correctly.
Workaround: Set the adapter firmware to 8-bit/narrow mode using the Symbios BIOS Configuration Utility:
Enter the Symbios Configuration Utility by typing CTRL-C when prompted on boot.
From the Main Menu, select the adapter with wide targets attached.
From the Utilities Menu, choose Device Selection. Select the device and set the Width (bits) to 8.
The Solaris driver still renegotiates to the highest shared data-transfer mode, resulting in no performance loss.
JumpStart installations configured to use a Plug-and-Play monitor cannot be properly installed. The monitor information on the installed system is incomplete.
Workaround: Configure the JumpsStart installation to use a comparable multi-frequency monitor.
A security vulnerability exists in the ufsdump(1M) and ufsrestore(1M) commands. If you have already gained access to a given Solaris system, you can exploit this vulnerability to obtain root access. Fixes for these problems are available for this release by installing patch ID 106793-01, a patch for SPARC systems, or patch ID 106794-01, a patch for x86 based systems.
If you have not yet obtained and installed the appropriate patch, you can apply the following workaround on your system.
Workaround: If you use the chmod command on the ufsdump and ufsrestore programs such that the set-uid bit is removed, the programs are then no longer vulnerable. You can remove the set-uid bit by executing the following command as root:
# chmod 0555 /usr/lib/fs/ufs/ufsdump /usr/lib/fs/ufs/ufsrestore |