| Solaris |
|
|
ReleaseNotes2008.11
Release Notes for the OpenSolaris 2008.11 Release
LanguagesTranslation for this page
EnglishDeutschEspañolFrançaisItaliano日本語한국어Português BrasileiroPусский简体中文繁體中文
This page lists the Release Notes for the OpenSolaris 2008.11 release. For additional information on the following issues, look up the bug number in Bugzilla.
For information about the new features in the OpenSolaris 2008.11 release, see What's New in OpenSolaris 2008.11.
Note: For information about upgrading your system to the OpenSolaris 2008.11 release from a previous release, see Upgrading OpenSolaris 2008.05 to Later Versions of OpenSolaris.
Installing OpenSolaris on Systems With Low Memory.
64 - Installer, but not Desktop, Allows Empty Passwords.
1156 - Booting a BE That Was Left Mounted Before the Reboot Fails.
1559 - GRUB Entry for Windows Incorrect From USB Stick Install.
1565 - Nautilus Process Hangs After GNOME Login.
1685 - Renaming a Busy BE Might Fail.
2656 - Enabling the printers:snmp Service Causes System to Revert to Maintenance State.
2900 - Firefox dumps core in NV95.
3691 - Using Fast Reboot When Specifying the Name of a BE Fails.
3783 - Installer Fails if the User Creates or Imports the ZFS Pool rpool.
3947 - Distribution Constructor Does Not Recognize ZFS File System Mountpoints for Build Areas.
4061 - Only the First GRUB menu.lst Entry of the Source BE Is Created When Creating a New BE.
4166 - Automated Installer Hangs on a 1 GB System Without Swap.
4246 - User and Root Passwords are Not Encrypted in the SC Manifest.
4248 - ICT reset_image_UUID Fails for Automated Installer if authname is Not Set to opensolaris.org.
4282 - Trackerd Does Not Start by Default on OpenSolaris.
4294 - Distribution Constructor Fails if Compressed ZFS Dataset Is Used as the Build Area.
4300 - Automated Installer Fails to Access the IPS Repository.
4488 - Automated Installer Services Should be Started Manually if the Install Server Is Reboooted.
4586 - Distribution Constructor Pause and Resume Functionality Might Fail.
4589 - Exception Message Generated by Distribution Constructor Upon Successful Termination.
4629 - Timezone Cannot be Customized if Automated Installer is Used for Installation.
4636 - Distribution Constructor Might Dump Core When Running the br-config Finalizer Script.
4645 - The Graphical Boot Progress Bar Hides sys-unconfig Questions at Boot Time.
4881 - Input Language Cannot be Switched When Russian Keyboard Layout Is Selected.
5003 - Crash Dumps Are Not Saved to the File System at Boot Time By Default.
5012 - Using sys-unconfig to Unconfigure the Network Fails.
5092 - pkg and packagemanager Fail to Start.
5146 - Live CD With Primary Languages Contains Default Locales Only.
5277 - Issues With the IIIM Daemon.
5302 - Automated Install Manifest Criteria Are Lost.
5473 - en_US/es_ES/fr_FR/de_DE UTF-8 Locales Might Not be Installed by pkg image-update.
5492 - pkg(1) Does Not Uninstall Packages When The System Is Installed From a Global Live CD.
5543 - Tracker Does Not Index the Home Directory by Default.
5544 - Tracker Cannot Search Evolution Emails.
5588 - Cannot Use the su(1M) to Get root Privileges in the Automated Installer.
6670311 - Installer Might Fail if the Linux Swap Primary Partition Precedes the Solaris Partition.
6687328 - vim Command Cannot Display Multibyte Characters.
6694783 - Input Method Duplicate Causes IDE Crash.
6696145 - Install Might Cause Panics on Intel 965 With GM965 Chipset.
6742850 - CJK Characters Do Not Display Correctly in the Java Application Environment.
6773520 - Issues With the Slovak Keyboard.
6775600 - Audio Is Unavailable After Installation of OpenSolaris 2008.11 RC2.
Installing OpenSolaris on Systems With Low Memory
Description
OpenSolaris supports installation through its Live CD on systems or virtual machines that contain at least 512 MB of RAM. The following limitations exist on systems with low memory.
While basic desktop functions and installation functions work well, attempting to use the Live CD as a full-blown user environment might cause issues. However, an installed system functions normally with 512 MB of RAM.
The Live CD supports booting the OpenSolaris kernel in either 32-bit mode or 64-bit mode depending on the capabilities of the underlying hardware. The OS will boot in the 64-bit mode only if the system has atleast 1000 MB of RAM. Systems with less than this amount will boot in the 32-bit mode. This limitation does not apply to the installed system.
It is not possible to start the 'Read the Release Notes' link from within the GUI Installer on systems with 512 MB of RAM. Attempting to open this link causes the system to freeze while loading Firefox. Therefore users are recommended to read the Release Notes prior to launching the GUI Installer.
On systems with less than 700 MB of RAM the installer will create a dedicated swap slice instead of a ZFS volume to use for system swap.
For more information about the enhancements that were made for the OpenSolaris 2008.11 release to support installation on systems with low memory, see # 3597 Unable to install OpenSolaris with 512 MB Base Memory.
# 64 Installer, but not Desktop, Allows Empty Passwords
Description
If, during installation, no root password is entered and no user account is created, you will not be able to log in to the installed system.
Workaround
Choose one of the following workarounds:
- Enter a root password as follows:
- During boot, type “e” in the grub menu twice, in order to edit the boot entry.
- Add -s to the end of the boot entry, and boot with this line.
- Log in as root and use the passwd command to enter a password.
- Restart the system. Boot normally, and log in with the new password.
- Set root so that it does not require a password as follows:
- During boot, type “e” in the grub menu twice, in order to edit the boot entry.
- Add -s to the end of the boot entry, and boot with this line.
- Log in to the system as root.
- Edit the /etc/X11/gdm/custom.conf file so that the value of PasswordRequired is false.
# 1156 Booting a BE That Was Left Mounted Before the Reboot Fails
Description
If a boot environment (BE) is mounted by using the beadm mount command and the system is rebooted before that BE is unmounted, selecting that BE from the GRUB menu causes a boot failure.
If a BE is activated by using the beadm activate command, this BE is the default selection in the GRUB menu. Therefore, leaving this BE mounted before a reboot causes a boot failure.
A typical boot error message is:
Use is subject to license terms. Hostname: opensolaris Apr 28 16:05:08 svc.startd[7]: svc:/system/sysevent:default: Method "/lib/svc/method/svc-syseventd start" failed with exit status 95. Apr 28 16:05:08 svc.startd[7]: system/sysevent:default failed fatally: transition to maintenance (see 'svcs -xv' for details) '/usr/sbin/pmconfig: cannot open/create "/etc/.cpr_config", Bad file number Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) Console login service(s) cannot run Root password for system maintenance (control-d to bypass):
Workaround
Use the following procedure:
- Reboot the system and select the previously active BE.
- When the system is up, reset the mount point of the activated BE by typing the following command as root user:
# beadm unmount //boot_environment//
- Reboot the system.
# 1161 GUI Installer Shrinks the Solaris Partition to be Created Even if Enough Available Space is Reported on the Disk Screen
Description
When creating a Solaris partition, the GUI installer only utilizes the free space at the end of the disk after the last primary partition. However, the sum of the total space available including gaps between partitions is reported on the disk screen. If the user tries to create a Solaris partition which is larger than the amount of free space available at the end of the disk, the size of Solaris partition is adjusted.
A warning message is displayed when the Next button is pressed on the disk screen and the Solaris partition is shrunk. The title of the warning message is as follows:
Adjustments were made to the new partitions
Workaround
Use the Solaris fdisk(1M) tool or the GParted tool to create a Solaris2 partition. These tools enable the utilization of unallocated space between already defined partitions. Select the newly created Solaris2 partition as the target for the installation on the installer disk screen.
# 1559 GRUB Entry for Windows Incorrect From USB Stick Install
Description
When the OpenSolaris 2008.11 release is installed from a USB stick, the GRUB entry for Windows does not reference the correct disk device.
Workaround
Edit the /rpool/boot/grub/menu.lst file. Modify the rootnoverify entry in that file.
Typically a USB installed system will have the following entry:
rootnoverify (hd1,0)
This entry should be changed to the following:
rootnoverify (hd0,0) #~---------- ADDED BY BOOTADM - DO NOT EDIT ~---------- title Windows rootnoverify (hd0,0) chainloader +1 #~------------------- END BOOTADM ~--------------------
If a diagnostic partition exists, a similar change is required.
# 1565 Nautilus Process Hangs After GNOME Login
Description
When you log in to the GNOME desktop, Nautilus might hang. In this case, the desktop background is a solid, blue-gray color and right-clicking on the background does not open a menu. The nautilus-debug-log.txt is added in your home directory.
If Nautilus hangs, it can consume 50% of the CPU time.
Workaround
Manually kill the broken Nautilus process as follows:
- Launch a GNOME terminal by selecting Applications->System Tool->Terminal on the menu bar.
- Kill the oldest nautilus process in the gnome-terminal. For example:
bash$ ps -ef |
grep naut
test 13425 13374 0 19:59:30 ? 0:00 nautilus ~--no-default-window
~--sm-client-id default2
test 13227 1 50 17:39:39 ? 39:36 nautilus ~--no-default-window
~--sm-client-id default2
bash$ kill 13227
- Log out.
# 1685 Renaming a Busy BE Might Fail
Description
Renaming a boot environment (BE) might fail if the BE has a dependent clone that is currently mounted or otherwise busy.
A typical example of this situation is when the live BE has been successfully upgraded. If you then try to rename the auto-generated and upgraded BE, the renaming fails. The renaming fails because the upgraded BE has been activated and the live BE is now its clone.
Workaround
Use the following procedure:
- Activate the live BE.
- Rename the upgraded BE.
- Activate the upgraded BE.
For example, if the live BE name is “opensolaris”, and the auto-generated BE name of the upgraded BE is “opensolaris-1,” use the following commands:
# beadm activate //opensolaris// # beadm rename //opensolaris-1 new_name// # beadm activate //new_name//
# 2656 Enabling the printers:snmp Service Causes System to Revert to Maintenance State
Description
After installing the OpenSolaris 2008.11 release, the hald-addon-network-discovery agent cannot be enabled. This failure occurs whether you try to enable the service from the desktop or from the command line.
Note - This problem does not occur on systems running a supported Solaris Express Community release.
An error message similar to the following is displayed in the service log:
[ Jul 24 21:09:32 Executing start method
("/lib/svc/method/svc-network-discovery start snmp"). ]
/usr/bin/dbus-send ~--system ~--print-reply ~--dest=org.freedesktop.Hal
~--type=method_call /org/freedesktop/Hal/devices/network_attached
org.freedesktop.Hal.Device.NetworkDiscovery.EnablePrinterScanningViaSNMP
int32:60 string:public string:0.0.0.0
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the network
connection was broken.
[ Jul 24 21:09:40 Method "start" exited with status 1. ]
Workaround
Use the following procedure:
- Add the SUNWSmmgr package.
# pkg install SUNWSmmgr
- Restart the HAL add-on module.
- To restart the add-on module from the desktop, perform these steps:- Open the Services settings application from the main menu.
System-> Administration-> Services
The Services settings window is displayed. - Select the Hardware Abstraction Layer network attached device discovery option (network/device-discovery/printers:snmp).
- Click OK to save the changes.
- To restart the add-on module from the command line, type:
- Open the Services settings application from the main menu.
# svcadm restart hal
- Clear the printers:snmp service.
# svcadm clear printers:snmp
# 2900 Firefox crashes on NV 95
Description
Firefox dumps core in NV build 95 due to Flash Player bug. Flash plugin v9.0 r124 has a bug that causes Firefox to crash. This issue has been fixed in the flash plugin v 9.0 r125.
Note - This affects only users of Flash Player v9.0 r124 and below.
Workaround
- Start firefox.
- From the Menu bar, click on Tools -> Add-ons -> Plugins.
- Right click on Shockwave Flash and choose the Disable option to disable the plugin.
- Manually install the updated version from the following url: http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-4
# 3691 Using Fast Reboot When Specifying the Name of a BE Fails
Description
The new fast reboot feature enables you to provide a '-e' option to specify the name of the boot environment (BE) to which you need to fast reboot. Attempting to do a fast reboot and specifying the name of a BE fails in the OpenSolaris 2008.11 release. The following error message is displayed:
# reboot -f -e opensolaris-7 reboot: cannot mount BE opensolaris-7
Workaround
Specify the full root dataset path to the BE to which you need to fast reboot. For example:
# reboot -f rpool/ROOT/opensolaris-7
# 3783 Installer Fails if the User Creates or Imports the ZFS Pool rpool
Description
If a ZFS pool named rpool is already present on the system because it was manually imported or created by the user during the current boot of the live CD, the install process fails. The last message in the installation log is as follows:
Root pool rpool exists, we can't proceed with the installation.
This behavior is intentional and ensures that the installer does not inadvertently corrupt the user's data.
The installer can recognise cases when rpool was created by the installer itself but the installation process failed or was interrupted. In such cases the installer destroys rpool automatically after it is restarted.
Workaround
Choose one of the following workarounds:
- To preserve data in the rpool, reboot the system and do not import the pool. The pool remains invisible to the installer. However, if the pool was created on the target disk then the pool cannot be preserved.
- If you do not want to preserve data in the rpool, destroy the pool before you start the installer, using the following command:
$ pfexec zpool destroy -f rpool
# 3947 Distribution Constructor Does Not Recognize ZFS File System Mountpoints for Build Areas
Description
If a system has a ZFS file system, the Distribution Constructor does not recognise or treat a build area as a ZFS file system in the following cases:
- A new sub-directory of the ZFS file system is specified as a build area, but the mountpoint is specified instead of the zpool.
- The build area already exists as a ZFS file system but the mountpoint is specified instead of the zpool
For example, in the following zpool:
$ zfs list | grep "disk2_pool/ib/pia" disk2_pool/ib/pia 1.90G 355G 18K /export/home/ib/pia
When you run the following command:
# distro_const build -p 1 slim_cd.xml
Where the build area in slim_cd.xml is specified as <build_area>/export/home/ib/pia</build_area>, the following message error message is displayed:
Checkpointing is not available Rerun the build without -p
Workaround
Specify the zpool in the manifest. For example, <build_area>disk2_pool/ib/pia</build_area>.
# 4061 Only the First GRUB menu.lst Entry of the Source BE Is Created When Creating a New BE.
Description
When a new boot environment (BE) is created, the new BE will only have one entry in the GRUB menu.lst file regardless of how many entries the source BE has. The source BE's first menu.lst entry is used to create the entry for the new BE. All other entries are ignored. This issue occurs when you create the new BE either through beadm or pkg image- update.
If the user needs the other entries for the new BE they are not available.
Workaround
Edit the /rpool/boot/grub/menu.lst file and copy the desired entries from the original BE. Replace the BE name in the source entries with the BE name of the target.
# 4166 Automated Installer Hangs on a 1 GB System Without Swap
Description
On a system with 1 GB of physical memory, the Automated Installer might not create swap space which causes the installation to hang due to insufficient memory.
Workaround
Ensure that the fdisk partition is bigger than 12 GB if you are specifying the target disk.
# 4215 Automatic Install Does Not Set the root Role and the Primary Administrator Profile to the Created User Account.
Description
When doing Automatic Install, the user is not assigned the Primary Administrator profile and root is not set up as a role.
Workaround
Use the following procedure:
- After the install completes log in to the newly installed client as the specified user.
- Become superuser.
% su -
- Change the role to root.
# usermod -K type=role root
- Assign the Primary Administrator profile to the user account.
# usermod -P "Primary Administrator" -R root //user_login_name//
# 4246 User and Root Passwords are Not Encrypted in the SC Manifest
Description
The Automated Installer enables setting the root password and creating a new user/password during installation. These passwords should be specified in plain-text and the installer encrypts them. Specifying passwords in plain-text is a security risk.
Workaround
Use the standard password for root and user. Change the password once installation is complete by using the /usr/bin/passwd command.
# 4248 ICT reset_image_UUID Fails for Automated Installer if authname is Not Set to opensolaris.org
Description
The Automated Installer enables setting an authority name. If an authority name other than opensolaris.org is set, the ICT reset_image_UUID displays the following error in the install_log file:
<ICT Oct 25 20:43:43> current task:reset_image_UUID <ICT_I Oct 25 20:43:43> _cmd_status: executing cmd=pkg -R /a set-authority ~--reset-uuid opensolaris.org pkg: set-authority: authority does not exist. Use -O to define origin URL for new authority <ICT_I Oct 25 20:43:45> _cmd_status: return exitstatus=256 <ICT_E Oct 25 20:43:45> Reset uuid failed - exit status = 256, command was pkg -R /a set-authority ~--reset-uuid opensolaris.org <ICT_E Oct 25 20:43:45> Failure. Returning: ICT_PKG_RESET_UUID_FAILED
The install_log file is located at /a/var/sadm/system/logs/install_log.
Workaround
In the Automated Installer manifest set authname to opensolaris.org. For example:
<main url="http://ipkg.sfbay:29047" authname="opensolaris.org"/>
# 4282 Trackerd Does Not Start by Default on OpenSolaris
Description
Trackerd does not start by default in the GNOME desktop.
Workaround
Use the following procedure:
- Go to System->Preferences->Session and enable trackerd, and tracker-applet.
- Log out of your system.
- Log in again.
For more information, see the FAQs at the Tracker community page.
# 4294 Distribution Constructor Fails if Compressed ZFS Dataset Is Used as the Build Area
Description
If a compressed ZFS dataset is specified as the build area for the Distribution Constructor, the bootroot_archive step fails. An error message indicating that the device ran out of space when creating the pkg.lib archive is displayed.
Workaround
Ensure that the ZFS dataset specified as the build area is not compressed.
# 4300 Automated Installer Fails to Access the IPS Repository
Description
If the DHCP server is not set up correctly, the Automated Installer client might not get the required DNS and router information. The Automated Installer might fail to access the IPS repository. The following error message is displayed:
pkg image-create failed
Workaround
If the installadm command is used to setup the DHCP server as part of installadm create-service, ensure that the following conditions are met in the install server before running the command:
- /etc/resolv.conf is populated with correct DNS information on the server
- Your name service is DNS by checking the /etc/nsswitch.conf configuration file. The hosts and IP nodes value should be set to dns in the file.
- The DNS client SMF service /network/dns/client:default is enabled
- The default router is set
# 4488 Automated Installer Services Should be Started Manually if the Install Server Is Rebooted
Description
The Automated Installer starts the Apache Web server at port 5555 to serve Automated Installer images to the clients. When you create a service using installadm create-service, an installer service is started. If the install server on which the command was used reboots for any reason, the install services and the Apache Web server will not be restarted automatically. This will stop the Automated Installer clients from using the install server to boot and install successfully.
Workaround
Use the following procedure:
- Restart the Apache Web server:
# /usr/apache/2.2/bin/apachectl -f /var/installadm/ai-webserver/ai-httpd.conf -k start
- Get the configured services from the /var/installadm/service_data file. For example, the configured services might displayed as shown:
# cat /var/installadm/service_data new1;/tmp/directory/test1;new1;aiwebserver=kumbam:46501 _install_service_46501;/tmp/target/test1;_install_service_46501;aiwebserver=kumbam:46501
Here, the first parameter is the name of the service.
- Start each service using the installadm start command:
#installadm start new1 #installadm start _install_service_46501
# 4575 Automated Installer Fails If the Target Disk Does Not Contain an fdisk Partition
Description
If a target disk is specified in the AI manifest and if the disk does not have an fdisk partition, the Automated Installer fails to install the OpenSolaris 2008.11 operating system.
Workaround
Choose one of the following workarounds:
- Create an fdisk partition using fdisk tool.
- Create an fdisk partition by specifying partition information in the AI manifest. See Automated Installer documentation on how to specify partition creation information in AI manifest.
# 4586 Distribution Constructor Pause and Resume Functionality Might Fail.
Description
If you use the resume and pause functionality on the same command line, the Distribution Constructor will not allow the -r option to precede the -p option. The Distribution Constructor wrongly decides that you have specified a resume step that is invalid. The following error message is displayed:
You must specify an earlier step to resume at.
Workaround
Specify the -p option before the -r option.
# 4589 Exception Message Generated by Distribution Constructor Upon Successful Termination
Description
The Distribution Constructor might display the following error message after successfully performing its function:
Unhandled exception in thread started by Error in sys.excepthook: Original exception was:
Workaround
This error message is displayed just before termination and can be safely be ignored.
# 4629 Timezone Cannot be Customized if Automated Installer is Used for Installation
Description
Due to the bug in Automated Installer, timezone is always set to PST8PDT on an installed system. The value defined by the tag in the SC manifest is not taken into account.
Workaround
Choose one of the following workarounds:
- Use the Automated Installer and boot the system. Go to System->Administration->Time and Date application on the Desktop and set the timezone.
- Use the GUI installer for installation.
# 4636 Distribution Constructor Might Dump Core When Running the br-config Finalizer Script
Description
The Distribution Constructor might dump core during the br-config finalizer script when running the mkrepo script. This occurs if the mount point associated with the build area specified in the manifest exceeds 26 characters. The following error message is displayed:
==== br-config: Boot root configuration /usr/share/distro_const/mkrepo: line 51: 13909: Abort(coredump) Stopping at br-arch: Boot root archiving
Workaround
Change the mount point associated with the build area to not exceed 26 characters.
For more information on the core dump, see CR 6721855 - svccfg Dumps Core.
# 4645 The Graphical Boot Progress Bar Hides sys-unconfig Questions at Boot Time
Description
The graphical boot feature has been enabled for the OpenSolaris 2008.11 release. This feature provides the user with a graphical horizontal scrolling progress bar during system boot instead of the boot messages.
If the user uses the sys-unconfig command, the graphical boot progress bar hides the sys-unconfig questions at boot time.
Workaround
Select the text boot option from the GRUB menu.
# 4881 Input Language Cannot be Switched When Russian Keyboard Layout Is Selected
Description
IIIM does not work correctly when the Russian keyboard layout is set as physical keyboard. As a result, if you log in to the Russian locale and activate Input Method, upper case ASCII letters are input instead of lower case ASCII letters.
Workaround
Select English layout as physical keyboard. Then if you log in to the Russian locale, you can switch input languages between Russian and ASCII by using the IM trigger key. The default key is Shift_L+Control_L for Russian locale.
# 5003 Crash Dumps Are Not Saved to the File System at Boot Time By Default
Description
To reduce the time required for a reboot, crash dumps are not saved to the file system at boot time.
Workaround
Use the dumpadm(1M) command to enable crash dumps at boot time:
# dumpadm -y
Alternatively, create a cron job which enables the saving of crash dumps at any given later point.
# 5012 Using sys-unconfig to Unconfigure the Network Fails
Description
If you have installed the OpenSolaris 2008.11 release from media, using the sys-unconfig to unconfigure the network settings on your system fails. The nwam service will still be enabled after the system reboots.
Workaround
Ensure that you change your current working directory to "/" before using the sys- unconfig command.
# cd / # sys-unconfig
# 5092 pkg and packagemanager Fail to Start
Description
pkg and packagemanager dump stack and fail to start if the current LANG variable is en_US.UTF-8, es_ES.UTF-8, fr_FR.UTF-8 or de_DE.UTF-8 and if these locales are not installed. These locales might not be installed due to bug # 5473.
Workaround
Install the missing locale packages. Execute the following commands:
- If your current LANG variable is any one of the locales listed above:
$ export LANG=C
- $ pfexec pkg install SUNWlang-enUS SUNWlang-frFR SUNWlang-esES SUNWlang-deDE
# 5146 Live CD With Primary Languages Contains Default Locales Only
Description
When using the Live CD with primary languages only default territories can be selected in the installer on the language screen. This issue is due to space constraints.
Workaround
Use the Global version of the Live CD for installation.
# 5277 Issues With the IIIM Daemon
Description
If the IIIM daemon is not running in the background, typing moderately fast in gtk+/gnome applications causes a delay in the display of text.
This issue occurs if you uncheck the 'Start IIIM Daemons', in gnome-session-properties under System->Preferences->Sessions, log out of the desktop session, and log back in. Starting a gtk+/gnome application and typing moderately fast in the application causes the text characters to appear after some delay.
Workaround
Currently there is no workaround to remove the IIIM deamon from an active session without side effects. If the reason for removing the IIIM daemon is to make the iiim-panel not visible on the gnome-panel and to disable Input Method trigger keys, use the procedure described below.
- Start iiim-properties under System->Preferences->Input Methods.
- Select None from the drop-down menu of 'Input Method status switcher placement' in the 'General' tab.
- Remove all trigger keys in 'Trigger Keys' tab.
- Click on Apply or OK button.
To ensure that IIIM daemons are running in the background, start gnome-session-properties from a terminal window. Check the 'Start IIIM Daemons' check box and close gnome-session- properties. Log out of the desktop session. When you re-login, the desktop session will not have the input methods applet.
# 5302 Automated Install Manifest Criteria Are Lost
Description
When you run installadm start on a service, all Automated Install manifest criteria for the Automated Install Web Server are lost.
Workaround
Use the installadm add command to add the install manifest criteria again. The following error message is displayed when you add the install manifest criteria:
Error: Not copying manifest, source and current versions differ ~-- criteria in place.
This error message can be safely ignored.
# 5473 en_US/es_ES/fr_FR/de_DE UTF-8 Locales Might Not be Installed by pkg image-update
Description
The following locales will not be installed if the slim_install cluster is uninstalled before you upgrade your system to the OpenSolaris 2008.11 release using the pkg image-update command:
- en_US.UTF-8
- es_ES.UTF-8
- fr_FR.UTF-8
- de_DE.UTF-8
Workaround
Install the missing locale packages. Execute the following commands:
- If your current LANG variable is any one of the locales listed above:
$ export LANG=C
- $ pfexec pkg install SUNWlang-enUS SUNWlang-frFR SUNWlang-esES SUNWlang-deDE
# 5492 pkg(1) Does Not Uninstall Packages When The System Is Installed From a Global Live CD
Description
If the system was installed using the global version of the Live CD, which contins all supported languages, the pkg(1) command does not uninstall any package from the installed system. The following error message is displayed:
$ pfexec pkg uninstall SUNWswmt Creating Plan \pkg: Cannot remove 'pkg:/SUNWswmt@0.5.11,5.11-0.101:20081119T230254Z' due to the following packages that depend on it: pkg:/slim_install@0.1,5.11-0.101:20081119T235636Z
Workaround
Remove the slim_install cluster from the installed system:
$ pfexec pkg uninstall slim_install
You can now remove other packages using the pkg(1) command.
# 5543 Tracker Does Not Index the Home Directory by Default
Description
When you start Tracker, the home directory is not indexed by default.
Workaround
Use the following procedure:
- Go to System->Preferences.
- Choose 'File Indexing' to start tracker-preferences.
- Check the 'Index and watch my home directory' checkbox in the 'Files' tab.
- Click on the OK button.
- A dialog box prompts that "data must be reindexed". Click on the Reindex button to reindex data.
For more information, see the FAQs at the Tracker community page.
# 5544 Tracker Cannot Search Evolution Emails
Description
When you start Tracker, you cannot search for Evolution emails. This is a known issue.
Workaround
None.
# 5588 Cannot Use the su(1M) to Get root Privileges in the Automated Installer
Description
When using the Automated Installer for installation of OpenSolaris, you can log in to the console to observe the installation process or reboot the system when installation is complete. You can log in either as a regular user where user name is jack, and the password is jack or you can log in as a root user where the password is opensolaris. Currently, when you are logged in as jack, you cannot use the su(1M) command to get root privileges.
Workaround
Log in as a root user from the console. The password is opensolaris.
# 6464201 Loop Back Mounts of the ZFS File Systems Causes the svc:/system/filesystem/local:default SMF Service to Fail
Description
If the system is rebooted after configuring an install service using the installadm create- service command, the system will not boot in the multi-user milestone. This issue occurs because the svc:/system/filesystem/local:default SMF service fails. When the installadm create- service command is executed, it adds lofs entries of the target or ZFS File System to /etc/vfstab. Since the file systems under /etc/vfstab are mounted before mounting the ZFS file systems, lofs mounts fail.
Workaround
Log in to the install server and clear the service using the following command:
# svcadm clear system/filesystem/local:default
Since the ZFS datasets are already mounted now, the system can recover.
# 6670311 Installer Might Fail if the Linux Swap Primary Partition Precedes the Solaris Partition
Description
The new Solaris installer installs the Solaris operating system into the Solaris2 partition (0xbf). The installer does not support multiple Solaris partitions on one disk. However, the installer recognizes the Linux swap partition (0x82) correctly and installs successfully if the primary partition is used as the Linux swap partition.
Solaris installation fails when the partition configuration is as following:
- The Linux swap primary partition precedes the Solaris2 partition
- The Solaris2 partition is not active
Workaround
Choose one of the following workarounds:
- Avoid defining a Linux swap partition as a primary partition on the same disk where the Solaris2 primary partition will be created. For example, create the Linux swap partition as logical volume within extended partition.
- Ensure that the Solaris2 partition precedes the Linux swap partition.
- Create the Solaris2 partition outside the installer and mark it as active. Then install into that preexisting partition.
- Before installation, change the Linux swap partition type to another type, excluding (0xbf) or (0x82). After the installation is complete, change the Linux swap partition type back to (0x82).
# 6687328 vim Command Cannot Display Multibyte Characters
Description
The vim command can not display multibyte characters. This bug affects other commands which symbolically link to /usr/bin/vim such as vi, view, and ex commands.
Workaround
Add the $HOME/.vimrc file that contains the following line:
set encoding=utf-8
Or, use the /usr/has/bin/vi command instead.
# 6694783 Input Method Duplicate Causes IDE Crash
Description
On rare occasions, when you log in to the desktop, you may encounter the following issue.
The Input Method(IM) status icon is displayed at the bottom of main window. When you open a new child window, such as when you select File->Open, a new IM status icon displays in the main window. When you close this child window, the new IM status icon remains. If you click on an IM status icon at this point, IDE crashes.
Workaround
- Find out if the iiim daemon is running by typing this command.
# ps -ef | grep //iiim//
- If you do not find a process that is related to iiimx or iiimd, restart the iiim daemon by typing this command.
# iiimx -//iiimd &//
- Try to use the Internet/Intranet Input Method instead of the X Input Method. You can select this option by right-clicking on the Gnome Applications icon.
# 6696145 Install Might Cause Panics on Intel 965 With GM965 Chipset
Description
Installing the OpenSolaris release on certain laptops that are equipped with the Mobile Intel GM965 Express chipset (Intel GMA X3100 Graphics) is known to cause panics.
This issue has been reproduced on the following models that are equipped with the GM965 chipset.
- Dell XPS M1330
- Lenovo ThinkPad X61/T61
- Toshiba Satellite Pro A200
How can I tell if my laptop is running the GM965 chipset?
You can use the Device Driver Utility on the LiveCD. Or, open a terminal window and run the following command:
pfexec /usr/X11/bin/scanpci
This command identifies which Graphics Controller you have on your laptop.
Workaround
Use the VESA driver to install the OpenSolaris 2008.11 release onto your system.
Use the following procedure for the vesa driver:
- From the GRUB menu, select the Text Console option.
- Login with user name, jack, and the password, jack.
- Execute the following commands
jack@opensolaris:~$ pfexec Xorg -configure jack@opensolaris:~$ sed //'/Driver.*"intel"/s/"intel"/"vesa"/'// xorg.conf.new > xorg.conf jack@opensolaris:~$ pfexec mv //xorg.conf.new /etc/X11/xorg.conf// jack@opensolaris:~$ svcadm enable //gdm//
- Install the release, per instructions at Installing OpenSolaris 2008.11 .
After the system reboots, the desktop is displayed using the vesa driver. - If you want to restart the Xserver using the intel driver, type the following:
% pfexec rm ///etc/X11/xorg.conf//
Restart the Xserver by logging out of your desktop session or hitting Ctrl-Alt-Backspace.
# 6742850 CJK Characters Do Not Display Correctly in the Java Application Environment
Description
Chinese, Japanese, and Korean characters do not display correctly on Java technology-based applications.
Workaround
Enable the antialising settings manually. Use one of the following commands:
- java -Dawt.useSystemAAFontSettings=on
- env _JAVA_OPTIONS=-Dawt.useSystemAAFontSettings=on java
For more information about turning on the antialiasing settings, refer to Java 2D API FAQs.
# 6773520 Issues With the Slovak Keyboard
Description
During installation of the OpenSolaris OS, if the Slovak Keyboard or Slovak Language is selected, some of the keys of the layout do not work.
Workaround
Choose one of the following workarounds:
- Use IIIMF instead of the Xorg Keyboard map:
- Reboot the system after installation and log in as a regular user.
- Open a terminal and type kbd -s and select US-English.
- Open 'Input Method Preference Editor' and select 'US/English' as 'Physical Keyboard Layout' in the 'Keyboard' tab.
- Add 'Slovak' Keyboard in the 'Languages / Scripts' tab and click on the Apply button.
*1.
- Log out of the system and re-login as a regular user.
The US-English keyboard layout has been set. Use IIIMF to set the Slovak Keyboard Layout. - Use the new Slovak kb layout map:
- Reboot the system after installation and log in as a regular user.
- Open a terminal and log in as the root user.
- Replace /usr/X11/lib/X11/xkb/symbols/sun/sk with the new Slovak kb layout map 'sk'. Click here to download the new Slovak kb layout map.
- Log out of the system and re-login as a regular user.
- (Optional) To switch to the US-English keyboard layout, use the setxkbmap us command. To switch back to the Slovak keyboard layout, use the setxkbmap sk command.
# 6775600 Audio Is Unavailable After Installation of OpenSolaris 2008.11 RC2
Description
On some laptop models, audio might not work after installation of the OpenSolaris 2008.11 RC2 build. An error message similar to the following is displayed in the output of the dmesg command in the log file at /var/adm/messages:
Nov 24 15:30:59 opensolaris audiosup: [ID 718941 kern.warning] WARNING: audiohd0: init_controller() no codec exists Nov 24 15:30:59 opensolaris audiosup: [ID 592854 kern.warning] WARNING: audiohd0: audiohd_attach() couldn't init controller Nov 24 15:30:59 opensolaris usba: [ID 723738 kern.info] /pci@0,0/pci1179,1@1a,7/communications@4 (usb_mid0): can't support ugen for multiple configurations devices that have attached child interface drivers
Workaround
The BIOS setup screens on some laptop models have an entry called 'Device Config' that might be set to 'Setup by OS'. Change the setting of 'Device Config' to 'All Devices'.
Use the following procedure:
- Enter the BIOS setup.
- Ensure that 'Device Config' is set to 'All Devices' instead of 'Setup by OS'. Now BIOS will configure all devices and not rely on the OS Software for initial configuration.
Note: If the workaround does not resolve your audio issue, there might be another problem or defect. Please consider discussing the issue through email on the laptop-discuss@opensolaris.org forum or filing a defect report at http://defect.opensolaris.org/bz/.
Terms of Use
|
Privacy
|
Trademarks
|
Copyright Policy
|
Site Guidelines
|
Site Map
|
Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.
© 2012, Oracle Corporation and/or its affiliates.