Trusted CDE Screen Lock Logs Out the User (6564548)
Cannot Switch Roles on Trusted Java DS (6546892)
Mouse Pointer and the dtfile Icon Are Not Displayed When You Drag the dtfile Icon (6462945)
SMC Updates the tnrhdb File But Does Not Run tnctl to Update the Trusted Host Cache (6471594)
Trusted Stripe Disappears From The Screen After Resolution Change (6460624)
x86: GNOME Applications Fail With dtremote (6278039)
CDE Removable Media Auto Run Capability Removed (4634260)
Solaris PDASync Cannot Delete Last Entry From the Desktop (4260435)
zoneadm install Fails With a ZFS Legacy Mount (6449301)
ZFS and UNIX/POSIX Compliance Issues
fdisk -E Can Sweep Disk Used by ZFS Without Warning (6412771)
ZFS and Third-Party Backup Product Issues
Veritas NetBackup Does Not Back Up and Preserve Files With ZFS/NFSv4 ACLs (6352899)
BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support
ZFS GUI Should Check For /usr/lib/embedded_su at the Beginning of Each Wizard (6326334)
Fails to Sync File System on Panic (6250422)
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)
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
The (ZFS) ARC Allocates Memory Inside The Kernel Cage Preventing DR (6522017)
mpathadm Does Not Display Load-Balance Setting Specific to Device
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)
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)
Multiple Input Method Switcher Applications Appear in Trusted Java DS
Uninstaller Displays Strings Incorrectly in Some Locales (6487062)
Input Method Cannot Be Enabled With Primary Administrator Rights (6475081)
New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)
AltGr Does Not Work As Mode Switcher in Some Russian Locales (6487712)
Arabic Text Not Appearing in ar Locales
L10N Messages Missing When Using localeadm Utility to Add Locales (6423974)
Several Arabic Fonts Do Not Work in GNOME (6384024)
Unable to Switch Input Language on Session-Saved Applications (6360759)
Keyboard Shortcuts in Mozilla in ES Locale Are Unusual and Ambiguous (6288620)
Migration Note to UTF-8 locales
Emails Saved As Portable Format
File Names and Directory Names
Launching Legacy Locale Applications
Cannot Print Documents in Portable Document Format (6239307, 6218079)
Sort Capability in the European UTF-8 Locales Does Not Function Correctly (4307314)
Login Fails on iSCSI Target With Two Portals and One Bad Portal (6476060)
System Domain of Interpretation Is Not Configurable (6314248)
IP Forwarding Disabled by Default in Solaris 10 OS
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 (6365896)
Incorrect Parameters Might Cause Panic in Sun StorEdge T3 (4319812)
Print Services Have Offline Settings by Default (5100134)
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
Unsupported Options in the ddi_dma_mem_alloc(9F) Man Page (6571030)
Changed Man Pages for Solaris Trusted Extensions Are in Reference Manual Only
Failed Unconfigure Command cfgadm Might Succeed Later Without Notice (6483258)
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)
Incomplete List of Contacts in Contact Folder (5088514)
Cannot Login Using GDM Unless Clearance is Set to admin_high (6432114)
Wrong Help Window Opened For Volume Control (6253210)
Cannot Print Certain Documents From the Mozilla Browser
User Preferences Not Fully Compatible
Problems With Online Registration of StarOffice 7 Software (6208829)
Release Notes Do Not Display in Thunderbird Help (6565136)
Trusted Java DS Workspace Does Not Start on Initial Change of Label (6550104)
Nautilus ACL MASK is Not in Sync With Group Permissions (6464485)
strftime(3c) Should Support GNU Extension in %-m And %-d (6448815)
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: GNOME Applications Fail With dtremote (6278039)
Certain View Options Might Cause File Manager to Fail (6233643)
Trusted $HOME Ownership Incorrect When Administrative Role Created (6579845)
SAN 4.4.13 Emulex Error With Patch 119914-12 (6558400)
iscsitgtd Double Frees on Target Creation With an Alias (6554915)
iSCSI Target Coredumps When Running JIST Test Suite (6550844)
zoneadm attach Command Might Fail (6550154)
Deferred Activation Patching (6486471)
Possible Error With 32-bit Applications Getting File System State on Large File Systems (6468905)
x86: Uninstallation of Solaris Trusted Extensions Fails (6460106)
Sun Patch Manager Tool 2.0 Not Compatible With Previous Versions
SPARC: Error Messages Displayed During Dynamic Reconfiguration (6312424)
Error Messages Displayed by pkgchk After You Remove Patches for Zones (6267966)
Race Condition Between 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)
SPARC: smosservice delete Command Does Not Successfully Remove All Directories (6192105)
SPARC: Stopping the System by Using Keyboard Sequences Might Cause a System Panic (5061679)
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
This section describes issues that apply to the Sun Java Desktop System (Java DS) in the Solaris 10 OS.
This section describes issues related to Email and Calendars.
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:
Select the messages you want to attach.
On the Menu bar, choose Action => Forward => Attached.
Alternatively, you can press Ctrl-J to send the messages.
After you change the authentication type for the incoming mail server, Email and Calendar might not work correctly.
Workaround: Restart Email and Calendar.
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.
This section describes login issues.
The login fails when you log in to the Solaris Trusted Extensions Java Desktop Systems (Java DS) 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.
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:
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.
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
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.
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.
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.
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:
Log out of the Java Desktop System.
Click Session and choose Failsafe terminal.
Log in.
In the failsafe terminal window, enter the following commands:
% gnome-cleanup exit
Log in again.
Your GNOME preferences are now reset.
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.
Open a terminal window.
Issue the following command:
% export PATH=/usr/sfw/bin:$PATH
To start the StarOffice software, issue the following command:
% soffice
Complete the StarOffice registration procedure.
The slide bar and the side counter do not work when the Sound Recorder is recording a new.wav file.
Workaround: None.
The release notes in the Thunderbird Help section fail to display. No error message is displayed.
Workaround: Set Firefox as the default browser. When opening Firefox for the first time, the system asks you if you want to set Firefox as the default browser. Select Yes. Then select Edit-> Preferences-> Main-> Check Now.
When you use the Trusted Java Desktop System (Java DS) workspace switcher to change the label of a workspace, the desktop does not start in that workspace. All applications fail to open in that workspace. No error message is displayed.
Workaround: Add the following line to the /usr/openwin/server/etc/TrustedExtensionsPolicy file:
extension MIT-SHM
If the /usr/X11/lib/X11/xserver/TrustedExtensionsPolicy file is present on the system, also add the same line to this file. This change becomes effective on subsequent Trusted CDE and Java DS sessions.
For more information, see the TrustedExtensionsPolicy(4) man page.
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.
The Java DS menu bar and some applications, like Evolution, incorrectly display Chinese date. The incorrect date is displayed in the %-m M %-d D format where M and D are the month and date in Chinese respectively.
Workaround: Perform the following steps:
Backup the /usr/share/locale/LC_MESSAGES/gnome-panel*.mo file.
Download gnome-panel.gnome-2-16.zh_CN.po from http://l10n.gnome.org/POT/gnome-panel.gnome-2-16/gnome-panel.gnome-2-16.zh_CN.po and save it under the /tmp directory.
Edit the file gnome-panel.gnome-2-16.zh_CN.po and replace all occurrences of %-m with %Om, and %-d with %e.
Generate a new gnome-panel.gnome-2-16.zh_CN.po file.
msgfmt -v -o gnome-panel.gnome-2-16.zh_CN.mo /tmp/gnome-panel.gnome-2-16.zh_CN.po
Copy the file back to the /usr/share/locale/LC_MESSAGES/ directory.
Log out of the system and re-login.
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.
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
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.
You cannot use Archive Manager to create the following types of archives:
.arj
.lha
.bzip
.lzop
.zoo
Workaround: None.