x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card
x86: Problems Configuring USB Mouse Device as Extension Device for Use With GNOME On-Screen Keyboard
x86: Support for Intel Integrated i810 and i815 Graphics Chipsets
Arabic Text Not Appearing in ar Locales
Launch Menu Cannot Be Opened With Ctrl-Esc (6340714)
x86: Problems With dtlogin When Using UTF-8 Locales (6334517)
SPARC: Problems Configuring Preferences With the GNOME On-Screen Keyboard (6329929)
x86: GNOME Applications Fail With dtremote (6278039)
Full-Screen Magnification and Keyboard Accessibility Features Not Working (6273030)
Desktop Icons Invisible on Second Desktop System (6211279)
x86: kdmconfig Instructions to Configure Xorg X Server Are Incomplete (6205881)
x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669)
CDE Removable Media Auto Run Capability Removed (4634260)
Solaris PDASync Cannot Delete Last Entry From the Desktop (4260435)
SUNWsdocs Package Needed to Remove Other Documentation Packages
European Locale PDF Documents Available Only Through C Locale (4674475)
ZFS and UNIX/POSIX Compliance Issues
Adding ZFS Patch to a Solaris 10 6/06 System Causes Spurious Warning Messages (6429860)
ufsrestore Does Not Use acl_set() For Setting ACLs (6421216)
fdisk -E Can Sweep Disk Used by ZFS Without Warning (6412771)
x86: BIOS Hangs on Reboot After Using ZFS on Sun Ultra 20 or Sun Fire X2100 (6363449)
ZFS and Third-Party Backup Product Issues
Veritas NetBackup Does Not Back Up and Preserve Files With ZFS/NFSv4 ACLs (6352899)
Legato Networker Needs to Support ZFS/NFSv4 ACLs (6349974)
ZFS GUI Should Check For /usr/lib/embedded_su at the Beginning of Each Wizard (6326334)
du Reports Wrong Size Information on RAID-Z (6288488)
Fails to Sync File System on Panic (6250422)
Need Itinerary so That Interrupted scrub or resilverDoesn't Have to Restart (2136811)
Upgrading From Some Solaris Express or Solaris 10 Releases Requires Remounting of File Systems
NFSv4 Access Control List Functions Might Work Incorrectly
Access Problems Between Solaris NFSv4 Clients and NFSv4 Servers
Using mkfs Command to Create File System Might Fail on Very Large Disks (6352813)
File System Creation Might Fail on Small Slices (6346510)
Undetected Write Errors in NFSv4 Client With Full File System (6346204)
System Crash Dump Fails on Devices Greater Than 1 TByte (6214480)
Using smosservice Command to Add OS Services Results in Insufficient Disk Space Message (5073840)
Hardware-Related Issue and Bugs
Registration Tool Prevents Power Management on Some Framebuffers (6321362)
SPARC: Sun Crypto Accelerator 4000 Board Versions 1.0 and 1.1 Not Supported in Solaris 10 OS
Certain USB 2.0 Controllers Are Disabled
Supported USB Devices and Corresponding Hub Configurations
x86: Limitations Exist With Certain Device Drivers in Solaris 10 OS
DVD-ROM/CD-ROM Drives on Headless Systems
x86: Manual Configuration Required to Specify Non-US English Keyboards
Contention Exists Between Certain Devices That Share the Same Bus (6196994)
hat_getkpfnum() DDI Function Is Obsolete (5046984)
Some Systems With USB 2.0 Hardware Might Hang or Panic (5030842)
x86: Soft System-Shutdown is Not Supported in Solaris OS on x86 (4873161, 5043369)
Some DVD and CD-ROM Drives Fail to Boot Solaris (4397457)
iPlanet Directory Server 5.1 Issues
Installing Directory Server 5.1
Migrating to the Sun Java System Directory Server 5 2005Q1
SPARC: Problems With dbx Debugger While Processing 64-bit Objects (6347707)
System Might Loop When Master CPU Is Changed (4405263)
Deadkeys Not Working With GTK Applications on Xsun in EMEA UTF-8 Locales (6429880)
L10N Messages Missing When Using localeadm Utility to Add Locales (6423974)
IIIMF Packages Might Not be Installed (6388988)
SPARC: Keycode 50 Does Not Work for European Keyboard Layouts (6387317)
Several Arabic Fonts Do Not Work in GNOME (6384024)
Unable to Switch Input Language on Session-Saved Applications (6360759)
Some Language Input Does Not Work Correctly on Non-U.S. Keyboard Layouts (6319383)
Keyboard Shortcuts in Mozilla in ES Locale Are Unusual and Ambiguous (6288620)
Login Screen Marks UTF-8 Locales as Recommended
Emails Saved As Portable Format
File Names and Directory Names
Launching Legacy Locale Applications
Cannot Print Documents in Portable Document Format (6239307, 6218079)
x86: Login Process Might Hang in Certain Asian Non-UTF-8 Locales (6215527)
Special Keyboard Keys Do Not Work (5077631)
Modifier Keys Do Not Function Correctly (4996542)
Chinese and Korean Characters Are Printed In a Box (4977300)
Sort Capability in the European UTF-8 Locales Does Not Function Correctly (4307314)
Memory Leaks with ECC and RSA Cipher Suites (6421471)
iSCSI Initiator Does Not Handle LUN Address Reporting Properly (6377485)
LUN Numbers Greater Than 256 Are Treated Differently by 2-Gbyte and 4-Gbyte QLogic HBAs (6371273)
Wrong MAC Address is Displayed When There is More Than One Ethernet Card (6316245)
SPARC: RTM_IFINFO Message Has Different Sizes on 32-bit and 64-bit Compilations
IP Forwarding Disabled by Default in Solaris 10 OS
Generic LAN Driver Version 3 Fails to Set Field Length of Logical Link Control Frames (6350869)
Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)
Intermittent Errors Might Occur With the Use of DataDigests (5108515)
ATM LANE Subnets for IPv4/IPv6 Might Not Complete Initialization (4625849)
Nonpassword Logins Fail With pam_ldap Enabled
Incorrect Parameters Might Cause Panic in Sun StorEdge T3 (4319812)
Print Services Have Offline Settings by Default (5100134)
keyserv Daemon Disables Some File System Services (5084183)
Login Prompts Sometimes Appear Before File Systems Are Mounted (5082164)
System Does Not Respond to Smart Card (4415094)
Edit Config File Menu Item in Smartcards Management Console Does Not Work (4447632)
Solaris Commands and Standards
Bash 2.0.5b No Longer Sets Some Environment Variables
New ln Utility Requires -f Option
New tcsh Rejects setenv Variable Names That Use a Dash or an Equals Sign
STDIO getc Family EOF Condition Behavior Change
Output Columns of the ps Command Have Been Widened
Command ping -v Does Not Work on IPv6 Addresses (4984993)
Solaris Volume Manager metattach Command Might Fail
Solaris Volume Manager metassist Command Fails in Non-English Locales (5067097)
Volume Creation Fails in Systems With Unformatted Disks (5064066)
Solaris Volume Manager metadevadm Command Fails if Logical Device Name No Longer Exists (4645721)
Solaris Volume Manager metarecover Command Fails to Update metadb Namespace (4645776)
Problems With Using Multiple Attachments (6260583)
Problem With Changing Authentication Type (6246543)
Problems When Saving Attachments With Localized Content (6204976)
Incomplete List of Contacts in Contact Folder (5088514)
Remote Connection Problems (6203727)
Wrong Help Window Opened For Volume Control (6253210)
Cannot Print Certain Documents From the Mozilla Browser
Cannot Specify User Preferences for Roaming Access in Mozilla Browser (6200999)
Keyboard Shortcuts Fail (6192644)
User Preferences Not Fully Compatible
GNU Image Manipulation Program Missing From the Graphics Menu (6209566)
Problems With Online Registration of StarOffice 7 Software (6208829)
Volume Control Option Not Working
Outdated List of Allowed Applications for Solaris OS (6267922)
Problems When Using Keyboard Indicator (6245563)
Certain View Options Might Cause File Manager to Fail (6233643)
CD Quality, Lossless Mode Fails at Start of Recording (6227666)
Cannot Delete Files Outside of Home Directory (6203010, 5105006)
Problems Creating Certain Types of Archives (5082008)
Cannot Type Multibyte Characters in Text Editor 2.9.1 (4937266)
smosservice or smdiskless Is Broken Due to wbem Issues (6378956)
Sun Patch Manager Tool 2.0 Not Compatible With Previous Versions
Sun Remote Services Net Connect Supported Only in the Global Zone
Adding Regions Fails With the localeadm Command (6350486)
SPARC: Error Messages Displayed During Dynamic Reconfiguration (6312424)
Error Messages Displayed by pkgchk After You Remove Patches for Zones (6267966)
Race Condition Between EF/kcfd and IPsec Algorithm Availability (6266083)
Solaris Product Registry Administration Utility Fails to Launch in a Zone (6220284)
Cannot Delete Existing Diskless Clients From the System (6205746)
Net Connect 3.1.1 Installation Fails (6197548)
x86: Default C Library Might Cause Boot Failure When You Install Solaris Flash Archives (6192995)
SPARC: smosservice delete Command Does Not Successfully Remove All Directories (6192105)
patchadd Command Does Not Support Installing Patches From an NFS Server (6188748)
lucreate Command Does Not Create RAID-1 Volumes (5106987)
Devices Not Immediately Available in Fabric Zones in a Storage Area Network (5077933)
SPARC: Stopping the System by Using Keyboard Sequences Might Cause a System Panic (5061679)
Using the ipfs Command With -W Option Fails (5040248)
kill -HUP Does Not Always Cause the Agent to Reread the snmpd.conf Configuration File (4988483)
x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757, 5051157)
4. End-of-Software Support Statements
A. Table of Integrated Bug Fixes in the Solaris 10 Operating System
The following bugs in Solaris 10 OS apply to the Common Desktop Environment (CDE).
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:
Log in to a command-line session.
If you are using the GNOME Display Manager, follow these steps:
Log in to a session as superuser.
At the prompt, type svcadm disable application/gdm2-login .
Log in again as superuser.
If you are using dtlogin, follow these steps:
In the dtlogin window, click Options and select Command Line Login.
Log in as superuser.
Create a new xorg.conf file.
# /usr/X11/bin/Xorg -configure
The command creates the file xorg.conf.new in the root (/) directory.
Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.
# cp /xorg.conf.new /etc/X11/xorg.conf
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.
Look for the following line under the ServerLayout section:
Screen 0 "Screen0" 0 0
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.
Save the changes.
Reboot the system from the appropriate command-line session:
If you are using GDM, perform the following:
Type svcadm enable application/gdm2-login.
Reboot the system.
If you are using dtlogin, reboot the system and log in.
Start the Gnopernicus screen reader.
Change the Startup Mode to Magnifier.
Click Preferences, then select Magnifier.
Click Add/Modify.
Assign the following values for Magnifier preferences:
For Source: 0.1
For Zoomer Placement:
Left and Top: 0
Bottom and Right: maximum
Click Apply.
Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.
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.
Log in as superuser.
While the USB mouse device is unplugged, type the following in a terminal window:
# ls -l /dev/usb/hid*
Connect the USB mouse and type the previous command again.
Record the path of the USB mouse that is displayed on the screen.
Log in to a command-line session.
If you are using the GNOME Display Manager, follow these steps:
Log in to a session as superuser.
At the prompt, type svcadm disable application/gdm2-login.
Log in again as superuser.
If you are using dtlogin, follow these steps:
In the dtlogin window, click Options and select Command Line Login.
Log in as superuser.
Create a new xorg.conf file.
# /usr/X11/bin/Xorg -configure
The command creates the file xorg.conf.new in the root (/) directory.
Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.
# cp /xorg.conf.new /etc/X11/xorg.conf
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.
Save the file and exit.
Reboot the system from the appropriate command-line session:
If you are using GDM, perform the following:
Type svcadm enable application/gdm2-login.
Reboot the system.
If you are using dtlogin, reboot the system.
Log in to the accessible UI user's account.
Enable Assistive Technology Support by clicking Launch Menu => Preferences => Accessibility => Assistive Technology Support.
Log out of the system then log in to the accessible UI user's account again.
Open a terminal window and type the following command:
% /usr/sfw/bin/gok --select-action=switch1
In the GOK window, click GOK and select Preferences.
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.
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.
Click OK.
Exit GOK and then repeat steps 14-17.
The warning message is no longer displayed.
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:
Become superuser.
Run the program to configure keyboard, display, and mouse.
# kdmconfig
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.
If the Intel i810 and i815 Chipsets are not automatically selected, select the Change Video Device/Monitor option.
On the Video Device Selection screen, select the Intel i810/i815 (4MB) option.
Continue to select other kdmconfig options.
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.
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
Reboot the system.
Alternatively, you can log in to ar_EG.UTF-8 or other UTF-8 locales.
Problems might occur if you use the AT keyboard to start the following assistive technologies in the Sun Java Desktop System (Java DS). Default time settings might cause the use of key combinations to fail to start these technologies:
GNOME On-Screen Keyboard (GOK)
Magnifier
Speech
Workaround: Follow these steps to start these technologies by using the keyboard when you log in.
Open the /etc/X11/gdm/modules/AccessKeyMouseEvents file.
Navigate to the line that defines the default minimum and maximum time limits for keystrokes.
For example, for GOK, the line is the following:
Controlk 1 1000 10000 gok --login --access-method=directselection
Modify the line by performing the following:
Change the minimum and maximum time settings.
Ensure that you include the correct path for GOK, /usr/sfw/bin/gok.
After you have completed the changes, the sample line should appear as follows:
Controlk 1 10 100 /usr/sfw/bin/gok --login --access-method=directselection
A problem occurs if you configure the Magnifier with two virtual or physical video devices in the following manner:
The Magnifier's source set is :0.1.
The Magnifier's target set is :0.0.
In this configuration, the key combination Ctrl-Esc cannot open the Launch menu on the magnified second desktop system.
Workaround: None.
If you upgrade an x86 based system from Solaris 9 9/04 release to any release of the Solaris 10 software, the login program might not work. The problem occurs when you select any UTF-8 locale in the dtlogin GUI. When the error occurs, the GUI generates a core dump.
Workaround: Do not select any UTF-8 locale from the Language pull-down menu under Options.
Software problems affect the use of extended devices such as a second mouse device or a USB head tracker with the GNOME On-Screen Keyboard (GOK). Consequently, the user preferences Dwell Selection and Direct Selection cannot be set by using GOK. Instead, you need to set these user preferences by using a physical keyboard and mouse device.
Workaround: After you have set the system to use an extended device, perform the following procedures in sequence.
First, set GOK to ensure that the core pointer is controlled by the primary mouse device. Other extended devices are then reserved for use by AT applications. Follow these steps when starting GOK for the first time:
Start GOK.
In the window where Sticky Keys have been activated, press Enter.
In the window that prompts you to use core pointer mode, use the arrow keys to highlight Cancel, then press Enter.
To set user preferences, click GOK and select Preferences.
Configure Dwell Selection or Direct Selection.
To configure Dwell Selection, follow these steps:
Click the Access Methods tab.
Choose Dwell Selection from the Method drop-down menu.
Click the Actions tab and perform the following:
Choose Dwell from the Name drop-down menu.
Check that Activate on Dwell is selected for Behavior.
Check that Other input device is selected for Event Source.
Click Apply.
In the Actions tab, perform the following:
Choose Mouse Pointer from the Name drop-down menu.
Check that Activate on Enter is selected for Behavior.
Click Apply, then click OK.
Exit the GOK window.
Log out and log in again.
To configure Direct Selection, follow these steps:
Click the Access Methods tab.
Choose Direct Selection from the Method drop-down menu.
From the Activate drop-down menu, choose Switch1 to use mouse button 1 on the second mouse.
Click Apply, then click OK.
Exit the GOK window.
Log out and log in again.
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
On your Java Desktop System software, you cannot set up the following:
Full-screen magnification
Keyboard accessibility features
Workaround: Perform the following steps:
Open the /etc/X11/gdm/gdm.conf file.
Depending on your system's platform, perform the following:
On SPARC based systems:
Look for the line in the file that begins as follows:
command=/usr/openwin/bin/Xsun
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:
Look for the line in the file that begins as follows:
command=/usr/X11R6/bin/Xorg
Append the following modification to the line:
+kb +accessx
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.
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).
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
In the custom JumpStart rules file, include the finish script in the rules entry for systems of the type that you want to install.
Perform the custom JumpStart installation.
For instructions about how to perform a custom JumpStart installation, see the Solaris 10 6/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.
A problem occurs if you configure the Magnifier with two virtual or physical video devices in the following manner:
The Magnifier's source set is :0.1.
The Magnifier's target set is :0.0.
In this configuration, no icons appear on the screen of the second desktop system.
Workaround: None.
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 #
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:
Create an xorg.conf file with one of these commands:
/usr/X11/bin/Xorg -configure
/usr/X11/bin/xorgconfig
/usr/X11/bin/xorgcfg
Edit the resultant xorg.conf file with the necessary changes.
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.
Note - Xorg command line options can override xorg.conf settings. See the man pages for more details about options to use with Xorg.
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.
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.
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.