Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Release Notes Oracle Solaris 10 8/11 Information Library |
3. Oracle Solaris Runtime Issues
The rstchown Parameter is Obsolete
Recommended Adoption of SHA-256 and SHA-512 crypt Plug-ins for Password Encryption
Trusted Stripe Disappears From the Screen After a Resolution Change (6460624)
ZFS Dynamic LUN Expansion Restriction (6241086)
The config/local_only Property in sendmail Must Not Be Set to true (6970172)
x86: ata Driver Timeouts During Boot (6586621)
zoneadm install Command Fails With a ZFS Legacy Mount (6449301)
ZFS and UNIX/POSIX Compliance Issues
fdisk -E Command Can Sweep Disk Used by ZFS Without Warning (6412771)
BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support Issue
ZFS GUI Should Check for /usr/lib/embedded_su Patch at the Beginning of Each Wizard (6326334)
Failure to Synchronize File System on Panic (6250422)
Upgrading From Some Oracle Solaris 10 Releases Requires Remounting of File Systems
NFSv4 Access Control List Functions Might Work Incorrectly
System Crash Dump Fails on Devices Greater Than 1 TByte in Size (6214480)
Hardware-Related Issues and Bugs
SPARC: System Might Hang if the Elastic Policy is Set (6989192)
System Panic Might Occur During DR operations for Crypto (7048323)
SPARC: Disk Warning Is Displayed When Booting the Oracle Solaris OS (7047435)
SPARC: Dynamic Reconfiguration Operations Fail on an OPL Platform (7060498)
x86: System Shuts Down If ata Disks or Controllers Are Replaced on a Running Machine (7059880)
SPARC: System Panic Might Occur When Executing Bulk Crypto Operations on sun4v T3 Machines (7041435)
Message Signaled Interrupt (MSI-X) Cannot Be Retargeted When the apix Module Is Loaded (7058060)
x64: PCI Subsystem ID Changes in ConnectX Firmware 2.6.0 From Mellanox (6810093)
The ZFS ARC Allocates Memory Inside the Kernel Cage Preventing DR (6522017)
mpathadm Command Does Not Display Load-Balance Setting Specific to Device
Registration Tool Prevents Power Management on Some Frame Buffers (6321362)
Certain USB 2.0 Controllers Are Disabled
Supported USB Devices and Corresponding Hub Configurations
x86: Limitations Exist With Certain Device Drivers in the Oracle Solaris 10 OS
DVD-ROM/CD-ROM Drives on Headless Systems
x86: Manual Configuration Required to Specify Non-U.S. English Keyboards
Contention Exists Between Certain Devices That Share the Same Bus (6196994)
Some DVD-ROM and CD-ROM Drives Fail to Boot the Oracle Solaris 10 OS (4397457)
SPARC: Copy Relocation Does Not Work (7083331)
Swedish Software Translations Note
Multiple Input Method Switcher Applications Appear in Trusted Java Desktop System
New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)
AltGr Key Does Not Work As a Mode Switcher in Some Russian Locales (6487712)
x86: Arabic Text Not Appearing in ar Locales
Several Arabic Fonts Do Not Work in GNOME Desktop (6384024)
Unable to Switch Input Language on Session-Saved Applications (6360759)
Migration Note for UTF-8 Locales
Emails Saved as Portable Format
File Names and Directory Names
Launching Legacy Locale Applications
Hardware for Some Keyboard Layouts Type 6 and 7 Not Available
BIND 9.6 Denies Recursion To Non-Local Networks (7046009)
Configuring Tunnels With the Same Source Address (4152864)
System Domain of Interpretation Is Not Configurable (6314248)
IP Forwarding Disabled by Default in the Oracle Solaris 10 OS
Oracle Solaris Commands and Standards
SPARC: Incorrect Results Are Displayed for the cpustat Command on a T4 1.2 Chip
winbind Command Fetches Only the First 1000 Active Directory Users
Changed Man Pages for Trusted Extensions Are in Reference Manual Only
Bash 3.00 No Longer Sets Some Environment Variables
New ln Utility Requires -f Option
New tcsh Version Rejects setenv Variable Names That Use a Dash or an Equal Sign
STDIO getc Family EOF Condition Behavior Change
Output Columns of the ps Command Have Been Widened
Solaris Volume Manager Does Not Remove Devices Correctly If fdisk Does Not Have Valid Entries
Solaris Volume Manager metattach Command Might Fail
Email and Calendar Application
Problem With Changing Authentication Type (6246543)
Wrong Help Window Opened For Volume Control (6253210)
User Preferences Not Fully Compatible
Nautilus ACL MASK Is Not Synchronized 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
Certain View Options Might Cause File Manager to Fail (6233643)
Package Database Contains Path Names That Do Not Exist (7054481)
SPARC: 64-bit Version of the libsoftcrypto Library Is Slow (7048794)
patchrm Command Is Not Supported After Applying Patch 144500/144501 (7033240)
lucreate Introduces Latency on Slower UFS Systems (7051757)
The Availability Suite Module sdbc Fails to Load During Boot (6952222)
Oracle Solaris 10 9/10 Clock Stops on Oracle VM 2.2 (6952499)
SPARC: FKU 137137-xx Patch Does Not Support Third-Party Volume Manager Software
Sun Patch Manager Tool 2.0 Incompatible With Previous Versions of the Tool
Cannot Delete Existing Diskless Clients From the System (6205746)
SPARC: smosservice delete Command Does Not Successfully Remove All Service Directories (6192105)
4. End-of-Software Support Statements
A. Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 8/11 Release
This section describes localization issues that apply to Oracle Solaris 10 OS.
Swedish software translations are no longer updated since the Solaris 10 8/07 release except for translations provided by communities. Therefore, updated messages are displayed in English.
Workaround: None.
When you log in to the Trusted Java Desktop System with UTF-8 or Asian locales, the Input Method Switcher application, iiim-panel, appears per label by default. Therefore, in a multiple-label environment, multiple iiim-panels appear, which could be confusing to the user.
No error message is displayed.
Workaround: Stop using the iiim-panel. Perform the following steps:
Right-click the iiim-panel and select Preference.
The Input Method Preference Editor, iiim-properties, is displayed.
Select None or Attach to Each Application from the Input Method Status and Switcher Placement list in the General tab.
Click the Apply or OK button.
To switch the input language, you can also use Hotkey. To enable Hotkey, perform the following steps:
Go to the Misc tab in the iiim-properties editor.
Select the Enable Language/Script Choice window using the Hotkey option.
Click the Apply or OK button.
Note - Once Attach to Each Application is selected, the language switcher list will not be displayed for GTK applications. You can switch the input language by using Hotkey.
The 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.
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 are 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. Press Control-Shift to switch input methods.
The AltGr key does not work as a mode switcher for the Russian Xsun layout inru_RU.KOI8-R and ru_RU.ANSI1251 locales.
Choose one of the following workarounds.
Workaround 1: Switch to the ru_RU.UTF-8 or the ru_RU.ISO8859-5 locale.
Workaround 2: Use IIIMF instead of the Russian keyboard layout.
If your x86 system is using Xorg as the default X server, 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 the /usr/dt/config/Xservers file.
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.
When you select certain Arabic fonts in the GNOME desktop, the characters do not display. This problem appears when you select fonts for applications, the desktop, or the window title by 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.
Multiple language input is supported in UTF-8 locales, but the language switch is not working with session-saved applications when mouse button 1 is clicked first after login. This problem occurs with the Java Desktop System. No error message is displayed.
Workaround: Click mouse button 1 on the background workspace or Launch Menu before clicking any application.
When migrating to UTF-8 locales, the files affect the method that you use to import or export data.
Modern email messages 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 do not have a charset tag. If the files are not in UTF-8, you must convert the encoding. For example, to convert a plain text file encoded in Traditional Chinese big5 to UTF-8, you would run the following command:
iconv -f big5 -t UTF-8 input-filename > output-filename
You can also use File System Examiner for the encoding conversion.
You can use 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.
If file names and directory names using multibyte characters are not in UTF-8, you must convert the encoding. 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. 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.
For applications that are not ready to migrate to Unicode UTF-8, you can create a launcher on the 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.
Right-click the panel where you want to place the launcher.
Choose Add to Panel -> Launcher.
Use the following format to type the entry in the Command field in the Create Launcher dialog box:
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, you would type 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
Click OK to create the launcher on the panel.
When you need to run CLI (command-line interface) applications that are specific to a legacy locale, open a erminal window in the legacy locale first and then run the CLI applications in the same erminal window. To open a terminal window in a legacy locale, type the following command:
eng LANG=locale LC_ALL=locale GNOME-TERMINAL –disable-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. Change the encoding through the Set Character Encoding menu in the terminal window. Then, you must also set the LANG and LANG environment variables to the current shell.
Software support for some keyboard layouts has been added to the Oracle Solaris OS. This support gives users greater flexibility for keyboard input by enabling them to modify standard U.S. keyboard layouts for their own language needs.
Currently, no hardware is available for the following keyboard layout types:
|
Choose one of the following workarounds.
Workaround 1: To take advantage of this keyboard support, set up keyboard input using the kbd -s command. For desktop sessions with the UTF-8 locale environment, use the Input Method Preference Editor. If the required keyboard layout is not listed, use Workaround 2.
Workaround 2: Modify the /usr/openwin/share/etc/keytables/keytable.map file. For example, for the Canadian Type 6 keyboard, make the following changes:
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
Reboot the system for the changes to take effect.