Chapter 2 Solaris Runtime Issues

This chapter describes runtime issues that are known to be problems.

Some of the issues and bugs in this chapter have been fixed in subsequent Solaris 10 releases. If you have upgraded your Solaris software, certain issues and bugs in this chapter might no longer apply. To see which bugs and issues no longer apply to your specific Solaris 10 software, refer to Appendix A, Table of Integrated Bug Fixes in the Solaris 10 Operating System.

Common Desktop Environment

The following bugs in Solaris 10 OS apply to the Common Desktop Environment (CDE).

Trusted Stripe Crashes When Users Change Roles (6495454)

Trusted Stripe crashes when you change roles on any locale except the C locale.

Workaround: Perform any one of the following steps:

• Use the C locale.

• Remove the usr/share/locale/$locale/LC_MESSAGES/tsoljds-tstripe.mo file from the login locale.

Nautilus ACL MASK is Not in Sync With Group Permissions (6464485)

The Group permissions in the Permissions tab should be the same as the Mask permissions in the Access Tab, but on some occasions they appear out of sync.

Workaround: Click the Close button, and then click Reload. View the file properties again. The Group permissions and the Mask permissions will now be in sync again. The permissions are set to what you changed the Mask to in the previous step.

SMC CLI Commands Do Not Process the Solaris Trusted Extensions Options (6447833)

This bug affects management of Solaris^TM Trusted Extensions by using the SMC. When the SMC command line with the -B toolbox option is used to pass in the Trusted Extensions options, the command is not executed. This failed execution prevents the use of the SMC CLI to manage Solaris Trusted Extensions. The following error message is displayed:

There was an unrecognized extended, nonstandard option specified with the -x option.
Please refer to man pages for additional information and correct syntax usage

Workaround: Use the SMC GUI for administration of users, roles, and profiles.

Mouse Pointer and the dtfile Icon Are Not Displayed When You Drag the dtfile Icon (6462945)

When you drag the dtfile icon, the icon and the the mouse pointer might not be displayed. No error message is displayed.

Workaround: Add the following lines to the /usr/dt/config/<locale>/sys.resources file , under #if EXT_SUN_TS OL:

!! DragNDrop protocol. Other styles cause policy violation.
*DragInitiatorProtocolStyle:            DRAG_DYNAMIC
*DragReceiverProtocolStyle:             DRAG_DYNAMIC

SMC Updates the tnrhdb File But Does Not Run tnctl to Update the Trusted Host Cache (6471594)

When the SMC is used to manage network security templates, the /etc/s ecurity/tsol/tnrhdb file is updated but the tndb cache is not updated. Network security definitions do not take effect. No error message is displayed.

Workaround: After you modify a network entry in the SMC, manually refresh the tndb cache with one of the following commands:

• Modify an entry in the file scope:

  # /usr/sbin/tnctl -H /etc/security/tsol/tnrhdb

• Modify an entry in the LDAP scope:

  # /usr/sbin/tnctl -H <hostname>

Cannot Login Using GDM Unless Clearance is Set to admin_high (6432114)

The login fails when you log in to the Solaris Trusted Extensions Java Desktop Systems (JDS) by using GDM. This failure is caused by the PAM configuration. The pam.conf(4) file does not contain the required entries for GDM.

On login, the following error message is displayed:

The system administrator has disabled access to 
the system temporarily

Workaround: Add the following two lines to the /etc/pam.conf file:

gdm account requisite pam_roles.so.1
gdm account required pam_unix_account.so.1

For information about the file format, see the pam.conf(4) man page.

Trusted Stripe Disappears From The Screen After Resolution Change (6460624)

When you type the /usr/X11/bin/xrander -s command to set a smaller screen resolution, Trusted Stripe is no longer displayed. This affects the Trusted CDE Desktop but not the Trusted Java DS Desktop. No error message is displayed.

Workaround: After the resolution changes, restart the Workspace Manager. Select windows -> Restart Workspace Manager from the CDE workspace menu and click OK.

Secure Attention Key or Hot Key Does Not Work on x86 Systems (6486416)

The Secure Attention key or hot key, Alt+Break, on PC keyboards does not work on x86 systems. No error message is displayed.

Workaround: None.

x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card

If your Solaris 10 system has a single physical video card, you cannot configure the system for full-screen magnification. For such a configuration, you must use a separate configuration file in which you define settings for a dummy driver. First, make sure that the Xserver is not running. Then perform the following steps:

1. Log in to a command-line session.

   • If you are using the GNOME Display Manager, follow these steps:

     1. Log in to a session as superuser.

     2. At the prompt, type svcadm disable application/gdm2-login .

     3. Log in again as superuser.

   • If you are using dtlogin, follow these steps:

     1. In the dtlogin window, click Options and select Command Line Login.

     2. Log in as superuser.

2. Create a new xorg.conf file.

   # /usr/X11/bin/Xorg -configure

   The command creates the file xorg.conf.new in the root (/) directory.

3. Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.

   # cp /xorg.conf.new /etc/X11/xorg.conf

4. Modify the configurations in the file by using the following sample configurations:

   • Add a new monitor section.

     Section "Monitor" Identifier "monitor_dummy" ModelName "dummy" HorizSync 10-200 VertRefresh 20-90 EndSection

   • Add a new device section.

     Section "Device" BoardName "dummy" Driver "dummy" Identifier "device_dummy" VendorName "dummy" videoram 10000 EndSection

     ---

     Note –

     You might need to adjust the videoram value, depending on the screen width, height, and color depth of your particular graphics card. The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8.

     ---

   • Add a new screen section.

     Section "Screen" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection Device "device_dummy" Identifier "screen_dummy" Monitor "monitor_dummy" EndSection

     ---

     Note –

     You might need to adjust the resolution value for your particular system setup.

     ---

5. Look for the following line under the ServerLayout section:

   Screen 0 "Screen0" 0 0

6. Insert the following line below the line in the previous step:

   Screen 1 "screen_dummy" RightOf "Screen0"

   This new line defines Screen1, a second dummy screen that is notionally to the right of Screen0, the physical and primary screen.

7. Save the changes.

8. Reboot the system from the appropriate command-line session:

   • If you are using GDM, perform the following:

     1. Type svcadm enable application/gdm2-login.

     2. Reboot the system.

   • If you are using dtlogin, reboot the system and log in.

9. Start the Gnopernicus screen reader.

10. Change the Startup Mode to Magnifier.

11. Click Preferences, then select Magnifier.

12. Click Add/Modify.

13. Assign the following values for Magnifier preferences:

    • For Source: 0.1

    • For Zoomer Placement:

      • Left and Top: 0

      • Bottom and Right: maximum

14. Click Apply.

    Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.

x86: Problems Configuring USB Mouse Device as Extension Device for Use With GNOME On-Screen Keyboard

You cannot set up a USB mouse device as an extension device with the GNOME On-Screen Keyboard (GOK). The configuration fails when you are setting up the USB mouse device while using a PS2 mouse device as the core pointer. To properly set up the USB mouse, follow these steps.

1. Log in as superuser.

2. While the USB mouse device is unplugged, type the following in a terminal window:

   # ls -l /dev/usb/hid*

3. Connect the USB mouse and type the previous command again.

4. Record the path of the USB mouse that is displayed on the screen.

5. Log in to a command-line session.

   • If you are using the GNOME Display Manager, follow these steps:

     1. Log in to a session as superuser.

     2. At the prompt, type svcadm disable application/gdm2-login.

     3. Log in again as superuser.

   • If you are using dtlogin, follow these steps:

     1. In the dtlogin window, click Options and select Command Line Login.

     2. Log in as superuser.

6. Create a new xorg.conf file.

   # /usr/X11/bin/Xorg -configure

   The command creates the file xorg.conf.new in the root (/) directory.

7. Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.

   # cp /xorg.conf.new /etc/X11/xorg.conf

8. Modify the configurations in the file:

   • In the ServerLayout section, add an input device for Mouse1 after the line InputDevice "Mouse0" "CorePointer". See the following example:

     InputDevice "Mouse0" "CorePointer" InputDevice "Mouse1"

   • In the InputDevice section that contains the line Identifier "Mouse0", apply the following changes:

     • Change Option "Device" "/dev/mouse" to Option "Device" "/dev/kdmouse".

     • Change Option "Protocol" "auto" to Option "Protocol" "VUID".

     • Add the following new Option:

       Option "StreamsModule" "vuid3ps2"

     After you have applied the changes, the section should appear similar to the following example:

     Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "VUID" Option "Device" "/dev/kdmouse" Option "StreamsModule" "vuid3ps2" EndSection

   • Create a new InputDevice section after the preceding InputDevice section:

     Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Device" "/dev/usb/hid1" EndSection

     ---

     Note –

     /dev/usb/hid1 is an example path for the USB mouse. Use the path in Step 4 to replace /dev/usb/hid1.

     ---

9. Save the file and exit.

10. Reboot the system from the appropriate command-line session:

    • If you are using GDM, perform the following:

      1. Type svcadm enable application/gdm2-login.

      2. Reboot the system.

    • If you are using dtlogin, reboot the system.

11. Log in to the accessible UI user's account.

12. Enable Assistive Technology Support by clicking Launch Menu => Preferences => Accessibility => Assistive Technology Support.

13. Log out of the system then log in to the accessible UI user's account again.

14. Open a terminal window and type the following command:

    % /usr/sfw/bin/gok --select-action=switch1

15. In the GOK window, click GOK and select Preferences.

16. If necessary, set up GOK to the accessible UI user's needs. Otherwise, to accept the current setup, click Apply then click OK in the GOK Preferences window.

17. Exit GOK and then restart it by clicking Launch Menu => Applications => Accessibility => On-Screen Keyboard. The following warning message might be displayed:

    The device you are using to control GOK is also controlling the system pointer.

18. Click OK.

19. Exit GOK and then repeat steps 14-17.

    The warning message is no longer displayed.

x86: Support for Intel Integrated i810 and i815 Graphics Chipsets

Intel Integrated i810 and i815 Graphics Chipsets are not supported by the Xorg X Window System server. Support is available with the Xsun server. To configure the Xsun server to use these chipsets, follow these steps:

1. Become superuser.

2. Run the program to configure keyboard, display, and mouse.

   # kdmconfig

3. On the Introduction and X Server Selection screen, select the Xsun server.

   On the View and Edit Window System Configuration screen, Intel i810/i815 (4MB) should be automatically selected and displayed as the Video Device.

4. If the Intel i810 and i815 Chipsets are not automatically selected, select the Change Video Device/Monitor option.

5. On the Video Device Selection screen, select the Intel i810/i815 (4MB) option.

6. Continue to select other kdmconfig options.

x86: GNOME Applications Fail With dtremote (6278039)

GNOME applications do not start if you log in remotely and enable accessibility in gnome-at-properties. If you attempt to start a GNOME application, the following error message is displayed:

** ERROR **: Accessibility app error:
 exception during registry activation from id:
 IDL:Bonobo/GeneralError:1.0
  aborting...

Workaround: None. Do not enable accessibility when you log in by using dtremote.

To revert to the default desktop settings in which accessibility is disabled, close the GNOME session. Issue the following command:

% gnome-cleanup

Full-Screen Magnification and Keyboard Accessibility Features Not Working (6273030)

On your Java Desktop System software, you cannot set up the following:

• Full-screen magnification

• Keyboard accessibility features

Workaround: Perform the following steps:

1. Open the /etc/X11/gdm/gdm.conf file.

2. Depending on your system's platform, perform the following:

   • On SPARC based systems:

     1. Look for the line in the file that begins as follows:

        command=/usr/openwin/bin/Xsun

     2. Append the following modification to the line:

        +kb +accessx -dev framebuffer1 -dev framebuffer2

        For example:

        +kb +accessx -dev /dev/fbs/pfb1 -dev /dev/fbs/pfb0

   • On x86 based systems:

     1. Look for the line in the file that begins as follows:

        command=/usr/X11R6/bin/Xorg

     2. Append the following modification to the line:

        +kb +accessx

x86: kdmconfig Command Does Not Create System Identification Configuration File for Xorg X Server (6217442)

If you use the JumpStart installation method, the process might use a system identification configuration (sysidcfg) file. This file is used to generate a specific Xsun configuration file for a system. The Xsun configuration portion of a sysidcfg file is created by the command kdmconfig -d filename. However, on systems that use the default Xorg server, the command does not create a file with any Xorg configuration information. Consequently, you cannot use the JumpStart method on these systems without some additional preparatory steps.

Workaround: Before using the JumpStart installation method on a system that uses the Xorg server, perform the following steps.

1. Prepare a specific xorg.conf file to be used on the system. Store this file in the JumpStart directory of the JumpStart server.

   For instructions to create an xorg.conf file and to access Xorg information, see x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669).

2. Create a finish script that copies the xorg.conf file to the /etc/X11 directory in the system that you want to install. For example, the script might include the following line:

   cp ${SI_CONFIG_DIR}/xorg.conf /etc/X11/Xorg.conf

3. In the custom JumpStart rules file, include the finish script in the rules entry for systems of the type that you want to install.

4. Perform the custom JumpStart installation.

For instructions about how to perform a custom JumpStart installation, see the Solaris 10 11/06 Installation Guide: Custom JumpStart and Advanced Installations. Chapter 4 includes information about the JumpStart rules file, while Chapter 5 contains a section about finish scripts.

x86: kdmconfig Instructions to Configure Xorg X Server Are Incomplete (6205881)

Instructions that are provided in the kdmconfig program to configure the Xorg server are incomplete. The program lists basic instructions to generate an xorg.conf file. However, some relevant information is unavailable. For example, options in the xorg.conf file can be overridden in several places:

• Command-line options

• Information that is detected by the Xorg server when the server starts

• The startup scripts for the Xorg server, which might include passing overriding arguments

Thus, for more information about Xorg configuration, refer to the following sources:

• Xorg(1x) man page in the /usr/X11/man directory

• Man pages for the desktop systems that use the X server, such as the following:

  • dtlogin(1X) in the /usr/dt/man directory

  • gdm(1) in the /usr/share/man directory

If these directories are not in your man path, use one of these options:

• Add the directory to the MANPATH environment variable setting.

• Use the -M directory option of the man command.

Some scripts that start the Xorg server use smf(5) repository properties. In particular, the FMRI svc:/applications/x11/x11-server is used for storing X server properties. The following properties are relevant to the Xorg server:

• options/xserver

• options/default_depth

• options/server_args

You can set and retrieve these properties by becoming superuser and using the svccfg command, as shown in the following example:

# svccfg 
svc:> select application/x11/x11-server 
svc:/application/x11/x11-server> listprop options/default_depth 
options/default_depth integer 24


 
svc:/application/x11/x11-server> setprop options/default_depth = 8 
svc:/application/x11/x11-server> listprop options/default_depth 
options/default_depth integer 8


 
svc:/application/x11/x11-server> end
#

x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669)

In this current Solaris 10 release, the default X server has changed from Xsun to Xorg. The program that configures keyboard, display, and mouse ( kdmconfig ) applies only to the Xsun server. The program has no effect on Xorg server configuration. Consequently, you cannot use kdmconfig to configure the Xorg server. While kdmconfig allows you to select which server to use, kdmconfig only configures the Xsun server.

Workaround: To configure the Xorg server, perform the following steps:

1. Create an xorg.conf file with one of these commands:

   • /usr/X11/bin/Xorg -configure

   • /usr/X11/bin/xorgconfig

   • /usr/X11/bin/xorgcfg

2. Edit the resultant xorg.conf file with the necessary changes.

3. Move the xorg.conf file to /etc/X11/xorg.conf.

For more details about Xorg configuration, refer to the Xorg man pages in /usr/X11/man. This directory is not in the default man page path. To view these man pages, use one of the following options:

• Add the path to the settings of the environment variable MANPATH .

• Use the syntax man -M /usr/X11/man.

Xorg command line options can override xorg.conf settings. See the man pages for more details about options to use with Xorg.

CDE Removable Media Auto Run Capability Removed (4634260)

The Removable Media auto run capability in the CDE desktop environment has been temporarily removed from the Solaris 10 software.

Workaround: To use the auto run function for a CD-ROM or another removable media volume, you must do one of the following:

• Run the volstart program from the top level of the removable media file system.

• Follow the instructions that are included with the CD for access from outside of CDE.

Solaris PDASync Cannot Delete Last Entry From the Desktop (4260435)

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 then 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.

Documentation DVD

The following Documentation DVD bugs apply to the Solaris 10 release.

SUNWsdocs Package Needed to Remove Other Documentation Packages

If you remove the SUNWsdocs package, then try to remove other documentation packages, the removal fails. This problem occurs because the SUNWsdocs package is installed with any collection and provides the browser entry point.

Workaround: If you removed the SUNWsdocs package, reinstall the SUNWsdocs package from the documentation media and then remove the other documentation packages.

European Locale PDF Documents Available Only Through C Locale (4674475)

On systems that are running the current Solaris 10 release, PDF documents on the Solaris 10 Documentation DVD are not accessible in the following European locales:

• de (German)

• es (Spanish)

• fr (French)

• it (Italian)

• sv (Swedish)

Workaround: Choose one of the following workarounds.

• On x86 based platforms, set the environment variable LC_ALL to C acroread. For example, in the C shell, type the following command in a terminal window:

  % env LC_ALL=C acroread

• On SPARC based systems, upgrade to Adobe Acrobat Reader 5.0 or a later version.

File Systems

The following file system bugs apply to the Solaris 10 release.

Overlapping Devices Might be Added to a ZFS Storage Pool (6414648)

Using the zpool add command might inadvertently add identical devices and might lead to data corruption. No error message is displayed.

Workaround: If a ZFS storage pool with identical devices is created, remove the pool and recreate the storage pool.

zoneadm install Fails With a ZFS Legacy Mount (6449301)

If a non-global zone is initially configured with a ZFS file system to be mounted with the `add fs subcommand and specifies mountpoint=legacy, the subsequent zone installation fails. The following error message is displayed.

ERROR: No such file or directory:
cannot mount </zones/path/root/usr/local> in non-global zone to install:
the source block device or directory </path/local> cannot be accessed

Workaround: Add access to a ZFS file system after installing the non-global zone.

zpool Scrubbing Leads to Memory Exhaustion and a System Hang (6456888)

A zpool scrub or resilver operation of large amounts of data might lead to a system hang or panic. No error message is displayed.

Workaround: If the system hangs or panics, perform the following steps:

1. Reboot the system.

2. Continue the resilver or scrub operation.

3. Do not stress the system with additional load until the resilver or scrub operation completes.

ZFS and UNIX/POSIX Compliance Issues

ZFS is designed to be a POSIX compliant file system and in most situations, ZFS is POSIX compliant. However, two edge case conditions exist when ZFS does not meet the POSIX compliance tests:

1. Updating ZFS files system capacity statistics.

2. Modifying existing data with a 100 percent full file system.

Related CRs:

• 6362314

• 6362156

• 6361650

• 6343113

• 6343039

Adding ZFS Patch to a Solaris 10 11/06 System Causes Spurious Warning Messages (6429860)

Adding ZFS patches to a Solaris 10 11/06 system causes spurious warning messages from the patchadd command because the ZFS packages are being added to the system for the first time. The following error message is displayed:

The following requested patches have packages not installed on the system:
	Package SUNWzfskr from directory SUNWzfskr in patch 122641-03 
	is not installed on the system.

	Changes for package SUNWzfskr will not be applied to the system.

Workaround:

Ignore the spurious messages from the patchadd command.

fdisk -E Can Sweep Disk Used by ZFS Without Warning (6412771)

If you use the fdisk -E command to modify a disk that is used by a ZFS storage pool, the pool becomes unusable and might cause an I/O failure or system panic.

Workaround:

Do not use the fdisk command to modify a disk that is used by a ZFS storage pool. If you need to access a disk that is used by a ZFS storage pool, use the format utility. In general, disks that are in use by file systems should not be modified.

ZFS and Third-Party Backup Product Issues

The following are the issues with the Veritas NetBackup and Brightstor ARCserve Backup products.

Veritas NetBackup Does Not Back Up and Preserve Files With ZFS/NFSv4 ACLs (6352899)

The Veritas NetBackup product can be used to back up ZFS files, and this configuration is supported. However, this product does not currently support backing up or restoring NFSv4-style ACL information from ZFS files. Traditional permission bits and other file attributes are correctly backed up and restored.

If a user tries to back up or restore ZFS files, the NFSv4-style ACL information from ZFS files is silently dropped. There is no error message indicating that the ACL information from ZFS files has been dropped.

Support for ZFS/NFSv4 ACLs is under development and is expected to be available in the next Veritas NetBackup release.

Workaround 1:

As of the Solaris 10 11/06 release, both the tar and cpio commands correctly handle ZFS files with NFSv4-style ACLs.

Use the tar command with the -p option or the cpiocommand with the -P option to write the ZFS files to a file. Then, use the Veritas NetBackup to back up the tar or cpio archive.

Workaround 2:

As an alternative to using Veritas NetBackup, use the ZFS send and receive commands to back up ZFS files. These commands correctly handle all attributes of ZFS files.

BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support

The BrightStor ARCserve Backup (BAB) Client Agent for UNIX (Solaris) can be used to backup and restore ZFS files.

However, ZFS NFSv4-style ACLs are not preserved during backup. Traditional UNIX file permissions and attributes are preserved.

Workaround: If you want to preserve ZFS files with NFSv4-style ACLs, use the tar command with the -p option or the cpio command with the -P option to write the ZFS files to a file. Then, use BAB to backup the tar or cpio archive.

ZFS GUI Should Check For /usr/lib/embedded_su at the Beginning of Each Wizard (6326334)

If you add the SUNWzfsg package from a Solaris 10 11/06 release to a system that runs a pre-Solaris 10 6/06 release, which does not have the embedded_su patch, the ZFS Administration application wizards are not fully functional.

If you attempt to run the ZFS Administration application on a system without the embedded_su patch, you will only be able to browse your ZFS configuration. The following error message is displayed:

/usr/lib/embedded_su: not found

Workaround:

Add the embedded_su patch (119574-02) to the system that runs a pre-Solaris 10 6/06 release.

Fails to Sync File System on Panic (6250422)

If a host panics with file system I/O occurring to a target, which is connected by using the Solaris iSCSI software initiator, the I/O might not be able to flush or sync to the target device. This inability to flush or sync might cause file system corruption. No error message is displayed.

Workaround:

Use the journaling file system like UFS. Starting with Solaris 10, UFS logging is enabled by default. For more information about UFS, see What’s New in File Systems in the Solaris 10 Release? in System Administration Guide: Devices and File Systems.

Need Itinerary so That Interrupted scrub or resilverDoesn't Have to Restart (2136811)

If a ZFS snapshot is created while a data scrub or resilver operation is in progress, the scrub or resilver operation will restart from the beginning. If snapshots are taken frequently, the scrub or resilver operation might never complete.

Workaround:

Do not take snapshots while a scrub or resilver operation is in progress.

Upgrading From Some Solaris Express or Solaris 10 Releases Requires Remounting of File Systems

After you upgrade an NFSv4 server from 6/05 to Solaris Express 7/05 or later (including all Solaris 10 updates), your programs might encounter EACCES errors. Furthermore, directories might erroneously appear to be empty.

To prevent these errors, unmount and then remount the client file systems. In case unmounting fails, you might need to forcibly unmount the file system by using umount -f. Alternatively, you can also reboot the client.

NFSv4 Access Control List Functions Might Work Incorrectly

NFSv4 Access Control List (ACL) functions might work improperly if clients and servers in the network are installed with different previous Solaris 10 releases. The affected ACL functions and command-line utilities that use these functions are the following:

• acl()

• facl()

• getfacl

• setfacl

For more information about these functions and utilities, see their respective man pages.

For example, errors might be observed in a network that includes the following configuration:

• A client that is running Solaris 10 Beta software

• A server that is running Solaris 10 software

The following table illustrates the results of the ACL functions in client-server configurations with different Solaris 10 releases.

Workaround: For the NFSv4 ACL functionality to work properly, perform a full installation of the Solaris 10 OS on both the server and the client.

Access Problems Between Solaris NFSv4 Clients and NFSv4 Servers

In the current Solaris 10 version, Solaris implementation of NFSv4 Access Control Lists (ACL) is now compliant with RFC 3530 specifications. However, errors occur for NFSv4 clients that use the Solaris 10 Beta 2 or Beta 1 versions. These clients cannot create files in the NFSv4 servers that are using the current Solaris 10 release. The following error message is displayed:

NFS getacl failed for server_name: error 9 (RPC: Program/version mismatch)

Workaround: None.

Using mkfs Command to Create File System Might Fail on Very Large Disks (6352813)

The mkfs command might be unable to create a file system on disks with a certain disk geometry and whose sizes are greater than 8 Gbytes. The derived cylinder group size is too large for the 1-Kbyte fragment. The large size of the cylinder group means that the excess metadata cannot be accommodated in a block.

The following error message is displayed:

With 15625 sectors per cylinder, minimum cylinders
per group is 16. This requires the fragment size to be
changed from 1024 to 4096.
Please re-run mkfs with corrected parameters.

Workaround: Use the newfs command instead. Or, assign a larger fragment size, such as 4096, when you use the mkfs command.

File System Creation Might Fail on Small Slices (6346510)

Creating a UFS file system with the newfs command might fail under the following conditions:

• The size of the slice is small, approximately less than 4 Mbytes.

• The size of the disk exceeds 8 Gbytes.

The error is caused by the large-size requirement of the file system for metadata. The following warning message is displayed:

Warning: inode blocks/cyl group (295) >= data blocks (294) in last
     cylinder group. This implies 4712 sector(s) cannot be allocated.
/dev/rdsk/c0t0d0s6:     0 sectors in 0 cylinders of 48 tracks, 128 sectors
         0.0MB in 0 cyl groups (13 c/g, 39.00MB/g, 18624 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
#

Workaround: As superuser, perform one of the following workarounds:

• Workaround 1: Specify the number of tracks when you use the newfs command. Follow these steps.

  1. Use the format command to find out the number of tracks to assign. For example:

     # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> /pci@1f,4000/scsi@3/sd@0,0 Specify disk (enter its number):

     In the example, the number of tracks is 19.

  2. Assign the number to the file system that you create with the newfs command. For example:

     # newfs -v -t 19 /dev/dsk/c0t0d0s6 newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y mkfs -F ufs /dev/rdsk/c0t0d0s6 4712 -1 19 8192 1024 16 10 167 2048 t 0 -1 8 128 n mkfs: bad value for nsect: -1 must be between 1 and 32768 mkfs: nsect reset to default 32 Warning: 152 sector(s) in last cylinder unallocated /dev/rdsk/c0t0d0s6: 4712 sectors in 8 cylinders of 19 tracks, 32 sectors 2.3MB in 1 cyl groups (16 c/g, 4.75MB/g, 2304 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, #

• Workaround 2: Specify the number of bytes per inode (nbpi) in the newfs command to reduce the inode density in the file system. For example:

  # newfs -i 4096 /dev/dsk/c0t0d0s6 newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y Warning: 1432 sector(s) in last cylinder unallocated /dev/rdsk/c0t0d0s6: 4712 sectors in 1 cylinders of 48 tracks, 128 sectors 2.3MB in 1 cyl groups (16 c/g, 48.00MB/g, 11648 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, #

System Crash Dump Fails on Devices Greater Than 1 TByte (6214480)

The system cannot generate a dump on a partition that is equal to or greater than 1 Tbyte in size. If such a device is on a system, the following might occur after the system boots subsequent to a system panic:

• The system does not save the dump.

• The following message is displayed:

  0% done: 0 pages dumped, compression ratio 0.00, dump failed: error 6

Workaround: Configure the size of your system's dump device to less than 1 Tbyte.

Using smosservice Command to Add OS Services Results in Insufficient Disk Space Message (5073840)

If you use the smosservice command to add OS services to a UFS file system, a message that there is insufficient disk space available is displayed. This error is specific to UFS file systems on EFI-labeled disks.

Workaround: Complete the following workaround.

1. Apply the SMI VTOC disk label.

2. Re-create the file system.

3. Rerun the smosservice command.

Hardware–Related Issue and Bugs

The following hardware–related issue and bugs apply to the Solaris 10 release.

Japanese 106 keyboard Cannot Be Set Through kdmconfig (6463842)

If the Japanese 106 keyboard is attached to the system and the keyboard type Japanese-106/type7 is selected on kdmconfig, the U.S. layout will be applied to the system after reboot. No error message is displayed.

Workaround: Set the kbd-type by running the eeprom command:

# eeprom kbd-type='Japanese(106)'

Reboot the system.

SPARC: DR: cfgadm -c configure Command Fails on Slot of Starcat and Silverstone (6452077)

This bug affects all existing PCI platforms with hot-pluggable slots when the customer tries to hot-plug and configure a card making a 64-bit MEM request, for example, the Crystal 2R Fibre Channel card.

No error message is displayed. However, the configuration fails and the card is not usable.

Workaround: None. Reboot the system with the card inserted in the slot, and the card is configured and ready for operation.

mpathadm Does Not Display Load-Balance Setting Specific to Device

The mpathadm show logical-unit subcommand lists the load balancing global configuration value for the Current Load Balance property. However, entries in the csi_vhci.conf that change the load-balance type for a specific product are not reflected in the mpathadm output even when the setting is active.

Registration Tool Prevents Power Management on Some Framebuffers (6321362)

If the background processes for the registration tool are left running, the Elite3D and Creator3D framebuffers stop power management. This failure reduces the power savings when the system is in a power-managed state. Under certain conditions, sys-suspend might also hang. No error message is displayed. The system might hang during a system suspend or resume operation.

Workaround:

Run the following command approximately 60 seconds after each login:

# pkill -f basicreg.jar
# pkill -f swupna.jar

SPARC: Sun Crypto Accelerator 4000 Board Versions 1.0 and 1.1 Not Supported in Solaris 10 OS

A new cryptographic framework is provided in Solaris 10 OS. However, versions 1.0 and 1.1 of the Sun Crypto Accelerator 4000 board's software and firmware do not utilize this framework. Consequently, these versions are not supported in the Solaris 10 OS.

The 2.0 release uses the new framework. This release is available as a free upgrade to current Sun Crypto Accelerator 4000 users who plan to use Solaris 10 OS. Because the Sun Crypto Accelerator 4000 is an export-controlled product, you must contact Sun Enterprise Services or your local sales channel to obtain the free upgrade. Additional information is available on the Sun Crypto Accelerator 4000 web page at Sun's products site.

Certain USB 2.0 Controllers Are Disabled

Support for certain USB 2.0 controllers has been disabled because of incompatibilities between these devices and the EHCI driver. The following message is displayed:

Due to recently discovered incompatibilities with this 
USB controller, USB2.x transfer support has been disabled. 
This device will continue to function as a USB1.x controller. 
If you are interested in enabling USB2.x support please refer 
to the ehci(7D) man page. 
Please refer to www.sun.com/io for Solaris Ready products 
and to www.sun.com/bigadmin/hcl for additional compatible 
USB products.

For the latest information about USB devices, see http://www.sun.com/io_technologies/USB-Faq.html.

Supported USB Devices and Corresponding Hub Configurations

This Solaris release supports both USB 1.1 and USB 2.0 devices. The following table is a summary of USB devices that work in specific configurations. Connection types can either be direct to the computer or through a USB hub. Note that USB 1.1 devices and hubs are low speed or full speed. USB 2.0 devices and hubs are high speed. For details about ports and speeds of operation, see the System Administration Guide: Devices and File Systems.

x86: Limitations Exist With Certain Device Drivers in Solaris 10 OS

The following list describes limitations with certain drivers and interfaces in this release of Solaris 10 for x86 platforms:

Checkpoint Resume

This functionality is turned off for all device types. In the DDI_SUSPEND code in your detach() function, you should return DDI_FAILURE.

Power Management

This functionality is unavailable to USB devices. Do not create power management components. Write your driver so that pm_raise_power() and pm_lower_power() are called only when power management components are created.

DVD-ROM/CD-ROM Drives on Headless Systems

Power management of interactive devices such as removable media is linked with power management of your monitor and the graphics card that drives your monitor. If your screen is active, devices such as the CD-ROM drive and diskette remain at full-power mode. These devices might switch to low-power mode on a system without a monitor. To restore power to the CD or diskette, type volcheck to obtain the latest status from each removable device.

Alternatively, you can disable power management on your system by using the Dtpower GUI. By disabling power management, these devices are constantly at full power.

x86: Manual Configuration Required to Specify Non-US English Keyboards

By default, the kdmconfig program specifies Generic US-English(104-Key) as the keyboard type that is connected to the system. If the system's keyboard is not a US-English keyboard, you must manually specify the keyboard type during installation. Otherwise, installation continues by using the default keyboard specification that is inconsistent with the system's actual keyboard type.

Workaround 1: If the system's keyboard is not a US-English keyboard, perform the following steps during installation:

1. When the Proposed Window System Configuration For Installation is displayed, press Esc.

   ---

   Note –

   The information on the Proposed Window System Configuration For Installation, which includes the keyboard type, is displayed only for 30 seconds. If you want to change configuration settings, you must press Esc before the 30 seconds lapse. Otherwise, the installation continues by using the displayed settings.

   ---

2. Change the keyboard type to the type that corresponds to your system's keyboard.

3. Press Enter to accept the changes and continue with the installation.

Workaround 2: If you want to change the keyboard type in a system that is already running Solaris 10 OS, use the kdmconfig program. Choose the option that applies to the type of X server your system is running.

• If your system is running the Xsun server, follow these steps:

  1. Run kdmconfig.

  2. Use the Change Keyboard option to change the keyboard type.

  3. Save the configuration.

• If your system is running the default Xorg server, follow these steps:

  1. Run kdmconfig.

  2. Select the Xsun server.

  3. Use the Change Keyboard option to change the keyboard type.

  4. Save the configuration.

  5. Run kdmconfig again to switch to the Xorg server.

SPARC: Power Management in Sun Expert3D and Sun Elite3D Hardware Not Working Under Certain Circumstances (6321362)

Sun Expert3D or Sun Elite3D cards in Sun Blade^TM 1000 or Sun Blade 2000 workstations normally switch to low-power mode after an idle period. However, if these cards are set as the primary head in the Xserver, power management does not work. The affected cards remain at full power and no power savings are realized. No error message is displayed.

Workaround: None.

SPARC: jfca Driver for Certain Host Bus Adapters That Are Connected to Tape Devices Might Cause Errors (6210240)

The jfca driver for the following host bus adapters (HBAs) might cause system panics or I/O failures when these HBAs are connected to tape devices:

• SG-PCI1FC-JF2

• SG-PCI2FC-JF2

The jfca driver for these HBAs is prone to race conditions when certain operations are being run, and thus causes the errors. The operations are the following:

• Link reset

• Loop reset

• Switch reset

• Repeated link failures

Error messages similar to the following examples might be displayed:

• I/O failure messages

  jfca: [ID 277337 kern.info] jfca4: Sequencer-detected error. Recover immediately. last message repeated 18376 times jfca: [ID 716917 kern.notice] jfca4: ExgWarning: SendVerify(1): SHOULD ABORT THE ORIG I/O PKG=30007520bd8! scsi: [ID 107833 kern.warning] WARNING: /pci@1e,600000/SUNW,jfca@3,1/fp@0,0/st@w2100001086108 628,1 (st3): SCSI transport failed: reason 'timeout': giving up

• System panic message

  panic[cpu1]/thread=2a100497cc0: BAD TRAP: type=31 rp=2a1004978d0 addr=a8 mmu_fsr=0 occurred in module "jfca" due to a NULL pointer dereference

Workaround: Do not connect tape devices to either the SG-PCI1FC-JF2 or SG-PCI2FC-JF2 HBA.

Contention Exists Between Certain Devices That Share the Same Bus (6196994)

A bus contention occurs if Quad Fast-Ethernet (QFE) cards share the same bus with any of the following adapters:

• Sun GigaSwift adapter

• Sun Dual Gigabit Ethernet and Dual SCSI/P adapter

• Sun Quad Gigaswift Ethernet adapter

The infinite-burst parameter of the ce driver that is used by these adapters is enabled by default. Consequently, little or no bus time is available for the QFE ports that share the same bus.

Workaround: Do not place QFE cards on the same bus as the network adapters in the list.

hat_getkpfnum() DDI Function Is Obsolete (5046984)

The hat_getkpfnum() DDI function is obsolete. Developers should update their device drivers to not use the hat_getkpfnum() DDI interface. If drivers are using hat_getkpfnum,() warnings similar to the following example are displayed:

WARNING: Module mydrv is using the obsolete hat_getkpfnum(9F)
interface in a way that will not be supported in
a future release of Solaris. Please contact the
vendor that supplied the module for assistance,
or consult the Writing Device Drivers guide,
available from http://www.sun.com for migration
advice.
---
Callstack of bad caller:
       hat_getkpfnum_badcall+93
       hat_getkpfnum+6e
       mydrv_setup_tx_ring+2d
       mydrv_do_attach+84
       mydrv_attach+242
       devi_attach+6f
       attach_node+62
       i_ndi_config_node+82
       i_ddi_attachchild+4a
       devi_attach_node+4b
       devi_attach_children+57
       config_immediate_children+6e
       devi_config_common+77
       mt_config_thread+8b

To determine if a driver is using hat_getkpfnum(), consult the driver source code, or examine the driver's symbols by using nm(). Using the driver mydrv as an example, type the following syntax:

% nm /usr/kernel/drv/mydrv | grep hat_getkpfnum

For guidance about migrating drivers away from hat_getkpfnum(), refer to Appendix B, Summary of Solaris DDI/DKI Services, in Writing Device Drivers.

x86: Using Two Adaptec SCSI Card 39320D Cards on a Sun Fire V65x Server Might Cause the System to Panic (5001908)

Using two Adaptec SCSI Card 39320D cards on a Sun Fire V65x server might cause that system to panic. The panic occurs during initial reboot after you have installed Solaris 10 software. The following error message is displayed:

Initializing system  Please wait... 
1 run-time error M6111: MATH
	- floating-point error: stack underflow

Workaround: Remove the second Adaptec card.

x86: Soft System-Shutdown is Not Supported in Solaris OS on x86 (4873161, 5043369)

The Solaris OS on x86 does not support a soft system-shutdown that is initiated by a command. A command to shut down simulates pressing the power button to turn the power off. On x86-based systems, issuing this command while the Solaris OS is running turns the power off immediately without properly shutting down the operating system. The improper shutdown process might corrupt the file system.

Workaround: Before powering off, shut down the operating system first. Perform the following steps:

1. Become superuser.

2. Use one of the available commands to shut down the Solaris OS properly, such as init, halt, or shutdown. For example:

   # shutdown

3. After the operating system shuts down completely, you can switch off the power by one of two ways:

   • If the system supports soft system-shutdown, issue the command to turn off the power.

   • If the system does not support soft system-shutdown, turn off the power manually by using the power switch.

For more information about the commands to shut down the operating system, see the man pages for the init(1M), halt(1M), and shutdown(1M) commands. For information about turning off your system's power, refer to the system's manuals.

Some DVD and CD-ROM Drives Fail to Boot Solaris (4397457)

The default timeout value for the SCSI portion of the SunSwift^TM PCI Ethernet/SCSI host adapter (X1032A) card does not meet the timeout requirements of Sun's SCSI DVD-ROM drive (X6168A). With marginal media, the DVD-ROM occasionally experiences timeout errors. The only exceptions are Sun Fire 6800, 4810, 4800, and 3800 systems. These systems overwrite the SCSI timeout value by means of OpenBoot PROM.

Workaround: For other platforms, use the on-board SCSI interfaces or DVD-ROM compatible SCSI adapters, such as the following examples:

• X1018A (SBus: F501-2739-xx)

• X6540A (PCI: F375-0005-xx)

iPlanet Directory Server 5.1 Issues

This section provides important information for users of iPlanet^TM Directory Server 5.1 who are upgrading to the new Solaris 10 release.

Installing Directory Server 5.1

Sun Java System Directory Server 5 2005Q1 replaces iPlanet Directory Server 5.1 that was integrated in the Solaris 9 Operating System. In Solaris 10 OS, this new Directory Server can be installed as part of the Sun Java Enterprise System.

For information about the Sun Java System Directory Server 5 2005Q1, refer to the documentation for the Sun Java System at http://docs.sun.com.

Solaris 10 OS continues to support Directory Server 5.1. You might need to install Directory Server 5.1 under the following circumstances:

• You need to recover Directory Server 5.1 data.

• You want to migrate your data to Directory Server 5 2005Q1.

In Solaris 10 release, you install the Directory Server 5.1 manually. Follow these steps:

1. Insert the Solaris 10 Software - 4 CD into your CD-ROM drive.

2. Become superuser.

3. In a terminal window, install the Directory Server.

   # cd /cdrom/cdrom0/Solaris_10/Product/ # pkgadd -d . IPLTnls IPLTnspr IPLTnss IPLTjss IPLTpldap \ IPLTdsr IPLTdsu IPLTadmin IPLTcons IPLTadcon IPLTdscon \ IPLTadman IPLTdsman

   To install Simplified Chinese localization packages, issue the following additional command:

   # pkgadd -d . IPLTcdsu IPLTcadmin IPLTccons IPLTcadcon \ IPLTcdscon IPLTcadman IPLTcdsman

   To install Japanese localization packages, issue the following additional command:

   # pkgadd -d . IPLTjdsu IPLTjadmin IPLTjcons IPLTjadcon \ IPLTjdscon IPLTjadman IPLTjdsman

4. After installation is complete, configure iPlanet Directory Server 5.1. Refer to Chapter 11, Sun ONE Directory Server Configuration, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) .

Migrating to the Sun Java System Directory Server 5 2005Q1

The database formats of the two Directory Server versions are incompatible. Thus, if you are a Directory Server 5.1 user, Sun recommends that you migrate your database to a database that is formatted for the Sun Java System Directory Server 5 2005Q1.

To perform a migration, both versions of the Directory Server must exist in the system that has been upgraded to the Solaris 10 OS. If you are a DS 5.1 user, but are using the compressed archive (.tar.gz) delivery format, you can skip immediately to the migration instructions in Step 2.

1. On a terminal window, check whether iPlanet Directory Server 5.1 packages are present in your system.

   $ pkginfo | grep IPLT

   If the following packages appear as output, then you can go to Step 2 to proceed with the migration. The output indicates that the iPlanet Directory Server 5.1 packages are in the system.

   system IPLTadcon Administration Server Console system IPLTadman Administration Server Documentation system IPLTadmin Administration Server system IPLTcons Console Client Base system IPLTdscon Directory Server Console system IPLTdsman Directory Server Documentation system IPLTdsr Directory Server (root) system IPLTdsu Directory Server (usr) system IPLTjss Network Security Services for Java system IPLTnls Nationalization Languages and Localization Support system IPLTnspr Portable Runtime Interface system IPLTnss Network Security Services system IPLTpldap PerLDAP $

   If the packages do not exist, then install the iPlanet Directory Server 5.1 packages first. Refer to the 4-step procedure in the preceding section Installing Directory Server 5.1. After installation is complete, go to Step 2 to proceed with the migration.

2. Migrate your iPlanet Directory Server 5.1 database to the current version. For instructions, refer to the documentation collection for the Sun Java System Directory Server at http://docs.sun.com/coll/DirectoryServer_05q1.

After migrating your data, make sure you continue to back up directory data in the same way as you backed up directory data before migration. Future disaster recovery might require the migrated database.

Issues While Running Debugger

The following issues involve the kernel debugger.

SPARC: Problems With dbx Debugger While Processing 64-bit Objects (6347707)

The dbx debugger terminates with a memory access failure while processing certain 64-bit executable files and libraries. However, the problem does not affect the normal use of these 64-bit objects. An error message similar to the following example is displayed:

dbx: internal error: signal SIGBUS (invalid address alignment)

Workaround: Use either the mdb debugger or the Solaris Dynamic Tracing facility instead. These alternatives can diagnose processes that use the 64-bit objects.

System Might Loop When Master CPU Is Changed (4405263)

A system that is running the Solaris kernel debugger to debug a live system might loop with incomplete error messages. This loop occurs when the OpenBoot PROM's master CPU is changed. A system reset restores the system to operation. However, the traces of the original failure are lost. Consequently, you cannot perform a diagnosis of the fatal reset.

Workaround: When the system is at the PROM level, the OpenBoot's ok prompt is displayed. In a system with multiple CPUs, the ok prompt is preceded by a number that is enclosed in curly braces. This number indicates the active CPU in the system. To run your debug session while at the PROM level, use the following steps.

1. Raise pil to f by typing the following command:

   {0} ok h# 0f pil!

2. Use the switch-cpu command to selectively switch from the currently active CPU to different CPUs. For example, to switch from CPU #0 to CPU #1, type the following command:

   (0) ok 1 switch-cpu

   The ok prompt is now preceded by the number of the CPU to which you switched.

   {1} ok

3. Run your debugger.

4. At the end of your debugger session, issue a reset-all command to return the system to normal use.

Make sure that you upgrade the system to the latest version of the OpenBoot PROM.

Localization Issues

This section describes localization issues that apply to Solaris 10 OS.

Wnn8 Japanese Input Method

Wnn8 Japanese Input method cannot be used if the Wnn8 servers are not enabled.

Workaround: Enable the Wnn8 servers:

# svcadm enable wnn8/server

In addition, select Wnn8 as the Japanese Language engine by running the iiim-properties command.

Keyboard Shortcuts in Mozilla Ambiguous in Spanish Locale (6288620)

The keyboard shortcuts in Mozilla 1.7 are ambiguous in the Spanish (Es) locale. For example, you can use Ctrl-S to copy or to save. No error message is displayed.

Workaround: Use the shortcut keys assigned to user actions from the product menu.

Uninstaller Displays Strings Incorrectly in Some Locales (6487062)

This bugs affects how you uninstall Solaris Trusted Extensions by using prodreg in locales other than C, POSIX, or any English locale. Strings are not displayed correctly in these locales when you uninstall by using prodreg.

No error message is displayed. The uninstaller shows placeholder strings, and buttons do not display correctly.

Workaround: Before you uninstall with prodreg, run the following commands:

# cd <Solaris_installation_media>/Solaris_10/ExtraValue/CoBundled/Trusted_Extensions
# cp -rp locale /var/sadm/tx

Then uninstall with prodreg.

Input Method Cannot Be Enabled With Primary Administrator Rights (6475081)

A user who has the Primary Administrator right can not use the input method for specific locales which prevents that user from entering characters normally. The input method status is not displayed in the workspace. No error message is displayed.

Workaround: Add the following lines to the /etc/security/exec_attr file:

Primary Administrator:solaris:cmd:::/usr/bin/csh:uid=0;gid=0
Primary Administrator:solaris:cmd:::/usr/bin/ksh:uid=0;gid=0
Primary Administrator:solaris:cmd:::/usr/bin/sh:uid=0;gid=0

For information about the file format, see the exec_attr(4) man page.

Auxilliary Window Fails to Open With Asian And Wnn Input Methods (6481697)

This bug affects the Solaris Trusted Extensions Desktop when you work with specific labels in some Asian locales. The AUX window fails to open with the Asian and Wnn Input methods. This prevents entering Asian characters normally. When the keyboard is used, multibyte characters are displayed.

Workaround: Perform the following steps:

1. Add the following three lines to the /usr/openwin/server/etc/TrustedExtensionsPolicy file and to the /usr/X11/lib/X11/xserver/TrustedExtensionsPolicy file for x86 systems only:

   selection /^Wnn/ selection /^wnn/ selection /^com.sun.iiim/

2. Restart the X Xserver.

New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)

When you upgrade the OS to the Solaris 10 6/06 or Solaris 10 11/06 release, the input method framework and individual input methods get upgraded from rev.10 to rev.12. However, ChuYin is not in the list of supported input methods. Also, you cannot use the function keys F2 and F3 to switch methods

Workaround: Use PinYin to type traditional Chinese characters with Hanyu PinYin. Use Ctrl+Shift to switch input methods.

AltGr Does Not Work As Mode Switcher in Some Russian Locales (6487712)

The AltGr key does not work as a mode switcher for the Russian Xsun layout inru_RU.KOI8-R and ru_RU.ANSI1251 locales.

Workaround 1: Switch to the ru_RU.UTF-8 or the ru_RU.ISO8859-5 locale.

Workaround 2: Use IIIMF^TM instead of the Russian keyboard layout.

Arabic6.kt Keytable Does Not Contain Arabic Symbols (6463576)

The Arabic6.kt keytable does not contain any Arabic symbols.

Workaround: Use IIIMF. Set the Arabic input through the gimlet switcher instead of switching to Arabic by using the Altgr key.

Some Compose Key Inputs Do Not Work on GTK Applications (6467756)

Some Compose key inputs such as Compose+?+? or Compose+|+| do not work on GTK applications in the EMEA UTF-8 locales. However, the inputs work fine on non-GTK applications, such as Motif or Java, when IM is inactive .

Workaround 1:

1. Edit the /usr/openwin/lib/locale/common/imsscript/S505multi and change the GTK_IM_MODULE=iiim to GTK_IM_MODULE=xim.

2. Log in to the system again.

Workaround 2:

Following the GTK application guidelines, choose X Input Method from the Input Methods submenu in the context menu of the text area. The Compose key inputs work when the IM is inactive

Input Method Switcher Does Not Work in Trusted Java DS Environment (6438372)

The input method status display and language switch functions do not work through Input Method Switcher on Java Desktop Systems (Java DS) panel. Admin label applications however, do work.

Workaround:

1. To display the IM status, change the display of the IM status to the application's frame by performing the following steps:

   • Start the Input Method Preference Editor (iiim-properties) from the command line or Launch menu (Preferences -> Desktop Preferences -> Input Methods).

   • Select Attach Window Frame at Placement choice button in the General tab.

   • Press Apply or click the OK button.

2. Switch input language through the language list which is shown. Left-click on the attached IM status window of the non-GTK application

The language list will not be shown for GTK applications. When language is switched on any non-GTK application, it will be reflected to all applications except when "The language is applied to all applications" check box is unchecked. This check box is checked by default in the General tab of Input Method Preference Editor. The language list will be shown if you run GTK applications with GTK_IM_MODULE=xim. For example:

% env GTK_IM_MODULE=xim gedit

Arabic Text Not Appearing in ar Locales

If your x86 system is using Xorg as the default Xserver, the Arabic font (iso7759-6) does not appear in the ar locale. This error does not occur if you are using XSun instead of XOrg.

Workaround: Follow these steps.

1. As superuser, edit /usr/dt/config/Xservers.

   • Uncomment or add the following line:

     :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner -defdepth 24

   • Comment out the following line:

     :0 Local local_uid@console root /usr/X11/bin/Xorg :0

2. Reboot the system.

Alternatively, you can log in to ar_EG.UTF-8 or other UTF-8 locales.

Solaris PDASync Does Not Support Data Exchange With the Multibyte Internationalized PDA Device (4263814)

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 Solaris PDASync application. If you accidentally exchange multibyte data and corrupt that data, restore your data from the backup.

Adding Regions Fails With the localeadm Command (6350486)

The function to add regions in the localeadm command no longer works if you create a new configuration file. The Language CD is not detected when you add the following regions:

• Southern Europe

• North America

• Northern Europe

The following error message is displayed:

No langcd image has been found in
/cdrom/sol_10_1005_x86_4/Solaris_10/Product

No langcd image has been found in
/cdrom/sol_10_1005_x86_4 /cdrom/sol_10_1005_x86_4
/cdrom/sol_10_1005_x86_4
/cdro m/sol_10_1005_x86_4
/cdrom/sol_10_1005_x86_4

Please enter the path to this image/disk, or enter 'q' to quit:

Workaround: When you are prompted to create a new configuration file, select No. Instead, use the configuration file that was installed in the system.

L10N Messages Missing When Using localeadm Utility to Add Locales (6423974)

When the Locale_config configuration file is created using the DVD/net image, using the Locale_config file to add locales leaves many unlocalized messages on the Gnome Desktop. No error message is displayed.

Workaround 1:

Login as superuser and do the following:

1. Change to the location of the localeadm Locale_config file.

   # cd /usr/sadm/lib/localeadm/

2. Revert to the existing Locale_config file bundled with the localeadm utility.

   # mv Locale_config_S10.txt.old Locale_config_S10.txt

Workaround 2:

Re-create the Locale_config file by using the CD images.

SPARC: Keycode 50 Does Not Work for European Keyboard Layouts (6387317)

Keycode 50 is not working for European keyboard layouts. This problem occurs with all European *6.kt keytable files. All keytables assign some symbols to keycode 50, but the key does not work. No error message is displayed.

Workaround:

Edit the *6.kt files in the /usr/openwin/share/etc/keytables directory. Duplicate keycode 50 for keycode 49 in the affected *6.kt file. For example, add the following entry for keycode 49 to the affected keytable file:

49 RN XK_numbersign XK_asciitilde

Several Arabic Fonts Do Not Work in GNOME (6384024)

In GNOME when you select certain Arabic fonts, the characters do not display. This problem appears when you select fonts for applications, the desktop, or the window title using the GNOME font properties menu. The affected fonts include:

• Akhbar MT (Regular, Bold)

• Shayyal MT (Regular, Bold)

• Naskh MT (Regular, Bold)

No error message is displayed.

Workaround:

Use any of the newly delivered Kacst family of fonts to display Arabic characters in GNOME applications.

Unable to Switch Input Language on Session-Saved Applications (6360759)

Multiple language input is supported in UTF-8 locales, but the language switch is not working with session-saved applications where mouse button 1 is clicked first after login. This problem occurs with the Java Desktop System (JDS). No error message is displayed.

Workaround:

Click mouse button 1 on the backgroundworkspace or Launch Menu before clicking any application.

Some Language Input Does Not Work Correctly on Non-U.S. Keyboard Layouts (6319383)

Localized keyboard layout based language inputs, such as Cyrillic and Arabic, are not working correctly with non-U.S. keyboard layouts. For example, if you are using French keyboard and switch to Arabic input then the typed output results are not based on Arabic Keyboard layout. For more information about input method, see Input Method Preference Editor and InputMethod Switcher Applet help. No error message is displayed.

Workaround 1:

Use XKB extension to switch keyboard layouts for Xorg server (x86 only). For example, add the following entry to the xorg.conf configuration file:

Section "InputDevice"
        Identifier "Keyboard1"
        Driver "Keyboard"

        Option "XkbModel" "pc105"
        Option "XkbLayout" "us,fr,ru"
        Option "XKbOptions" "grp:alt_shift_toggle"
EndSection

This configuration enables you to switch among U.S., French, and Russian keyboard layouts by pressing the Alt-Shift keys. For more information, see the /usr/X11/share/doc/README.XKB-Config file.

Workaround 2:

Use the xorgcfg utility to configure localized keyboard layouts (x86 only).

If a non-root user uses the xorgcfg utility, the configuration is not saved, but keyboard layout is changed for the current session.

Keyboard Shortcuts in Mozilla in ES Locale Are Unusual and Ambiguous (6288620)

The keyboard shortcuts in Mozilla 1.7 are unusual, especially in Spanish locale. For example, Ctrl-S is being used for copying as well as for saving. No error message is displayed.

Workaround:

Identify the shortcut keys assigned to user actions from menu in the product.

Login Screen Marks UTF-8 Locales as Recommended

On the Language menu of the login screen, the UTF-8 locales are labeled as a recommended option. For example, for Japanese locales, the screen would appear as follows:

ja_JP.eucJP -------------- Japanese EUC
ja_JP.PCK  --------------- Japanese PCK
ja_JP.UTF-8 (Recommended) - Japanese UTF-8

Using UTF-8 locales is recommended to users of the Java Desktop System (JDS) because JDS uses UTF-8/Unicode as internal character encoding. This recommendation also applies to the announcement of future end-of-software support for non-UTF-8 locales. See Legacy or Traditional Non-UTF-8 Locales.

Migration Note to UTF-8 locales

When migrating to UTF-8 locales, the files affect the method that you use to import or export data.

Microsoft Office Files

Microsoft Office files are encoded in Unicode. StarOffice applications can read and write the Unicode encoded files.

HTML Files

HTML files authored using HTML editors such as Mozilla Composer, or HTML files saved by a web browser, usually contain a charset encoding tag. After exporting or importing, you can browse such HTML files with the Mozilla Navigator web browser, or edit the files with Mozilla Composer, according to the encoding tag in the HTML file.

Fixing Broken HTML File

Some HTML files might be displayed in garbage characters. This problem is typically due to the following reasons:

• The charset encoding tag is incorrect.

• The charset encoding tag is missing.

To find the charset encoding tag in the HTML file, perform the following actions:

1. Open the file with Mozilla.

2. Press Ctrl-i, or click View to open the View menu.

3. Click Page Info.

The charset information is in the bottom of the General tab, for example:

Content-Type text/html; charset=us-ascii

If the string charset=us-ascii does not match the actual encoding of the file, the file might appear broken. To edit the encodings of the HTML file, perform the following actions:

1. Open the file with Mozilla Composer.

2. Open the File menu.

3. Select Save as Charset.

4. Choose the correct encoding. Mozilla Composer automatically converts the encoding and the charset tag as appropriate.

Emails Saved As Portable Format

Modern mails are tagged with the MIME charset tag. The Email and Calendar application accepts MIME charset tags. You do not need to perform any encoding conversion.

Plain Text Files

Plain text files do not have a charset tag. If the files are not in UTF-8 encoding, encoding conversion is needed. For example, to convert a plain text file encoded in Traditional Chinese big5 to UTF-8, execute the following command:

iconv -f big5 -t UTF-8 inputfilename



 > outputfilename

You can also use the File System Examiner for the encoding conversion.

You can use the Text Editor to read and write character encoding text automatically or by specifying an encoding explicitly when opening or saving a file.

To start Text Editor, click Launch, then choose Applications->Accessories->Text Editor.

File Names and Directory Names

If file names and directory names using multibyte characters are not in UTF-8 encoding, encoding conversion is needed. You can use File System Examiner to convert file and directory names and the contents of plain text files from legacy character encodings to UTF-8 encoding. Refer to the online Help for File System Examiner for more information.

To start File Systems Examiner, click Launch, then choose Applications->Utilities->File System Examiner.

When you access non-UTF-8 file or directory names on Microsoft Windows via SMB using File Manager, you can access the non-UTF-8 file or directory names without encoding conversion.

Launching Legacy Locale Applications

For applications that are not ready to migrate to Unicode UTF-8, you can create a launcher on a front panel to start the application in legacy locales. You can also launch the applications directly from the command line. Perform the following steps to create a launcher for an application.

1. Right-click on the panel where you want to place the launcher.

2. Choose Add to Panel->Launcher.

3. Use the following format to type the entry in the Command field in the Create Launcher dialog:

   env LANG=locale LC_ALL= locale application name

   For example, if you want to launch an application called motif-app from /usr/dt/bin in the Chinese Big5 locale, enter the following text in the Command field of the Create Launcher:

   env LANG=zh_TW.BIG5 LC_ALL=zh_TW.BIG5 /usr/dt/bin/motif-app

4. Click OK to create the launcher on the panel.

When you need to run CLI (command line interface) applications which are specific to a legacy locale, open a Terminal window in the legacy locale first and then run the CLI applications in the same Terminal window. To open a Terminal window in a legacy locale, enter the following command:

eng LANG=locale LC_ALL=locale GNOME-TERMINAL –disbable-factory.

Instead of opening a new Terminal window in a legacy locale, you can switch the locale setting from UTF-8 to a legacy locale in the current Terminal window by changing the encoding the Set Character Encoding menu in the Terminal window. Then you must also set the LANG and LANG environment variables to the current shell.

Hardware for Estonian Keyboard Type 6, French Canadian Keyboard Type 6, and Polish Programmers Keyboard Type 5 Not Available

Software support for three additional keyboard layouts has been added to the Solaris OS: Estonian keyboard Type 6, French Canadian keyboard Type 6, and Polish programmers keyboard Type 5.

This software gives users in Estonia, Canada, and Poland greater flexibility for keyboard input by modifying standard U.S. keyboard layouts to their own language needs.

Currently, no hardware is available for the three additional keyboard layout types.

Workaround: To take advantage of this new keyboard software, modify the /usr/openwin/share/etc/keytables/keytable.map file in one of the following ways:

• For the Estonian Type 6 keyboard, make the following changes:

  1. Change the US6.kt entry to Estonia6.kt in the /usr/openwin/share/etc/keytables/keytable.map file. The modified entry should read as follows:

     6 0 Estonia6.kt

  2. Add the following entries to the /usr/openwin/lib/locale/iso8859-15/Compose file:

     <scaron>	: "/xa8"	scaron
     <scaron>	: "/xa6"	scaron
     <scaron>	: "/270"	scaron
     <scaron>	: "/264"	scaron

  3. Reboot the system for the changes to take effect.

• For the French Canadian Type 6 keyboard, make the following changes:

  1. Change the US6.kt entry to Canada6.kt in the /usr/openwin/share/etc/keytables/keytable.map file. The modified entry should read as follows:

     6 0 Canada6.kt

  2. Reboot the system for the changes to take effect.

• If you are using the existing Polish Type 5 keyboard layout, make the following changes:

  1. Change the Poland5.kt entry to Poland5_pr.kt in the /usr/openwin/ share/etc/keytables/keytable.map file. The modified entry should read as follows:

     4 52 Poland5_pr.kt

     ---

     Note –

     If you are using a keyboard with dip-switches, make sure the switches are set to the correct binary value for the Polish keytable entry (binary 52) before rebooting the system.

     ---

  2. If you are using a standard U.S. Type 5 keyboard, change the US5.kt entry to Poland5_pr.kt in the /usr/openwin/share/etc/keytables/keytable.map file. The modified entry should read as follows:

     4 33 Poland5_pr.kt

  3. Reboot the system for the changes to take effect.

Cannot Print Documents in Portable Document Format (6239307, 6218079)

On all locales, the Document Viewer cannot print localized files that are in Portable Document Format (PDF).

Workaround: Choose one of the following workarounds:

• On SPARC based systems, use the Acrobat Reader to print localized PDF files.

• On x86 based systems, use StarOffice to create and then print PDF files.

x86: Login Process Might Hang in Certain Asian Non-UTF-8 Locales (6215527)

On some x86 based systems, if you log in to certain Asian non-UTF-8 locales, the login process might hang. The following are examples of the locales where the error is observed:

• zh_CN.EUC

• zh_TW.BIG5

• ko_KR.EUC

Workaround: At the login window's Language menu, choose UTF-8 locales.

Special Keyboard Keys Do Not Work (5077631)

Special keys on the left of the keyboard do not work on European keyboard mappings. This problem affects all European locales.

Workaround: Use shortcut keys instead of the special keyboard keys. The following example lists shortcut keys and the corresponding functions:

• Ctrl-Z - Undo

• Ctrl-C - Copy

• Ctrl-V - Paste

• Alt-Tab allows you to switch between windows.

Modifier Keys Do Not Function Correctly (4996542)

On all locales, the Alt key and the Shift key might not function as modifier keys when you use the Internet/Intranet input method. For example, the Shift-arrow key combination might not allow you to select text. Instead, the combination might insert Latin characters.

Workaround: Use a different input method, for example, Default. To switch input methods, right-click on an object and select Input method.

Chinese and Korean Characters Are Printed In a Box (4977300)

The postscript printer does not bundle Chinese or Korean fonts. Consequently, in Chinese or Korean locales, if you attempt to print from the Mozilla browser, the characters are printed within a box. The Common UNIX Printer System (CUPS) needs to convert the Mozilla postscript fonts before a file can be printed.

Workaround: Perform the following steps.

1. Click Launch => Preferences => Printers.

2. Right-click the PostScript printer icon, then select Properties.

3. Click the Advanced tab.

4. Set the Ghostscript pre-filtering to Convert to PS level 1.

Sort Capability in the European UTF-8 Locales Does Not Function Correctly (4307314)

The sort capability 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 ISO–1 equivalent.

# echo $LC_COLLATE
>  es_ES.UTF-8
# LC_COLLATE=es_ES.IS08859-1
# export LC_COLLATE

Then start sorting.

Networking Issues

The following networking bugs apply to the Solaris 10 release.

Login Fails on iSCSI Target With Two Portals and One Bad Portal (6476060)

If an iSCSI target or an array returns more than one IP address as part of its send target response, the initator takes into account only the last address in the list and not the first one, as it used to prior to this release. As a result, if the last IP address is bad or invalid, the connection to this target fails.

Workaround: Return the different target portal group tags (TPGT) for each entry in its send target response. The initiator tries to establish a connection to all the IP addresses so that the connection succeeds.

System Domain of Interpretation Is Not Configurable (6314248)

The system Domain of Interpretation (DOI) is not configurable. When the SMC is used to create a new trusted network template, the SMC sets the DOI to 0 and Solaris Trusted Extensions does not function correctly. Various error messages are displayed.

Workaround: Set the DOI to 1 using the SMC.

Memory Leaks with ECC and RSA Cipher Suites (6421471)

Memory leak in NSS with ECC and RSA cipher suites might cause a system hang or system panic. The out of memory error message is displayed.

Workaround: Install the following patches:

• Patch ID 119213-09 for SPARC based systems.

• Patch ID 119214-09 for x86 based systems.

iSCSI Initiator Does Not Handle LUN Address Reporting Properly (6377485)

The Solaris iSCSI software initiator does not support logical units with a LUN greater than 255. No error message is displayed.

Workaround:

Change the logical unit numbers of the target device to less than 255.

Wrong MAC Address is Displayed When There is More Than One Ethernet Card (6316245)

When you register to a Solaris 10 11/06 OS for remote update management using the Sun Update Connection, your system information is displayed. If your system has more than one Ethernet card, the same MAC address is displayed for all the Ethernet cards. No error message is displayed.

Workaround: None.

SPARC: RTM_IFINFO Message Has Different Sizes on 32-bit and 64-bit Compilations

Sixty-four-bit programs that create PF_ROUTE sockets and parse the contents of RTM_IFINFO messages in the if_msghdr_t structure might work incorrectly unless they are recompiled.

IP Forwarding Disabled by Default in Solaris 10 OS

In this Solaris release, IP forwarding is disabled by default. This setting applies to both IPv4 and IPv6 regardless of other system configurations. Systems with multiple IP interfaces that formerly forwarded IP packets by default no longer have this automatic feature. To enable IP forwarding in multihomed systems, administrators must manually perform additional configuration steps.

Workaround: The command routeadm enables IP forwarding. The configuration changes that are the result of routeadm usage persist across system reboots.

• To enable IPv4 forwarding, type routeadm -e ipv4-forwarding .

• To enable IPv6 forwarding, type routeadm -e ipv6-forwarding .

• To apply the enabled IP-forwarding configuration to the currently running system, type routeadm -u.

For more information about IP forwarding, see the routeadm(1M) man page.

Generic LAN Driver Version 3 Fails to Set Field Length of Logical Link Control Frames (6350869)

The Generic LAN Driver Version 3 (GLDv3) incorrectly sets the field length of Logical Link Control (LLC) frames. Consequently, protocols such as AppleTalk that are dependent on LLC do not function correctly. No error message is displayed. The problem affects the following network interface controllers:

• bge

• e1000g

• xge

Workaround: None.

Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)

A zone can be configured so that the zone's IP address becomes part of an IP Network Multipathing (IPMP) group. The configuration process is documented in How to Extend IP Network Multipathing Functionality to Non-Global Zones in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

If all the network interfaces in the IPMP group fail, a zone does not boot if it has an IP address that is part of the IPMP group.

The following example illustrates the result if you attempt to boot the zone.

# zoneadm -z my-zone boot 
zoneadm: zone 'my-zone': bge0:1: 
could not set default interface for multicast: Invalid argument 
zoneadm: zone 'my-zone': call to zoneadmd failed

Workaround: Repair at least one network interface in the group.

Intermittent Errors Might Occur With the Use of DataDigests (5108515)

Internet SCSI (iSCSI) targets might report cyclic redundancy check (CRC) errors if DataDigests are enabled. User applications that update input/output buffers after transmitting to the iSCSI initiator might cause a miscalculation of the CRC. When the target responds with a CRC error, the iSCSI Initiator retransmits the data with the correct DataDigest CRC. Data integrity is maintained. However, data transfer performance is affected. No error message is displayed.

Workaround: Do not use the DataDigest option.

ATM LANE Subnets for IPv4/IPv6 Might Not Complete Initialization (4625849)

During system boot, multiple instances might not connect to their LAN Emulation (LANE) instance if more than eight LANE instances are on a single adapter. This bug does not appear at multiuser level.

Workaround: To reinitialize your SunATM network, perform the following steps:

1. Verify the problem by issuing a lanestat -a command.

   Instances that are not connected have Virtual Circuit Identifier (VCI) values of 0 to the LAN Emulation Server (LES) and Broadcast and Unknown Address Server (BUS).

2. Stop and restart your SunATM network.

   # /etc/init.d/sunatm stop # /etc/init.d/sunatm start

3. Reset netmasks or any other network setup for the SunATM interfaces.

Configuring Multiple Tunnels Between Two IP Nodes With Filtering Enabled Might Result in Packet Loss (4152864)

If you configure multiple IP tunnels between two IP nodes, and enable ip_strict_dst_multihoming or other IP filters, packet loss might result.

Workaround: Choose one of the following:

• First, configure a single tunnel between the two IP nodes. Add addresses to the tunnel by using the ifconfig command with the addif option.

• Do not enable ip_strict_dst_multihoming on tunnels between two IP nodes.

Security Issues

The following security issues applies to the Solaris 10 release.

Nonpassword Logins Fail With pam_ldap Enabled

After the account management PAM module for LDAP (pam_ldap) is enabled, users must have passwords to log in to the system. Consequently, nonpassword-based logins fail, including those logins that use the following tools:

• Remote shell (rsh)

• Remote login (rlogin)

• Secure shell (ssh)

Workaround: None.

Incorrect Parameters Might Cause Panic in Sun StorEdge T3 (4319812)

A Sun StorEdge^TM T3 system might panic if an application uses the HTTP interface to send tokens with out-of-range parameters.

Service Management Facility

This section describes issues that involve the Service Management Facility of Solaris 10 OS. For more information about this new feature in the Solaris OS, see Solaris Service Manager in Solaris 10 What’s New.

Print Services Have Offline Settings by Default (5100134)

When a host has no local printers configured, two print services, ipp-listener and rfc1179, are set to offline by default. These services are automatically moved to online after local printers are configured on the host. The default offline settings of these services do not indicate an error. Therefore, no user intervention is required.

Workaround: None.

keyserv Daemon Disables Some File System Services (5084183)

On systems that do not use Network Information Service (NIS) or NIS+ name service, the NFS and autofs services are disabled. The failure is due to these services' dependency on the keyserv daemon. The keyserv daemon relies on the RPC domain name, which is not set on systems that do not use NIS or NIS+. Consequently, the failure of the keyserv daemon causes the NFS and autofs services to become disabled.

Workaround: To enable the services, perform the following steps:

1. Become superuser.

2. Issue the following commands:

   # svcadm disable network/rpc/keyserv # svcadm disable -t network/nfs/client:default # svcadm enable network/nfs/client:default # svcadm disable -t network/nfs/server:default # svcadm enable network/nfs/server:default # svcadm disable -t network/rpc/gss:ticotsord # svcadm enable network/rpc/gss:ticotsord

Login Prompts Sometimes Appear Before File Systems Are Mounted (5082164)

During system startups, sometimes the login services such as console or ssh logins start before remote file systems and naming services become available. Consequently, the user name might not be recognized or the user's home directory might not be available.

Workaround: If the error occurs, wait for a few seconds and then log in again. Alternatively, log in from a local account to view the system state.

Smart Card

The following Smart Card bugs apply to Solaris 10 OS.

System Does Not Respond to Smart Card (4415094)

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:

1. Perform a remote login to the machine on which the ocfserv process was terminated.

2. Become superuser.

3. Kill the dtsession process by typing the following in a terminal window.

   # pkill dtsession

ocfserv restarts and smart card login and capability are restored.

Edit Config File Menu Item in Smartcards Management Console Does Not Work (4447632)

The Edit Config File menu item in the Smartcards 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 which indicates not to continue unless requested by technical support.

Workaround: Do not use the Edit Config File menu item in the Smartcards Management Console. For information on smart card configuration, see the Solaris Smartcard Administration Guide.

Solaris Commands and Standards

The following section describes behavior changes in certain commands and standards in Solaris 10 OS.

Failed Unconfigure Command cfgadm Might Succeed Later Without Notice (6483258)

Sometimes the cfgadm -c unconfigure command fails because of pending I/Os. With the changed kernel, the command is retried offline. The cfgadm's unconfigure command might, however, succeed later without any notice to the user.

Workaround: Run the cfgadm -al command.

Bash 2.0.5b No Longer Sets Some Environment Variables

Solaris 10 OS includes Bash 2.0.5b. This shell no longer automatically exports the following variables to the environment:

• HOSTNAME

• HOSTTYPE

• MACHTYPE

• OSTYPE

This new behavior applies even if the shell assigns default values to these variables.

Workaround: Export these variables manually.

New ln Utility Requires -f Option

The behavior of /usr/bin/ln has changed to adhere to all of the standards from SVID3 through XCU6. If you use the ln command without the -f option to link to an existing target file, the link is not established. Instead, a diagnostic message is written to standard error, and the command proceeds to link any remaining source files. Finally, the ln command exits with an error value.

For example, if file b exists, the syntax ln a b generates the following message:

ln: b: File exists

This behavior change affects existing shell scripts or programs that include the ln command without the -f option. Scripts that used to work might now fail in Solaris 10 OS.

Workaround: Use the -f option with the ln command. If you have existing scripts that execute the link utility, make sure to modify these scripts to comply with the command's new behavior.

New tcsh Rejects setenv Variable Names That Use a Dash or an Equals Sign

In Solaris 10 OS, tcsh has been upgraded to version 6.12. This version no longer accepts environment variables whose names use a dash or an equals sign. Scripts that contain setenv lines and that work in earlier Solaris versions might generate errors in the current Solaris 10 release. The following error message is displayed:

setenv: Syntax error

For more information, refer to the tcsh man page for the Solaris 10 OS.

Workaround: Do not use the dash or equals sign in names for environment variables.

STDIO getc Family EOF Condition Behavior Change

Applications that were built in strict standard C conformance mode are affected by the behavior changes of certain library functions. An example is applications that were compiled by using the cc -Xc or c89 compilation mode. The behavior has changed for the following library functions:

• fgetc()

• fgets()

• fgetwc()

• fgetws()

• getc()

• getchar()

• gets()

• getwc()

• getwchar()

• getws()

A formal interpretation of the 1990 C Standard requires that after an end-of-file condition is set, no more data is returned from the file on subsequent input operations. The exception is if the file pointer is repositioned or the error and end-of-file flags are explicitly cleared by the application.

The behavior for all other compilation modes remains unchanged. Specifically, the interfaces can read additional newly written data from the stream after the end-of-file indicator has been set.

Workaround: Call fseek() or clearerr() on the stream to read additional data after the EOF condition has been reported on the stream.

Output Columns of the ps Command Have Been Widened

Due to larger UIDs, processor ids, and cumulative execution time, the columns of the ps command output have been widened. Customer scripts should not assume fixed output columns.

Workaround: Scripts should use the -o option of the ps command.

For more information, see the ps(1) man page.

Command ping -v Does Not Work on IPv6 Addresses (4984993)

The command ping -v fails when the command is applied to addresses that use Internet Protocol version 6 (IPv6). The following error message is displayed:

ping: setsockopt IPV6_RECVRTHDRDSTOPTS Invalid argument

Workaround: None. To obtain the same ICMP packet information that ping -v provides, use the snoop command.

Solaris Volume Manager

The following Solaris Volume Manager bugs apply to the Solaris 10 release.

Solaris Volume Manager metattach Command Might Fail

If you have a Solaris Volume Manager mirrored root (/) file system in which the file system does not start on cylinder 0, all submirrors you attach must also not start on cylinder 0.

If you attempt to attach a submirror starting on cylinder 0 to a mirror in which the original submirror does not start on cylinder 0, the following error message is displayed:

can't attach labeled submirror to an unlabeled mirror

Workaround: Choose one of the following workarounds:

• Ensure that both the root file system and the volume for the other submirror start on cylinder 0.

• Ensure that both the root file system and the volume for the other submirror do not start on cylinder 0.

By default, the JumpStart installation process starts swap at cylinder 0 and the root (/) file system somewhere else on the disk. Common system administration practice is to start slice 0 at cylinder 0. Mirroring a default JumpStart installation with root on slice 0, but not cylinder 0, to a typical secondary disk with slice 0 that starts at cylinder 0, can cause problems. This mirroring results in an error message when you attempt to attach the second submirror. For more information about the default behavior of Solaris installation programs, see the Solaris 10 Installation Guides.

Solaris Volume Manager metassist Command Fails in Non-English Locales (5067097)

In non-English locales, the Solaris Volume Manager metassist command might fail to create volumes. For example, if LANG is set to ja (Japanese), the following error message is displayed:

xmlEncodeEntitiesReentrant : input not UTF-8
Syntax of value for attribute read on mirror is not valid
Value "XXXXXX"(unknown word) for attribute read on mirror 
is not among the enumerated set
Syntax of value for attribute write on mirror is not valid
Value "XXXXXX"(Parallel in Japanse) for attribute write on mirror 
is not among the enumerated set
metassist: XXXXXX(invalid in Japanese) volume-config

Workaround: As superuser, set the LANG variable to LANG=C.

For the Bourne, Korn, and Bash shells, use the following command:

# LANG=C; export LANG

For the C shell, use the following command:

# setenv LANG C

Volume Creation Fails in Systems With Unformatted Disks (5064066)

Creating Solaris Volume Manager volume configurations with the metassist command might fail if an unformatted disk is in the system. The following error message is displayed:

metassist: failed to repartition disk

Workaround: Manually format any unformatted disks before you issue the metassist command.

Hot Spares Do Not Work Correctly When Solaris Volume Manager RAID-1 (Mirror) or RAID-5 Volumes Are Created in Disk Sets Built on Soft Partitions (4981358)

If you create a Solaris Volume Manager RAID-1 (mirror) or RAID-5 volume in a disk set that is built on top of a soft partition, hot spare devices do not work correctly.

Problems that you might encounter include, but are not limited to, the following:

• A hot spare device might not activate.

• A hot spare device status might change, indicating the device is broken.

• A hot spare device is used, but resynced from the wrong drive.

• A hot spare device in use encounters a failure, but the broken status is not reported.

  Workaround: Do not use this configuration to create a Solaris Volume Manager RAID-1 or RAID-5 volume in disk sets.

Solaris Volume Manager metadevadm Command Fails if Logical Device Name No Longer Exists (4645721)

You cannot replace a failed drive with a drive that has been configured with the Solaris Volume Manager software. The replacement drive must be new to Solaris Volume Manager software. If you physically move a disk from one slot to another slot on a Sun StorEdge A5x00, the metadevadm command fails. This failure occurs when the logical device name for the slice no longer exists. However, the device ID for the disk remains present in the metadevice replica. The following message is displayed:

Unnamed device detected. Please run 'devfsadm && metadevadm -r to resolve.

You can access the disk at the new location during this time. However, you might need to use the old logical device name to access the slice.

Workaround: Physically move the drive back to its original slot.

Solaris Volume Manager metarecover Command Fails to Update metadb Namespace (4645776)

If you remove and replace a physical disk from the system, and then use the metarecover -p -d command to write the appropriate soft partition specific information to the disk, an open failure results. The command does not update the metadevice database namespace to reflect the change in disk device identification. The condition causes an open failure for each such soft partition that is built on top of the disk. The following message is displayed:

Open Error

Workaround: Create a soft partition on the new disk instead of using the metarecover command to recover the soft partition.

If the soft partition is part of a mirror or RAID 5, use the metareplace command without the -e option to replace the old soft partition with the new soft partition.

# metareplace dx mirror or RAID 5 
old_soft_partition new_soft_partition

Sun Java Desktop System

This section describes issues that apply to the Sun Java Desktop System (Java DS) in the Solaris 10 OS.

Email and Calendar

This section describes issues related to Email and Calendars.

Problems With Using Multiple Attachments (6260583)

If you drag and drop email messages to a new email message body, the content of the new email message is corrupted.

Workaround: To send multiple attachments, perform the following steps:

1. Select the messages you want to attach.

2. On the Menu bar, choose Action => Forward => Attached.

   Alternatively, you can press Ctrl-J to send the messages.

Problem With Changing Authentication Type (6246543)

After you change the authentication type for the incoming mail server, Email and Calendar might not work correctly.

Workaround: Restart Email and Calendar.

Incomplete List of Contacts in Contact Folder (5088514)

After you import an LDAP Data Interchange Format file containing several contacts, only some of the contacts are displayed in your contact folder. This is a display problem only. Email and Calendar has imported all the contacts.

Workaround: Restart Email and Calendar.

Login Issues

This section describes login issue.

Login Error Message

You might encounter the following error message when you log in to a Java Desktop System session:

Could not look up internet address for hostname.
This will prevent GNOME from operating correctly.
It may be possible to correct the problem by adding 
hostname to the file /etc/hosts

Workaround: Ensure that your hostname is set up correctly in the /etc/hosts file. Perform the following steps:

1. Set the hostname in the /etc/hosts file as follows:

   127.0.0.1 localhost loghost hostname localhost.localdomain

   hostname is the name of your system.

2. Ensure that your hostname is listed in the /etc/nodename file. This file must also contain the following line:

   127.0.0.1 localhost loghost hostname localhost.localdomain

$PATH issues (6247943)

When you log into Java Desktop System Release 3, your $PATH is set incorrectly to the following:

/usr/bin::/usr/dt/bin:/usr/openwin/bin:/bin:
/usr/ucb:/usr/openwin/bin:/usr/dt/bin

Workaround: Remove the following from your $PATH:

• /usr/openwin/bin:

• /bin:

• ::

The resulting path should be similar to the following example:

/usr/bin:/usr/dt/bin:/usr/ucb:/usr/openwin/bin:/usr/dt/bin

Remote Connection Problems (6203727)

If you use dtlogin remote connection, you cannot connect to the GNOME Display Manager from certain systems.

Workaround: When you are prompted to select the remote login, specify the IP address instead of the hostname.

Help System

Wrong Help Window Opened For Volume Control (6253210)

If you use the Yelp browser to open the online help for Volume Control, the help file for the Keyboard Accessibility panel application is opened instead.

Workaround: None.

Online Help Freezes (5090731)

If you open an application's online help and no help files exist for that application, an error dialog box is displayed. Unless you click OK, the online Help system freezes and you cannot open the online help of other applications that you start subsequently.

Workaround: You must click the OK button in the error dialog box.

Mozilla Browser

Cannot Print Certain Documents From the Mozilla Browser

You cannot print documents from the Mozilla browser if the documents contain Unicode characters that are not in the Basic Multilingual Plane (BMP).

Workaround: None.

Cannot Specify User Preferences for Roaming Access in Mozilla Browser (6200999)

In the Mozilla browser, you can specify that User Preferences should be transferred to and from the Roaming Access server. You specify your Roaming Access option by following these steps:

1. On the browser, click Edit and select Preferences.

2. Select Roaming User, then select Item Selection.

3. On the right panel, select User Preferences.

However, the selection of User Preferences does not take effect.

Workaround: None.

Keyboard Shortcuts Fail (6192644)

In the Mozilla browser, you enable caret browsing by pressing F7. When caret browsing is enabled, the keyboard shortcut Ctrl-Home brings you to the beginning of the web page that you are browsing. However, this keyboard shortcut does not work when you browse certain sites such as www.yahoo.com and www.mozilla.org.

Workaround: Disable caret browsing by pressing F7.

System-Level Issues

User Preferences Not Fully Compatible

User preferences in your home account for an earlier version of the GNOME Desktop might be partly incompatible with the version on the Java DS Release 3.

Workaround: Reset your preferences. Perform the following steps:

1. Log out of the Java Desktop System.

2. Click Session and choose Failsafe terminal.

3. Log in.

4. In the failsafe terminal window, enter the following commands:

   % gnome-cleanup exit

5. Log in again.

   Your GNOME preferences are now reset.

GNU Image Manipulation Program Missing From the Graphics Menu (6209566)

The GNU Image Manipulation Program (GIMP) is not available in the Graphics menu.

Workaround: Perform the following steps.

1. Open a terminal window.

2. Edit the /usr/share/applications/gimp-2.0.desktop file.

3. Change the Exec and TryExec lines to add the full path to the GIMP binary:

   TryExec=/usr/sfw/bin/gimp2.0 Exec=/usr/sfw/bin/gimp-remote-2.0 %u

Problems With Online Registration of StarOffice 7 Software (6208829)

You might be unable to complete the online registration of the StarOffice 7 software if the software cannot find Mozilla on the system. The software must be able to locate the Email and Calendar application to successfully send documents.

Workaround: Add /usr/sfw/bin to your PATH. Perform the following steps.

1. Open a terminal window.

2. Issue the following command:

   % export PATH=/usr/sfw/bin:$PATH

3. To start the StarOffice software, issue the following command:

   % soffice

4. Complete the StarOffice registration procedure.

Problems With Sound Recorder

The slide bar and the side counter do not work when the Sound Recorder is recording a new.wav file.

Workaround: None.

Volume Control Option Not Working

The option in the Volume Control panel application that enables you to start the Volume Control desktop applications does not work.

Workaround: None.

Outdated List of Allowed Applications for Solaris OS (6267922)

In the Solaris software, you restrict application launching by setting to true the /desktop/gnome/lockdown/restrict_application_launching gonf key. This setting allows only certain applications to appear on the Launch menu where you can start these applications. The allowed applications are listed in the /desktop/gnome/lockdown/allowed_applications gonf key.

Currently, the list includes applications that are outdated and are no longer included in the Java Desktop System software. Moreover, the list also contains references to certain applications with incorrect directory locations. Consequently, if you restrict application launching, certain key applications such as Mozilla or StarOffice do not appear on the Launch menu.

Workaround: Perform the following steps.

1. Become superuser.

2. Remove the ~/.gconf/desktop/gnome/lockdown directory if the directory exists.

   # rm -rf ~/.gconf/desktop/gnome/lockdown

3. Log out of the system and then log in again.

Problems When Using Keyboard Indicator (6245563)

Using the keyboard indicator might make the keyboard unusable when you switch between X servers.

Workaround: None. Do not use the Keyboard Indicator.

Certain View Options Might Cause File Manager to Fail (6233643)

The File Manager might fail if you use the following View options:

• View as Catalog

• View as Image Collection

Depending on the View options that you use, the following error messages might be displayed:

• Error:

  The application nautilus has quit unexpectedly

• Error:

  The Catalog view encountered an error while starting up

• Error:

  The Image Collection view encountered an error while starting up

Workaround: None. Every time these problems occur, restart File Manager or click the Restart Application button on the crash dialog box.

CD Quality, Lossless Mode Fails at Start of Recording (6227666)

If you use the Sound Recorder multimedia application in CD Quality, Lossless mode, the application fails when recording starts. The following error message is displayed:

The Application "gnome-sound-recorder" has quit unexpectedly.

Workaround: Perform the following steps.

1. Become superuser.

2. Issue the following command:

   # GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule /etc/gconf/schemas/gnome-audio-profiles.schemas

In addition, existing users must perform the following steps.

1. If the gnome-audio-profiles-properties application is running, stop the application by closing the application window.

2. If the profile cdlossless exists in ~/.gconf/system/gstreamer/audio/profiles, remove the profile.

   % rm ~/.gconf/system/gstreamer/audio/profiles/cdlossless

3. Log out of the system and then log in again.

Cannot Delete Files Outside of Home Directory (6203010, 5105006)

You can only delete files from your own home directory file system.

Workaround: To delete files outside your home directory file system, open a terminal window and use the command line.

Problems Creating Certain Types of Archives (5082008)

You cannot use Archive Manager to create the following types of archives:

• .arj

• .lha

• .bzip

• .lzop

• .zoo

Workaround: None.

System Administration

This section describes system administration bugs in Solaris 10 OS.

Solaris Trusted Extensions Administration Tools Display Incorrect Labels (6478436)

Solaris Trusted Extensions administration tools such as the Solaris Management Console (SMC) and tninfo might not display the ADMIN_LOW or ADMIN_HIGH labels. Instead the administration tools might incorrectly display labels like PUBLIC and CNF : RESTRICTED.

This incorrect display of labels can result in misconfigured systems. For example, the SMC might incorrectly display PUBLIC for a zone when the actual default label is ADMIN_LOW. Because of incorrect label display the zone fails to boot.

The error is because the default label view is EXTERNAL when it should be INTERNAL. This causes ADMIN_LOW to be promoted to the minimum user label and ADMIN_HIGH to be demoted. As a result, the administration tools incorrectly display the lowest and highest labels defined instead of correctly displaying ADMIN_LOW and ADMIN_HIGH.

Workaround: Perform the following steps:

1. Install Solaris Trusted Extensions but do not reboot the system.

2. Edit your label encodings file. The default label_encodings file is /etc/security/tsol/label_encodings. Add the following line in the LOCAL DEFINITIONS section:

   Default Label View is Internal;

x86: Uninstallation of Solaris Trusted Extensions Fails (6460106)

Uninstallation of Solaris Trusted Extensions on x86 systems fails. On rebooting the system, the following error message is displayed:

NOTICE: template type for bge0 incorrectly configured
    Change to CIPSO type for 129.146.108.249
    ifconfig: setifflags: SIOCSLIFFLAGS: bge0: Invalid argument
    NOTICE: bge0 failed: Cannot insert CIPSO template for
    local addr 129.146.108.249
    ip_arp_done: init failed

The system then hangs.

Workaround: Perform the following steps:

1. Uninstall Solaris Trusted Extensions but do not reboot the system.

2. Run the following commands.

   # touch /etc/system # bootadm update-archive

3. Reboot the system.

Using patchadd With the -R Option To Specify an Alternative Root Path From Systems That Are Not Zones Aware Should Be Restricted (6464969)

On systems running a Solaris release that is not zones aware, using patchadd -R, or any command that accepts the -R option to specify an alternate root path for a global zone that has non-global zones installed, will not work.

In contrast with the error message that is displayed by using the luupgrade [-t, -T, -p, -P] command, no error message regarding the use of appropriate command-level restrictions is displayed in this instance.

There is no indication that the -R option did not work. As a result of the failure of the command, Solaris 10 packages or patches are not installed on any of the installed non-global zones.

This problem occurs while installing and uninstalling packages or patches.

The -R option works if the alternate boot environment has configured non-global zones, but no installed non-global zones. However, to avoid a potential problem, or if you are not sure whether there are any installed non-global zones used as the alternate root path, restrict the use of the -R option in all instances.

For more information, see the following man pages :

• patchadd(1M)

• patchrm(1M)

• pkgadd(1M)

• pkgrm(1M)

Workaround 1: Upgrade the OS to at least the Solaris 10 1/06 release.

If you are running the Solaris 10 3/05 release, install the following patches to enable the use of commands that accept the -R option to create an alternate root path:

• Patch ID 119254-19 for SPARC based systems

• Patch ID 119255-19 for x86 based systems

Workaround 2: Restrict the use of the patchadd -R command or any command that accepts the -R option to create an alternate root path.

Instead, boot the alternate root, for example, the Solaris 10 release, as the active OS. Then install and uninstall the Solaris 10 packages and patches without using the -R option.

Upgrade to Solaris 10 11/06 or Changing Specific Device Configurations Might Break PCI/PCIe Hotplug Administration (6466526)

The cfgadm command displays ApIds that might be incorrect or inconsistent with the format that is specified in the cfgadm_pci(1M) man page. This inconsistency occurs under the following circumstances:

• Upgrading to the Solaris 10 11/06 release

• Swapping hardware of PCI or PCI Express (PCIe) attachment points at the same physical location. For example, replacing an expansion chassis at the same location.

No specific error message is displayed. However, the cfgadm command might display one of the following:

• An incorrectly formatted ApId which might work

• A correctly formatted ApId which might not work

If the ApId does not work, then the cfgadm command will display a corresponding error message.

Workaround: Remove all PCI and PCIe links under the /dev/cfg directory and then run the command, devfsadm -C. The PCI and PCIe links are displayed as ApIds in:

cfgadm -s "select=class(pci)"

smosservice or smdiskless Is Broken Due to wbem Issues (6378956)

The smosservice or smdiskless command might not work because of a dependency on JDK^TM 1.5 release.

The following error message is displayed:

 /usr/sadm/bin/smosservice list -u <user> -p <password> Exception in thread "main" 
java.lang.UnsupportedClassVersionError: 
com/sun/management/viperimpl/console/BaseConsoleOptionsManager 
(Unsupported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
       at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
       at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123)
       at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
       at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
       at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
       at java.security.AccessController.doPrivileged(Native Method)
       at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
       at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
       at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

Workaround:

Set the JAVA_HOME variable to point to a JDK 1.5 installation.

# JAVA_HOME=/usr/java

Sun Patch Manager Tool 2.0 Not Compatible With Previous Versions

A system that runs the Sun Patch Manager Tool 2.0 can manage remote systems that run Patch Manager Tool, including Sun Patch Manager Tool 1.0.

However, a system with an earlier version of Patch Manager Tool cannot manage remote systems that run Patch Manager Tool 2.0. Earlier versions include the following:

• Sun Patch Manager Base Software 1.x

• Sun Patch Manager Tool 1.0

Common Information Model/Web Based Enterprise Management (CIM/WBEM) support for Patch Manager Tool does not exist in the Solaris 8 OS. Consequently, remote management with Patch Manager does not apply to Solaris 8 systems.

Sun Remote Services Net Connect Supported Only in the Global Zone

Sun Remote Services (SRS) Net Connect is supported only in the global zone. Error messages are displayed if you perform one of the following actions:

• You install SRS Net Connect in a local zone.

• SRS Net Connect is installed in the global zone at the time a local zone is created.

The error messages are as follows:

*** package SUNWcstu failed to install - 
interactive administration required:

Interactive request script supplied by package
pkgadd: ERROR: request script did not complete successfully

Installation of SUNWcstu was suspended (interaction required).
No changes were made to the system.  

*** package SUNWfrunc failed to install - 
interactive administration required:

Interactive request script supplied by package
pkgadd: ERROR: request script did not complete successfully

Installation of SUNWfrunc was suspended (interaction required).
No changes were made to the system.

Workaround: Ignore the error messages.

Error or Warning Messages Might Be Displayed While Installing Non-global Zones With the zoneadm Command

While installing a non-global zone by using the zoneadm command, error or warning messages might be displayed during package installation. The messages are similar to the following example:

Preparing to install zone zone1.
Creating list of files to copy from the global zone.
Copying 2348 files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize 790 packages on the zone.
Initialized 790 packages on zone.
Zone zone1 is initialized.

Installation of the following packages generated errors: 
SUNWjhrt SUNWmcc SUNWjhdev SUNWnsb SUNWmcon SUNWmpatchmgr

Installation of the following packages generated warnings: 
SUNWj3rt SUNWmc SUNWwbmc SUNWmga SUNWdclnt SUNWlvma SUNWlvmg 
SUNWrmui SUNWdoc SUNWpl5m SUNWpmgr

Problems about package installation are also recorded in /export/zone1/root/var/sadm/system/logs/install_log which contains a log of the zone installation.

Workaround: None.

The non-global zone can still be used even though these messages have been reported. Issues with package installation existed in earlier Solaris Express and Solaris 10 Beta releases. However, no notification about these problems was being generated. Beginning with this Solaris release, these errors are now properly reported and logged.

SPARC: Error Messages Displayed During Dynamic Reconfiguration (6312424)

During dynamic reconfiguration (DR), error messages might be displayed. The messages are displayed if you perform DR while input and output operations are active on devices that are in the DR path. After the messages are displayed, the input and output operations are retried and eventually succeed. The following is a sample that is displayed:

Jul 28 12:23:19 qame10-a scsi: [ID 107833 kern.warning] WARNING:
/ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056fa13,0 (ssd6):
Jul 28 12:23:19 qame10-a 	transport rejected fatal error
Jul 28 12:22:08 qame10-a scsi: [ID 107833 kern.warning] WARNING:
/ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056f9a7,0 (ssd36):
Jul 28 12:22:08 qame10-a 	SCSI transport failed: reason 'timeout':
retrying command

Workaround: None. Ignore the error messages.

Error Messages Displayed by pkgchk After You Remove Patches for Zones (6267966)

The patchadd and patchrm commands work improperly in non-global zones with inherited file systems. Consequently, in those zones, the pkgchk command might generate error messages about packages under the following circumstances:

1. In the global zone, you apply patches for the Solaris 10 zone system by using the patchadd command.

2. You use the patchrm command to remove patches that you just recently applied.

3. In a non-global zone with inherited file systems, you check with the pkgchk command for information about a package in any of the removed patches.

The following sample message is displayed when the pkgchk command is used on SUNWcsu under the circumstances previously listed.

# pkgchk SUNWcsu
ERROR: /usr/lib/inet/certdb
     modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
     file size <36012> expected <42152> actual
     file cksum <37098> expected <19747> actual
ERROR: /usr/lib/inet/certlocal
     modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
     file size <44348> expected <84636> actual

Workaround: None. The errors are harmless. Ignore the error messages.

Race Condition Between EF/kcfd and IPsec Algorithm Availability (6266083)

Systems with the Solaris 10 3/05 HW1 release might cause problems with IPsec. This problem might occur on a freshly installed system or a system that imports a large number of new Service Management Facility (SMF) manifests during the boot. After these booting conditions, IPsec, which is part of svc:/network/initial:default, might be initialized prior to the encryption framework, which is part of svc:/system/cryptosvc:default. Because authentication or encryption algorithms are not available, creation of IPsec security associations might fail with an error message such as the following:

PF_KEY error: type=ADD, errno=22:
Invalid argument, diagnostic  code=40:
Unsupported authentication algorithm

For example, this error might occur when using DR on a Sun Fire E25K system, which involves IPsec services.

Workaround: Before performing operations that use IPsec services, perform the following steps after a boot that imports a large number of new SMF manifests:

1. Issue this command after booting:

   ipsecalgs -s

2. If /etc/inet/secret/ipseckeys exists on the system, also issue this command:

   ipseckey -f /etc/inet/secret/ipseckeys

Now you can perform actions that create IPsec security associations, such as using DR on a Sun Fire E25K system.

This procedure needs to be repeated only when a large number of new SMF manifests are imported during the boot.

Solaris Product Registry Administration Utility Fails to Launch in a Zone (6220284)

If you attempt to launch the Solaris Product Registry administration utility in a zone, the attempt fails. During the zone installation, productregistry, the Solaris Product Registry database, is not duplicated in the zone. Consequently, the utility cannot run in a zone.

Workaround: As superuser, copy the productregistry database to the zone.

# cp /var/sadm/install/productregistry zone_path/var/sadm/install/

In the previous command, zone_path is the path to the root directory of the zone that you created.

Cannot Delete Existing Diskless Clients From the System (6205746)

If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:

Failing with error EXM_BMS.

Workaround: Unshare the /export partition before adding the client.

Net Connect 3.1.1 Installation Fails (6197548)

Installation of Net Connect 3.1.1 fails if you select the product at the beginning of a full Solaris 10 installation. This failure occurs when you are installing by using the Solaris 10 Operating System DVD. At the completion of the OS installation, the following error message is recorded in the Net Connect install log in /var/sadm/install/logs/:

Installation of SUNWSRSPX failed.
Error: pkgadd failed for SUNWsrspx 
Install complete. Package: SUNWsrspx

Workaround: After the OS installation is completed, follow these steps:

1. Insert the Solaris 10 Operating System DVD or the Solaris 10 Software - CD 4.

2. Change to the directory of the Net Connect product.

3. Run the Net Connect installer.

To download the latest version of the Sun Net Connect software and release notes, go to the Sun Net Connect portal at https://srsnetconnect.sun.com.

SPARC: smosservice delete Command Does Not Successfully Remove All Directories (6192105)

If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.

Workaround: Follow these steps.

1. Make sure that no clients exist that use the service.

   # unshare /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/Solaris_10_sparc.all # rm -rf /export/exec/.copyofSolaris_10_sparc.all # rm -rf /export/.copyofSolaris_10 # rm -rf /export/Solaris_10 # rm -rf /export/share # rm -rf /export/root/templates/Solaris_10 # rm -rf /export/root/clone/Solaris_10 # rm -rf /tftpboot/inetboot.sun4u.Solaris_10

2. Remove the following entry from the /etc/bootparams file.

   fs1-24 boottype=:os

   ---

   Note –

   Remove this entry only if this file server does not provide functions or resources for any other services.

   ---

3. Remove the following entry from the /etc/dfs/dfstab file.

   share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr

4. Modify the /var/sadm/system/admin/services/Solaris_10 file.

   • If the file server is not Solaris_10, delete the file.

   • If the file server is Solaris_10, remove all entries after the first three lines. The deleted lines indicate the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.

patchadd Command Does Not Support Installing Patches From an NFS Server (6188748)

If you use the patchadd command to install patches across the NFS from another system, the command fails. The following example shows a patchadd operation that failed and the error message that is displayed:

Validating patches...

Loading patches installed on the system...
[...]
Loading patches requested to install.
[...]
Checking patches that you specified for installation.
[...]
Approved patches will be installed in this order:
[...]
Checking local zones...
[...]
Summary for zones:
[...]
Patches that passed the dependency check:
[...]

Patching global zone
Adding patches...

 Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...
Installing patch packages...

 Patch Patch_ID has been successfully installed.
See /var/sadm/patch/Patch_ID/log for details
 Patch packages installed:
   SUNWroute
[...]

Adding patches...
 The patch directory
 /dev/.SUNW_patches_0111105334-1230284-00004de14dcb29c7
 cannot be found on this system.  

[...]

Patchadd is terminating.

Workaround: Manually copy all of the patches to be installed from the NFS server to the local system first. Then use the patchadd command to install the patches from the directory on the local system where the patches were copied.

lucreate Command Does Not Create RAID-1 Volumes (5106987)

If you use the lucreate command to create RAID-1 volumes (mirrors) that do not have device entries in the /dev/md directory, the command fails. You cannot mirror file systems with the lucreate command unless you first create the mirrors with Solaris Volume Manager software.

Workaround: Create the mirrored file systems with Solaris Volume Manager software, then create the new boot environment with the lucreate command.

For more information about the lucreate command, see the lucreate(1M) or Solaris 10 11/06 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

For more information about how to create mirrored file systems with Solaris Volume Manager software, see Solaris Volume Manager Administration Guide.

SPARC: Stopping the System by Using Keyboard Sequences Might Cause a System Panic (5061679)

If you attempt to stop the system by pressing keyboard sequences such as Stop-A or L1-A, the system might panic. An error message similar to the following example is displayed:

panic[cpu2]/thread=2a100337d40: pcisch2 (pci@9,700000): 
consistent dma sync timeout

Workaround: Do not use keyboard sequences to force the system to enter OpenBoot PROM.

Using the ipfs Command With -W Option Fails (5040248)

The ipfs command saves and restores information about the state of the Network Address Translation (NAT) and packet-filtering state tables. This utility prevents network connections from being disrupted if the system reboots. If you issue the command with the -W option, ipfs fails to save the kernel state tables. The following error message is displayed:

state:SIOCSTGET: Bad address

Workaround: None.

kill -HUP Does Not Always Cause the Agent to Reread the snmpd.conf Configuration File (4988483)

After modifying the contents of snmpd.conf, you can issue the command kill -HUP snmp Process ID. This command stops the snmp process. The command then sends a signal to the System Management Agent's master agent (snmpd) to reread snmpd.conf and implement the modifications that you introduced. The command might not always cause the master agent to reread the configuration file. Consequently, using the command might not always activate modifications in the configuration file.

Instead of using kill -HUP, restart the System Management Agent after adding modifications to snmpd.conf. Perform the following steps:

1. Become superuser.

2. Type the following command:

   # /etc/init.d/init.sma restart

x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757, 5051157)

You are booting a Sun LX50 which has a Service partition and Solaris 10 OS on x86 is installed. Pressing the F4 function key to boot the Service partition, when given the option, causes the screen to go blank. The system then fails to boot the Service partition.

Workaround: Do not press the F4 key when the BIOS Bootup Screen is displayed. After a time-out period, the Current Disk Partition Information screen is displayed. Select the number in the Part# column that corresponds to type=DIAGNOSTIC. Press the Return key. The system boots the Service partition.

Solaris WBEM Services 2.5 Daemon Cannot Locate com.sun Application Programming Interface Providers (4619576)

The Solaris WBEM Services 2.5 daemon cannot locate providers that are written to the com.sun.wbem.provider interface or to the com.sun.wbem.provider20 interface. Even if you create a Solaris_ProviderPath instance for a provider that is written to these interfaces, the Solaris WBEM Services 2.5 daemon does not locate the provider.

Workaround: To enable the daemon to locate such a provider, stop and restart the Solaris WBEM Services 2.5 daemon.

# /etc/init.d/init.wbem stop

# /etc/init.d/init.wbem start

If you use the javax API to develop your provider, you do not need to stop and restart the Solaris WBEM Services 2.5 daemon. The Solaris WBEM Services 2.5 daemon dynamically recognizes javax providers.

Some com.sun Application Programming Interface Method Invocations Fail Under XML/HTTP Transport Protocol (4497393, 4497399, 4497406, 4497411)

If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only Common Information Model (CIM) remote method invocation (RMI) is fully supported. Other protocols, such as XML/HTTP, are not guaranteed to work completely with the com.sun application programming interface.

The following table lists examples of invocations that execute successfully under RMI but fail under XML/HTTP:

Cannot Modify File-System Mount Properties With Solaris Management Console Mounts and Shares Tool (4466829)

The Solaris Management Console Mounts and Shares tool cannot modify mount options on system-critical file systems such as root (/), /usr, and /var.

Workaround: Choose one of the following workarounds:

• Use the remount option with the mount command.

  # mount -F file-system-type -o remount, additional-mount-options \ device-to-mount mount-point

  ---

  Note –

  Mount property modifications that are made by using the -remount option with the mount command are not persistent. In addition, all mount options that are not specified in the additional-mount-options portion of the previous command inherit the default values that are specified by the system. See the man page mount_ufs(1M) for more information.

  ---

• Edit the appropriate entry in the /etc/vfstab file to modify the file-system mount properties, then reboot the system.