Chapter 3 Late-Breaking Solaris Runtime Issues

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_sparc/s0/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.

Localization Bugs

Arabic 16-Bit Proportional Fonts Clip Characters (4167851)

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 Desktop Text Is Not Enabled For Complex Text Layout (4170194)

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 Some Locales

OW is not supported as a desktop option in the following locales and partial locales:

CDE Bugs

restore from sys-suspend Sometimes Does Not Restore CDE (4174133)

sys-suspend(1M) may hang and not refresh the screen on some slow systems. After a system is resumed, Screen Lock is in effect by default. This problem occurs after you enter a user password. A white screen is displayed instead of a Common Desktop Environment (CDE) screen. Although you can gain access to the system remotely, you cannot enter anything because the screen is still locked. If this problem occurs, you can recover the CDE session by remotely logging on the system as superuser and then killing the sys-suspend process.

Workaround: If this problem has occurred as a result of executing autoshutdown, use the dtpower(1M) application to disable autoshutdown. The problem does not occur if you execute sys-suspend without the Screen Lock option.

Refer to "Disabling the Screen Lock" in Using Power ManagementSolaris 7 Reference Manual Collection for a description on how to disable the Screen Lock for sys-suspend invoked by the keyboard's power key. To disable the Screen Lock for the sys-suspend command that is invoked from the CDE Workspace Menu:

1. Become superuser.

2. Create the following dtaction file /etc/dt/appconfig/types/locale/sunOW.dt. The locale is the name of the language option that is selected when you start CDE.

3. Copy the ACTION SDTsuspend { ... } definition from /usr/dt/appconfig/types/locale/sunOW.dt to /etc/dt/appconfig/types/locale/sunOW.dt.

4. Add the -x flag to sys-suspend command in the /etc/dt/appconfig/types/locale/sunOW.dt file.

5. Exit the CDE session and log in again.

File System Bugs

cpr_reset_properties: Unable to open /.cpr_default on /pci@1f,4000/scsi@3/disk@0,0 (4163575)

The above-listed message or a variation of this message may be displayed whenever you reboot after a cpr Suspend if the file system logging feature is enabled.

The cpr Suspend/Resume feature does not work with with the logging file system feature when logging is used on either the root file system or the file system chosen for the cpr state file.

The criteria for using cpr are:

• root must not be a logging file system

• The file system selected for the cpr state file (see power.conf(4)) must not be a logging file system.

Workaround: Select a file system for the cpr state file other than root or one that has logging turned on.

64-Bit Solaris Bugs

64-bit libmail Not Available (4169295)

The 64-bit libmail library is missing. You cannot create 64-bit applications that require this library.

Security Bugs

Security Vulnerability In ufsdump And ufsrestore (4132365)

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