Chapter 1 Solaris Express Developer Edition Issues and Bugs

This chapter describes installation and runtime issues and bugs that are known to be problems in the current release. All of the following issues and bugs apply to the Solaris Operating System. Issues include information that you should know about, including prerequisites, tips, troubleshooting hints, and bugs. Bugs are a subset of issues, which have tracking numbers that are shown in parentheses. For updates on bugs published in these release notes, go to the SunSolve^SM web site. For the complete list of issues that apply to the Solaris 10 OS, see the Solaris 10 Release Notes at http://docs.sun.com.

This document includes descriptions of specific issues that you might encounter when performing upgrades. In general, problems might potentially occur if you use upgrade methods with Solaris Express releases. These problems might require you to perform an initial installation and reconfiguration of your system.

Solaris Express Developer Edition 1/08 Issues

The following issues apply to the Developer 1/08 release.

x86: Solaris Installation Might Fail When Whole Disk Option Is Selected (6652417)

Installation of the Developer 1/08 release might fail when the whole disk option is selected. This failure occurs due to an fdisk error. The following error message is displayed:

ERROR: At least one 30 Mbyte Solaris fdisk partition is required on a selected drive
ERROR: System installation failed

Workaround: Perform the following steps:

1. Restart the installation of the OS. Reboot the system or type install-solaris on the command line.

2. Choose the default disk option or partition the disk option on the disk screen.

Installation of the Developer 1/08 OS Fails on Acer FR 5000/1000 (6643143)

Installation of the Developer 1/08 OS fails on Acer FR 5000/1000 machines. The following error message is displayed:

configuring /dev
ata_id_common: BUSY status 0x80 error 0x80
ata_id_common: BUSY status 0xfe error 0x0
ata_id_common: BUSY status 0x80 error 0x80
ata_id_common: BUSY status 0xfe error 0x0
atapi_start_cmd: drive select failed
WARNING: /pci@0,0/pci-ide@14,1/ide@0 (ata2):
timeout: early timeout, target=0 lun=0
atapi_start_cmd: drive select failed
WARNING: /pci@0,0/pci-ide@14,1/ide@0 (ata2):
timeout: early timeout, target=0 lun=0

Workaround: Perform the following steps:

1. Boot your system using the -k option so that kmdb is loaded at the boot process. Use the -d boot option to request a debugger breakpoint prior to starting the kernel.

   ok boot -kd

2. Set a breakpoint at the [0]>kmdb debugger prompt:

   ::bp ata`ata_init_controller+0x165

3. Once the breakpoint is hit, print the general-purpose register $r and verify that the $eax, or the $ebx, contains a valid ata_ctl_t structure:

   <address>::print -a ata_ctl_t

4. Take the address of the ac_timing_flags and set the value from 0x0 to 1:

   <address>/W 1

   You might hit the breakpoint more than once, but it is sufficient if you set the ac_timing_flags value once.

5. Resume upgrading your OS.

For more information on these commands, see the Solaris Modular Debugger Guide.

x86: Xorg Does Not Use the RadeonHD Driver Without the xorg.conf File (6642276)

The Developer 1/08 release includes a video driver for ATI Radeon X1000 and ATI Radeon HD2000 series graphics cards and chipsets. Xorg will not detect and use the new driver unless it is specified in the xorg.conf configuration file. Xorg attempts to use the VESA driver instead, which might not work on all Radeon graphics devices. No error message is displayed.

Workaround: Type the /usr/X11/bin/Xorg -configure command to generate a /etc/X11/xorg.conf file after installation. Verify that the xorg.conf configuration file specifies the RadeonHD driver.

Empty negative_sign in en_US Locale (6618050)

The locale data for existing European and Middle East and African (EMEA), Central and South American, and Oceania locales are migrated to Common Locale Data Repository (CLDR) to achieve maximum compatibility across platforms. Existing applications might see different formats for locale sensitive data when you upgrade from Solaris 10 to the Solaris Express release.

Workaround: Customize the Solaris locales. For instructions on how to customize Solaris locales, see the tech tips at http://developers.sun.com/dev/gadc/techtips/locale_customization.html.

PRODRM Has Problems Deleting prodreg Entry For Solaris Trusted Extensions (6616592)

While upgrading Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the current Developer 1/08 release, the prodreg entry for Solaris Trusted extensions will not be removed. No error message is displayed.

Workaround: After upgrading Solaris Trusted Extensions to the current release, remove the prodreg entry manually as follows:

# prodreg unregister -f -r -u "Solaris Trusted Extensions" -i 1

Solaris Trusted Extensions Upgrade Issues (6616585)

While upgrading Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07 release to the current Developer 1/08 release, unwanted localized Solaris Trusted Extensions packages are installed on your system. This bug occurs because the Solaris Trusted Extensions installer in the Solaris 10 11/06 or Solaris 10 8/07 releases installs localized packages by default. No error message is displayed.

Workaround: Before upgrading Solaris Trusted Extensions to the current release, remove the following localized Solaris Trusted Extensions packages:

Remote Multilevel Login From the Login Screen Is Not Supported in Solaris Trusted Extensions (6616030)

The Remote Login item on the Options menu on the login screen cannot be used to remotely log in to a multilevel Solaris Trusted Extensions system. When the label of your system is the same as the label that has been assigned to an unlabeled system, you can log in remotely to that unlabeled system.

Workaround: To log in remotely, see the instructions in Chapter 14, Remote Administration in Trusted Extensions (Tasks), in Solaris Trusted Extensions Administrator’s Procedures.

gDesklets Fails to Start (6608943)

When you log in to the system as a new user, gDesklets fails to start. The following error message is displayed:

bash-3.00$ gdesklets shell

You're running gDesklets for the first time.
gDesklets will start a requirements check now...

Checking requirements:
 - sys ... found
 - xml.parsers.expat ... found
 - xml.sax ... found
 - gtk ... found
 - ORBit ... found
 - bonobo.ui ... missing
Version check failed.

bonobo python bindings are required.

Workaround: Perform the following steps:

1. Change to your home directory:

   cd <home_directory>

2. Type the following command:

   mkdir .gdesklets

Reboot Now Button Is Unresponsive (6270371)

After installation of the Solaris OS, the Reboot Now button does not work.

Workaround: Perform the following steps:

1. Open a terminal window.

2. Type the following commands:

   # touch /tmp/.instsuccess # pkill -9 java

The system reboots and does not require CDs.

SPARC: NFS/RDMA Connection Errors (6229077)

There might be connection errors between an NFS server and client while using Remote Direct Memory Access (RDMA). Because of these errors the buffer pool resources are exhausted and the system panics. The following error message is displayed:

rpcib: WARNING: rib_rbuf_alloc: No free buffers!

Workaround: Choose one of the following workarounds:

• Configure the NFS server to enable TCP. In the /etc/default/nfs file, change (NFSD_PROTOCOL=tcp).

• Mount the NFS file system from the client side with the proto=tcp mount option.

For more information, see the mount_nfs(1M) and nfs(4) man pages.

NetBeans Dynamic Tracing GUI Plug-in

The NetBeans^TM Dynamic Tracing (DTrace) GUI plug-in is installed during the installation of the NetBeans 6.0 and Sun Studio software. The plug-in should be configured manually before using it.

Workaround: To use the DTrace GUI plug-in, copy the DTrace scripts from the /opt/dtrace-gui to your home directory:

cp -r /opt/dtrace-gui/DTraceScripts $HOME/
chmod -R 755 $HOME/DTraceScripts

The installation of the Dtrace GUI plug-in is now complete.

For more information about this plug-in, see the /opt/dtrace-gui/doc/NetBeans_DTrace_GUI_Plugin.html file. This file describes how to set privileges in the /etc/user_attr file, and how to start the Dtrace GUI. Ensure that you start NetBeans or Sun Studio IDE from a different shell than the shell you use to set privileges.

Build Number Mismatch Between uname -a Output and /etc/release Contents

The uname -a command displays the build number of the kernel as Build 79a. However, the contents of /etc/release is Build 79b which is the build number of the final assembly of the Developer 1/08 OS.

Workaround: None.

x86: Solaris JumpStart Fails

Solaris JumpStart^TM goes to interactive mode if the netmask value in the sysidcfg script is defined. No error message is displayed. The sysidtool starts due to missing network data.

Workaround: Do not specify the netmask value in the sysidcfg script.

GTK+ Issues With JDK

The Sun Studio IDE might have display problems while loading GTK look and feel libraries. These problems are due to a JDK^TM 6 Update 3 bug. Following are examples of the display problems faced:

• Icons in the Run menu item partly hide the labels

• The Debug toolbar is twice as big as the Build toolbar

Workaround: Use an alternate version of JDK. For example:

% sunstudio --jdkhome /usr/jdk/jdk1.5.0_13

Solaris Express Developer Edition 9/07 Issues

The following issues apply to the Developer 9/07 release.

x86: Vista Multiboot Installation Might Fail (6598208)

Windows Vista fdisk program has a new approach to allocation of extra sectors on a disk drive. Vista allocates space in multiples of 2048 sectors. This change affects the Developer 9/07 multibooting process for some laptops that have Vista pre-installed. The fdisk command reports errors during installation while reading the existing partition table.

While installing the Developer 9/07 release on a system that has Windows Vista, one of the following two failures might occur:

• Install might fail with the following error message:

  Not enough free space

• fdisk might fail with the following error message:

  fdisk: Cannot Create partition table

Confirm that the problem exists by using the following command:

fdisk -d <device>

For example:

# fdisk -d c0d0p0
  Physical Geometry:
    cylinders[30400] heads[255] sectors[63]
    sector size[512] blocks[488376000] mbytes[896]
  Virtual (HBA) Geometry:
    cylinders[30400] heads[255] sectors[63]
    sector size[512] blocks[488376000] mbytes[896]
  Partition Table Entry Values:
  SYSID  ACT   BHEAD  BSECT  BEGCYL  EHEAD  ESECT  ENDCYL  RELSECT  NUMSECT
  191    128   0      1      1       254    63     1023    16065    488359935
  100    0     0      0      0       0      0      0       100      100   
  100    0     0      0      0       0      0      0       100      100  
  100    0     0      0      0       0      0      0       100      100 

The maximum disk capacity is shown in the blocks as 488376000. The highest sector allocated is calculated from the partition table 16065 + 488359935 which is 488376000. If the highest sector allocated is greater than the disk capacity then the problem exists.

If Solaris is not installed on this system, you can boot using the install CD or DVD and early in the install process select the option to exit to shell.

Workaround: Create a recovery CD of the affected hard disk partitions. Perform the following steps:

1. Boot Windows Vista.

2. Shrink the last partition. Go to Windows -> Control Panel -> System Maintenance -> Administrative Tools -> Create and format hard disk partitions.

3. Right-click on the last partition on the right and select Shrink Volume. Shrink the volume by about 9 Mbytes.

   Given the difference between the Vista fdisk calculations and the Solaris installer fdisk calculations, an adjustment of 9 MBytes to the existing size of the last Vista partition will resolve the Solaris installer errors.

4. Reboot the system and install the Solaris OS.

Unexpected European Locales Are Installed (6594145)

Using new Solaris streamlined installer, if you select any of European language support, including English, some other European locales are also installed because of the current geographic based packaging. No error message is displayed.

Workaround: None.

Sun4U Systems Lose Network Access After CPR Resume (6593956)

After resuming from a suspend operation, Sun4U^TM systems with hme will lose network access. The Ultra 10, Ultra 60, and Ultra 80 systems lose communications and cannot ping or be pinged. No error message is displayed.

Workaround: Choose one of the following workarounds:

• Do not use the suspend command by disabling system wide power management.

• After resuming from a suspend operation, use the command snoop -d hme0 -c1.

Prompt Messages for Logout and Shutdown Wrongly Translated in Chinese and Korean Locales (6592664)

This bug affects simplified Chinese and Korean users. When a user wants to log out or shut down the system, a dialog is displayed with one of the following messages:

You will be automatically logged out in 60 seconds

Or:

The system will be automatically shutdown in 60 seconds

The simplified Chinese and Korean translations of these messages are not meaningful. No error message is displayed.

Workaround: Download the gnome-panel.mo from the OpenSolaris community and replace the original gnome-panel.mo with the downloaded one. Perform the following steps:

1. Download the l10nmessages-vermillion_*.tar file from http://dlc.sun.com/osol/jds/downloads/current/.

2. Replace the original gnome-panel.mo file with the SUNWgnome-l10nmessages-zhCN/reloc/share/locale/zh/LC_MESSAGES/gnome-panel.mo.

The messages will then be in English.

x86: Signal 11 SIGSEGV Terminates After RTC Startup (6584707)

Runtime Checking (RTC) fails in the Developer 9/07 release. RTC instruments memory, access instructions for access checking. These instructions are handled by a SIGSEGV handler at runtime. Since RTC requires its own SIGSEGV handler and signal alternate stack, attempts to install a SIGSEGV handler or sigaltstack will either be ignored or result in an EINVAL error. SIGSEGV handler calls cannot be nested. The following error message is displayed:

terminating signal 11 SIGSEGV

Workaround: Use the rtc skippatch command to skip instrumentation of the affected function.

For example, the following dbx commands workaround the nested segv problem:

rtc skippatch libc.so -f lrw_rdlock lrw_unlock lrw_wrlock _lock_try
rtc skippatch libc.so -f read_lock_try read_unlock_try write_lock_try
write_unlock_try
rtc skippatch libc.so -f queue_unlink mqueue_spawner thread_queue_dump
rtc skippatch libc.so -f thread_queue_fifo thread_queue_spin
thread_queue_verify
rtc skippatch libc.so -f __rw_unlock __rw_trywrlock __rw_workerscnt
rtc skippatch libc.so -f __rwlock_destroy __rwlock_init

x86: Unnecessary I/O Resource Warnings on Some Machines (6573171)

On some machines, for example Sun V40z, and laptops, for example Acer Ferrari 5000, you might see warning messages about booting with I/O resources. These warnings indicate potential failure on hot-pluggable add operations on the slots displayed in the warning messages.

However, on some machines these warnings are inaccurate and invalid when hot-plugging is not supported on the displayed slots. Ignore the warnings when hot-plugging is not supported.

When hot-plugging is supported, the warnings are valid and you might experience a hot-pluggable operation failure on the specified bridge slots. These types of failures do not affect the current state or functionality of the system in any way.

The examples below show various warning messages that are displayed:

• WARNING: out of I/O resources on bridge: bus 0x20, dev 0x3, func 0x0, for secondary bus 0x23 WARNING: devices under bridge bus 0x20, dev 0x3, func 0x0 will not be assigned I/O ports

• WARNING: detected unsupported configuration: non-empty bridge (bus 0x0 dev 0x7 func 0x0) without I/O resources assigned by bios for secondary bus 0x7

• WARNING: devices under bus 0x0, dev 0x7, func 0x0 will not be assigned I/O ports

Workaround: None.

x86: Incorrect Disk Size Causes libspmistore.so Calls Faults (6570738)

fdisk reports an incorrect size. This error makes the last partition appear to extend beyond the drive limits. Installation might fail or default to using the entire disk. The following error message is displayed:

Installation can not create Solaris fdisk partition (c1t0d0p0),
causing installation failure.
Or, invalid fdisk partition causes installation to overwrite the entire disk.

Workaround: Choose one of the following workarounds:

• Move the last partition by using gparted or a similar tool, so the partition fits within the drive size limit as reported by fdisk. This change enables the installation to complete.

• For Windows Vista systems which have recovery partitions, which use NTFS, use the Vista disk partitioning tool to shrink the last partition on the disk. his shrinking ensures that the partition size does not exceed the drive size limit. Shrinking the last partition by about 1 Mbyte enables complete installation.

x86: gnome—about Error Message (6561499)

After installation, the following error message is displayed:

application gnome-about has crashed.

This error message may be ignored.

Workaround: None.

Menu Items Displayed in English When Logged in With Chinese Locale (6555226)

Some menu items and many GNOME On-Screen Keyboard (GOK) UI items are displayed in English when logged in with the Chinese locale. The menu items listed in All Applications are in English. No error message is displayed.

Workaround: Choose one of the following workarounds:

• Choose the zh_CN.xxx locale instead of the zh locale.

• Modify the /usr/dt/config/Xinitrc.jdsfile as follows:

  1. Locate the following code in the file:

     export G_FILENAME_ENCODING=@locale,UTF-8 export G_BROKEN_FILENAMES=yes (2)

  2. Insert the following code before code in step 1:

     if [ "x$LANG" = "xzh" ] ; then export LANGUAGE=zh:zh_CN.EUC fi

  3. Save the file and log in again to the system.

512 Mbytes Install Option (6512362)

512 Mbytes of memory is insufficient to install the Solaris Express Developer Edition GUI installer. You need at least 768 Mbytes of memory to install the Developer release.

Workaround: Choose one of the following workarounds:

• x86 systems: In the GRUB menu, choose the Solaris Express Serial Console ttyb installation option (#4). This option provides a text-based installation that works with 512 Mbytes of memory. This installation includes only the operating system and not the developer tools. You can add the developer tools after the installation.

• SPARC systems: Use the following installation command:

  ok boot cdrom - text

  This option also provides a text-based installation that works with 512 Mbytes of memory. This installation will include only the operating system, not the developer tools. You can add the developer tools after the installation.

For more information about these installation options, see the Solaris Express Installation Guide: Basic Installations.

Help Document Only Contains Two Topics When in Locales Other Than C/POSIX (6412835)

When you log in to the Solaris OS and choose Help from the Launch menu, a window with 12 topics on the left side is displayed. While in locales other than C/POSIX, only two topics are displayed instead of 12. The displayed topics are:

• Manual pages

• GNU Info pages

No error message is displayed.

Workaround: Perform the following steps:

1. Log in as the root user.

2. Use the following commands:

   - scrollkeeper-update -q - cp -rf /var/lib/scrollkeeper/C /var/lib/scrollkeeper/xx_yy.zzz

   xx_yy.zzz stands for the locale name with which you log in.

x86: Sun Studio Express June 2007 and NetBeans Default Browser Not Found (6512279)

The Developer Guide HTML page that is displayed when you first log in as a user describes Getting Started documentation within Sun Studio 12 and NetBeans 5.5 applications as a way to learn about these products. The text on the right-hand side of this HTML page includes:

• Launch Sun Studio Express and follow the Getting Started Tutorial within the IDE

• Launch NetBeans 5.5 and select the Getting Started within the IDE

There are two issues with the above instructions. The issues and workarounds follow:

• The correct name of the Sun Studio document is Quick Start Guide, not Getting Started Tutorial and is found under the Help menu. No workaround is needed for this issue.

• Sun Studio and NetBeans IDEs expect to find Mozilla at /usr/dist/exe/. The Solaris Express Developer Edition includes the Firefox browser and not Mozilla. In order to access the Getting Started documents or any documentation on the internet, both Sun Studio and Netbeans must specify Firefox as the browser to use.

  Workaround: In order to select Firefox as the browser perform the following steps:

  1. Click on the Tools menu item in the application's menu bar and select Options.

  2. A dialog box is displayed with Options as the title. In the General section, search for the following line:

     *Web Browser*: Mozilla

     Click on the right hand arrow following the box containing Mozilla and select Firefox.

  3. Click on the OK box.

  Select the Getting Started document or any internet link within the application to test whether the Firefox browser is used.

  ---

  Note –

  If you do select the Getting Started documentation or other link with Mozilla still set as the browser, you will see a dialog box explaining what to do to correct this problem. Ensure that you use the above instructions instead of the ones in the dialog box.

  ---

Changes to uid_t and gid_t Types in the Developer 9/07 Release

To promote compatibility with other operating systems, the uid_t and gid_t types have been changed from long (32-bit binaries) and int (64-bit binaries) to the uint32_t type. For more information about this feature, see uid_t and gid_t Type Changes in Solaris Express Developer Editicon What’s New.

The following are the consequences of these changes:

Impact to Newly-compiled C binaries:

When code is recompiled, standard development practices should catch any problems that are caused by changes in the uid_t and gid_t type.

Problem areas to be aware of include the following:

1 #include <unistd.h>
2 #include <stdlib.h>
3 #include <stdio.h>
4
5 int
6 main(void)
7 {
8 uid_t negone = -1;
9
10 if (getuid() < 0)
11 exit(1);
12
13 (void) setreuid(negone, getuid());
14
15 (void) printf("%ld\n", getuid());
16
17 return (0);
18 }

• The following warning is generated by Sun's Studio 11 compiler:

  "uid.c", line 8: warning: initializer does not fit or is out of range: -1"

• The following warnings are generated by Studio 11 lint:

  ((8) warning: constant truncated by assignment

  (8) warning: initializer will be sign-extended: -1

  (10) warning: suspicious comparison of unsigned with 0: op "<"

  function argument ( number ) type inconsistent with format

• The following warnings are generated by gcc -Wall -Wextra:

  uid.c:10: warning: comparison of unsigned expression < 0 is always false

  uid.c:15: warning: long int format, uid_t arg (arg 2)

Newly-compiled C binaries can be intermingled with old objects and system objects. The size of the type has not changed.

Impact on C++ code.

The change in the uid_t and gid_t type results in different name mangling for C++ functions and objects.

As with C binaries, C++ binaries and libraries continue to function as before. The exception is when libraries contain interfaces that use uid_t and gid_t. In this instance, the libraries that contain these interfaces, and the applications that use these interfaces, would need to be recompiled at the same time.

Because the Solaris OS does not expose C++ interfaces of this nature, no incompatibilities with Solaris libraries are expected.

Solaris Express Developer Edition 5/07 Issues

The following issues apply to the Developer 5/07 release.

Firefox Crashes When Browsing With Assistive Technology (6566708)

Firefox might crash when used together with Orca. No error message is displayed.

Workaround: Disable assistive technology.

inetd Displays Warnings After Upgrade (6557608)

After upgrading to the Developer 5/07 release, the inetd command displays the following two warnings:

inetd[685]: Failed to update state of instance 
svc:/network/tname:default in repository: entity not found

and:

inetd[685]: Failed to update state of instance 
svc:/network/tname:default in repository: No such file or directory

Workaround: These two warnings only appear during the first boot after upgrade. These warnings are benign and may be safely ignored.

x86: Root(/) File System is at Full (100%) After Installing With Minimal Filesystem Sizes (6557276)

The root(/) file system might be full (100%) when you do all the following steps:

1. You choose to modify the default filesystem layout.

2. You split the filesystems into root(/), /var, /opt, and /usr.

3. You accept the minimal filesystem sizes provided by the installer.

The system might not be able to reboot and might display the following message:

notice: realloccg: / file system full

Workaround: When splitting filesystems, add 25-50% to the minimal size of the root(/) filesystem.

GNOME-Keyring Crashes (6552688)

GNOME-keyring crashes when attempting to validate blank keyring names and item names. This also results in a core dump.

The following error message is displayed:

Segmentation Fault (core dumped)

Workaround: None.

SPARC: The (ZFS) ARC Allocates Memory Inside The Kernel Cage Preventing DR (6522017)

ZFS can potentially allocate kernel memory across all system boards on systems with very large memory configurations. One free system board is required for dynamic memory reconfiguration so that the memory from the board to be dynamically reconfigured can be copied to the free board. The dynamic memory reconfiguration means that you cannot dynamically reconfigure memory on systems with very large memory configurations that have ZFS running. High-end SunFire^TM servers can relocate kernel pages so that this issue is avoided. These servers must have kernel page relocation (KPR) enabled for domains with more than 32 cores. No error message is displayed

Workaround: Reduce the amount of kernel memory that ZFS can allocate by setting the zfs_arc_max parameter in the /etc/system file. The following example sets the maximum size to 512 Mbytes.

set zfs_arc_max = 0x20000000

Some Keyboard Layouts Do Not Install Correctly (6518611)

Some keyboard layouts that are selected during installation in the Configure Keyboard Layout screen, are not installed correctly. Instead, the keyboard layout remains in US-English. This error can cause problems later, when the user switches keyboard layout in the Java DS by using the Input Method Switcher (iiim-panel). The affected keyboard layouts are:

Albanian, Belarusian, Bulgarian, Croatian, Czech, French-Canadian, Hungarian, Greek, Latin-American, Lithuanian, Latvian, Macedonian, Malta UK, Malta US, Polish, Russian, Serbia-And-Montenegro, Slovenian, and Slovakian

No error message is displayed.

Workaround: Select the US-English keyboard layout during the installation. Then, revise your keyboard setting after the installation. To switch the keyboard layout after installation, you can use either the Input Method Switcher (iiim-panel) or the kbd -s command-line utility.

strftime(3c) Should Support GNU Extension in %-m And %-d (6448815)

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:

1. Backup the /usr/share/locale/LC_MESSAGES/gnome-panel*.mo file.

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

3. Edit the file gnome-panel.gnome-2-16.zh_CN.po and replace all occurrences of %-m with %Om, and %-d with %e.

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

5. Log out of the system and re-login.

Apache Tomcat Shutdown Issue

When shutting down Apache Tomcat 5.5, an exception is generated due to lack of required permissions. This problem is caused because the user who shuts down the system is not root or in the group “other”, which all files are set to recognize during the installation of Tomcat.

Workaround: Prior to starting Tomcat, change permissions of files in the Tomcat directory as follows:

% su root
Password:
# DIR=/opt/netbeans-5.5/enterprise3/apache-tomcat-5.5.17
# find ${DIR} -perm -100 -exec chmod ugo+x {} \;
# find ${DIR} -perm -200 -exec chmod ugo+w {} \;
# find ${DIR} -perm -400 -exec chmod ugo+r {} \;
# exit
% 

Japanese Man Pages Might Not Be Synchronized With English

The contents of some Japanese man pages are not synchronized with the latest English man pages. No error message is displayed.

Workaround: See the English man pages to confirm the latest contents.

% env LC_MESSAGES=C man <manpage>

Solaris Express Developer Edition 2/07 Issues

The following issues apply to the Developer 2/07 release.

The Linux Partition Does Not Display on the GRUB Menu After Installing the Solaris OS (6508647)

If Linux is installed on your disk and you installed the Solaris OS on a separate partition, the Linux partition does not display on the GRUB menu. No error message is displayed.

Workaround: Edit the GRUB menu's menu.lst file to add Linux to the GRUB menu. Perform the following steps:

1. Boot the Solaris OS.

2. Edit the menu.lst file at /boot/grub/menu.lst. For more information, see the System Administration Guide: Basic Administration.

The Linux Partition is Not Recognized When Installing the Solaris OS (6507774)

When you are installing the Solaris OS, the installer enables installing on the whole disk, but not on the Solaris partition that you've created. This problem occurs under the following conditions:

• You are installing with the Solaris interactive installation graphical user interface (GUI)

• You have Linux and a Linux swap partition installed on your system

• You have created a dual-boot partition for Solaris before running the installer

The following error message is displayed:

WARNING: The initial fdisk information found on disk<disk> was invalid. 
Defaulting the entire disk to a Solaris partition.

Workaround: Modify the partition ID for the Linux swap partition. Perform the following steps:

1. Exit the installer.

2. Open a terminal window.

3. Copy the current fdisk partition table to a temporary file.

   # fdisk -W /tmp/partfile /dev/rdsk/<disk>p0

4. Open the /tmp/partfile in vi editor.

5. Change the ID of the Linux swap partition from 130 to 132.

6. Write the fdisk partition table from the edited file.

   # fdisk -F /tmp/partfile /dev/rdsk/<disk>p0

7. Restart the installer.

   # install-solaris

8. Reboot the system after the Solaris installation is complete.

9. Change the partition ID of the Linux swap partition back to 130 by performing step 4 through step 7.

sd Treats an fdisk Partitioned Disk as EFI Partitioned Disk (6355349)

If a GPT backup header is left on a disk after the disk is repartitioned to a format other than EFI or GPT, the Solaris OS might treat the disk as EFI or GPT labeled. This error occurs only if an EFI or GPT labeled disk is repartitioned with earlier releases of Solaris or by using a utility that is not EFI or GPT aware. If the GPT backup is used, the following warning is displayed:

primary label corrupt; using backup

Workaround 1: Clear the entire disk before you repartition the disk.

dd if=/dev/zero of=/dev/rdsk/c1t3d0

Workaround 2: Clear the GPT backup header that resides in the last block of the disk. Perform the following steps:

1. Run the format command on the disk and specify the verify option. Note the values of the sectors.

   #echo "verify" | format /dev/rdsk/c1t3d0 | grep "^sectors" Reading the primary EFI GPT label failed. Using backup label. Use the 'backup' command to restore the primary label. sectors = 143374743

2. (Optional) Copy the contents of the specified block.

   dd if=/dev/rdsk/c1t3d0 of=/var/tmp/lastblock iseek=143374743

3. Clear the specified block.

   dd if=/dev/zero of=/dev/rdsk/c1t3d0 oseek=143374743

The Solaris Partition is Not Recognized When Installing the Solaris OS (6346759)

When you are installing the Solaris OS, the installer does not install the OS on the Solaris partition that you have created. Instead, the installer tries to install the OS on the Linux swap partition. This problem occurs under the following conditions:

• You are installing with the Solaris interactive installation in text mode.

• You have Linux and a Linux swap partition installed on your system.

• You have created a separate partition for Solaris before running the installer.

No error message is displayed.

Workaround: Modify the partition ID for the Linux swap partition. Perform the following steps:

1. Exit the installer.

2. Open a terminal window.

3. Copy the current fdisk partition table to a temporary file.

   # fdisk -W /tmp/partfile /dev/rdsk/<disk>p0

4. Open the /tmp/partfile in vi editor.

5. Change the ID of the Linux swap partition from 130 to 132.

6. Write the fdisk partition table from the edited file.

   # fdisk -F /tmp/partfile /dev/rdsk/<disk>p0

7. Restart the installer.

   # install-solaris

8. Reboot the system after the Solaris installation is complete.

9. Change the partition ID of the Linux swap partition back to 130 by performing step 4 through step 7.

Installation Defaults to Developer Release

The Developer 2/07 release includes a set of developer tools and uses a quick installation process.

Workaround: The prior default was to install the Solaris Express release. The Solaris Express release does not include the developer tools set. However, the Solaris Express release enables you to customize your system configuration during the installation. If you want to install the Solaris Express release, you must select that release in the initial installation screen.

Extended Partitions Maintained

If you have another OS on an extended partition, the existing extended partition is not changed and is not lost during a Solaris Developer release installation. Existing extended partitions are not visible during the Developer release installation, but the primary fdisk partition in which the extended partition resides is visible. Data in these partitions is not lost due to the installation. The OS on the extended partition does not display on the GRUB menu. For instructions about how to add another OS to the GRUB menu, see Introduction to GRUB Based Booting in System Administration Guide: Basic Administration.

Workaround: None.

Solaris Express 11/06 Issues

The following issue applies to the Solaris Express 11/06 release.

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 Express 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 Express 12/05 release.

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 Express release, as the active OS.

Solaris Express 10/06 Issues

The following issue applies to the Solaris Express 10/06 release.

Keyboard Configuration in JumpStart Must Be Valid

A new sysidkdb tool is introduced in the Solaris Express 10/06 release, which configures the USB keyboard layout during installation. This new tool defines valid keyboard layout strings. Unknown is not a valid string. Therefore, during the JumpStart installation on SPARC systems, the keyboard=Unknown in the sysidcfg script is not valid.

The following error message is displayed:

keyboard=Unknown
Unknown is not a valid keyboard layout

Workaround: Remove the line Keyboard=Unknown from your sysidcfg script. Or, replace Unknown with a valid keyboard string. For more information about the new sysidkbd tool and for information about valid keyword options, see the sysidcfg(4) man page.

For serial keyboards with SPARC systems, omit the keyboard variable in your sysidcfg scripts for SPARC systems.

If a valid keyboard string is not provided in the sysidcfg script, you are prompted for a keyboard selection during the installation.

Solaris Express 7/06 Issues

The following issue applies to the Solaris Express 7/06 release.

Installation Results Changed

Because of the new security features, the results of an installation are substantially different in this release. All network services, except ssh, are disabled or restricted to respond to local requests only.

For information about enabling services, see Network Services Startup in Solaris Express Developer Edition What's New.

Solaris Express 6/06 Issues

The following issues apply to the Solaris Express 6/06 release.

Solaris Volume Manager Not Starting on Systems That Revert to Solaris OS Previous to Solaris Express 4/06 Release

You encounter problems with starting the Solaris Volume Manager if you perform the following procedures on your system:

1. Upgrade to the Solaris Express 4/06 OS or a subsequent release that contains the new Solaris Volume Manager support for descriptive names.

2. Create volumes and hot-spare pools, which Solaris Volume Manager automatically configures with descriptive names.

3. Without removing these components, revert to a Solaris OS previous to the Solaris Express 4/06 release currently in the system.

The Solaris Volume Manager in the previous Solaris OS does not recognize the components with descriptive names. Consequently, in the reverted Solaris release, the Solaris Volume Manager does not start. The following error message is displayed:

svc:/system/mdmonitor:default: Method "/lib/svc/method/svc-mdmonitor" 
failed with exit status 1.
   system/mdmonitor:default failed

The system also panics and displays a message similar to the following:

Cannot open mirrored root device, error 19
Cannot remount root on /pseudo/md@0:0,10,blk fstype ufs

panic[cpu0]/thread=180e000: vfs_mountroot: cannot remount root

000000000180b950 genunix:vfs_mountroot+344 (18831f0, 2021, 18831f0, 18621a8, 
18362c0, 185d760)
  %l0-3: 00000000018362c0 000000000185d400 000000000183b400 00000000011e6400
  %l4-7: 0000000000000001 0000000000008025 000000000185d518 00000000018831f0
000000000180ba10 genunix:main+98 (18141a0, 1013400, 18362c0, 18aa000, 
180e000, 1814000)
  %l0-3: 0000000070002000 0000000000000001 000000000180c000 000000000180e000
  %l4-7: 0000000000000001 0000000001074400 0000000000000060 0000000000000000

Workaround: All Solaris Volume Manager components that you created subsequent to the OS upgrade use descriptive names. Remove these components first before performing the OS reversion. Follow these steps:

1. Become superuser.

2. With the metastat -D command, list the metadevices and hot-spare pools that use descriptive names.

   You must issue the command separately for local and named metasets to acquire a complete list of these components. For further details about the metastat command, see the metastat(1M) man page.

   1. Issue the metastat -D command for local metasets. The command generates an output similar to the following:

      # metastat -D d21: Concat/Stripe Size: 208278 blocks (101 MB) Stripe 0: Device Start Block Dbase Reloc c1t1d0s1 0 No Yes swimming: 1 hot spare Device Status Length Reloc c1t2d0s1 Available 208278 blocks Yes

   2. Issue the metastat -D command for named metasets. The command generates an output similar to the following

      # metastat -s named -D named/alley: Concat/Stripe Size: 208278 blocks (101 MB) Stripe 0: Device Start Block Dbase Reloc c1t3d0s1 0 No Yes

3. With the metaclear command, remove these components that use descriptive names. You must issue this command separately for local and named metasets.

   1. From the local set, remove the component d21 and the hot-spare pool swimming.

      # metaclear d21 d21: Concat/Stripe is cleared # metahs -d swimming c1t2d0s1 swimming: Hotspare is deleted # metahs -d swimming swimming: Hotspare pool is cleared

   2. From the named metaset, remove the component alley.

      # metaclear -s named alley named/alley: Concat/Stripe is cleared

4. Proceed with reverting to the previous Solaris OS.

smosservice add Command Does Not Install Designated ARCH=all Packages (4871256)

The smosservice add command does not install any packages that are designated ARCH=all in the root (/) or /usr file systems. No error message indicating that these packages were skipped is displayed. This behavior has existed since the Solaris 2.1 OS. The behavior applies to both SPARC based and x86 based clients.

Note that the list of missing packages varies, depending on the Solaris release that you are running.

Workaround:

Locate and install the missing ARCH=all packages.

For step-by-step instructions about locating and installing missing packages, see How to Locate and Install Missing ARCH=all Packages in System Administration Guide: Basic Administration.

Solaris Express 4/06 Issues

The following issue applies to the Solaris Express 4/06 release.

Solaris Express 3/06 Issues

The following issue applies to the Solaris Express 3/06 release.

x86: Upgrade Option Is Not Available When Upgrading to Solaris Express 3/06 OS (6386504 )

The upgrade operation fails when upgrading the OS to the Solaris Express3/06 OS as follows:

• For the Solaris installation program, the upgrade option is unavailable.

• For the custom JumpStart program, the upgrade fails.

This problem is due to an unused boot partition that must deleted. The problem occurs under the following circumstances:

• You have performed an initial installation from the Solaris 8, 9, or 10 3/05 release. An x86 boot partition was created during installation.

• You have performed an initial installation from the Solaris 10 1/06 release or Solaris Express release that supports GRUB. The x86 boot partition is preserved, but is not used.

• You try to upgrade to the Solaris Express 3/06 OS.

The following error will be in/tmp/install_log:

# more /tmp/install_log
kdmconfig:  The following warning was noted:
Error while executing loadkeys command.
Checking c1d0s0 for an upgradeable Solaris image.
The x86 Boot fdisk partition is missing /a/boot/solaris/bootenv.rc

Workaround:

• If you are upgrading with the Solaris installation program, delete the unused boot partition using the format or fdisk command. Repartition before you upgrade.

• If you are upgrading with JumpStart, specify the disk that contains the root (/) file system to be upgraded with the root_device keyword. For example, the profile would contain the following keywords.

  • install_type upgrade

  • root_device c1t0d0s0

Solaris Express 1/06 Issues

The following issue applies to the Solaris Express 1/06 release.

x86: Graphics of Sun Java Desktop System Might Become Corrupted After Installation (6358446)

The graphics of the Java DS might become corrupted if you install the Solaris Express 1/06 software in the following manner:

• You install the software by using the DVD media or a DVD image on the network.

• You configure the system to use the Xorg X server.

The error is observed on systems that use certain Matrox graphics cards such as the Millennium G450, AGP, DualHead card, or the Millennium G400 card.

No error messages are displayed. However, you might observe the following symptoms on all GNOME applications:

• Icons and window titles exhibit unassigned colors.

• Buttons overlap.

• The positions of icons are unstable.

Workaround: None.

Solaris Express 12/05 Issues

The following issues apply to the Solaris Express 12/05 release.

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

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

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.

Solaris Express 11/05 Issues

The following issues apply to the Solaris Express 11/05 release.

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.

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

Solaris Express 6/05 Issues

The following issue applies to the Solaris Express 6/05 release.

Cannot Create a Solaris Flash Archive When Solaris Zones Are Installed (6246943)

Starting with the current Solaris release, a Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not currently compatible with the Solaris containers (zones) feature.

Do not use the flar create command to create a Solaris Flash archive in these instances:

• In any non-global zone

• In the global zone if there are any non-global zones installed

If you create a Solaris Flash archive in such an instance, the resulting archive might not install properly when the archive is deployed.

Workaround: None.

Bugs Fixed and Integrated

This table lists issues and bugs that have been fixed since the release of Solaris 10 Operating System.