Common Desktop Environment

The following bugs in Solaris 10 OS apply to the Common Desktop Environment (CDE).

Trusted Stripe Crashes When Users Change Roles (6495454)

Trusted Stripe crashes when you change roles on any locale except the C locale.

Workaround: Perform any one of the following steps:

Use the C locale.
Remove the usr/share/locale/$locale/LC_MESSAGES/tsoljds-tstripe.mo file from the login locale.

Nautilus ACL MASK is Not in Sync With Group Permissions (6464485)

The Group permissions in the Permissions tab should be the same as the Mask permissions in the Access Tab, but on some occasions they appear out of sync.

Workaround: Click the Close button, and then click Reload. View the file properties again. The Group permissions and the Mask permissions will now be in sync again. The permissions are set to what you changed the Mask to in the previous step.

SMC CLI Commands Do Not Process the Solaris Trusted Extensions Options (6447833)

This bug affects management of Solaris Trusted Extensions by using the SMC. When the SMC command line with the -B toolbox option is used to pass in the Trusted Extensions options, the command is not executed. This failed execution prevents the use of the SMC CLI to manage Solaris Trusted Extensions. The following error message is displayed:

There was an unrecognized extended, nonstandard option specified with the -x option.
Please refer to man pages for additional information and correct syntax usage

Workaround: Use the SMC GUI for administration of users, roles, and profiles.

Mouse Pointer and the `dtfile` Icon Are Not Displayed When You Drag the `dtfile` Icon (6462945)

When you drag the dtfile icon, the icon and the the mouse pointer might not be displayed. No error message is displayed.

Workaround: Add the following lines to the /usr/dt/config/<locale>/sys.resources file , under #if EXT_SUN_TS OL:

!! DragNDrop protocol. Other styles cause policy violation.
*DragInitiatorProtocolStyle:            DRAG_DYNAMIC
*DragReceiverProtocolStyle:             DRAG_DYNAMIC

SMC Updates the `tnrhdb` File But Does Not Run `tnctl` to Update the Trusted Host Cache (6471594)

When the SMC is used to manage network security templates, the /etc/s ecurity/tsol/tnrhdb file is updated but the tndb cache is not updated. Network security definitions do not take effect. No error message is displayed.

Workaround: After you modify a network entry in the SMC, manually refresh the tndb cache with one of the following commands:

Modify an entry in the file scope:

# /usr/sbin/tnctl -H /etc/security/tsol/tnrhdb

Modify an entry in the LDAP scope:
```
# /usr/sbin/tnctl -H <hostname>
```

Cannot Login Using GDM Unless Clearance is Set to `admin_high` (6432114)

The login fails when you log in to the Solaris Trusted Extensions Java Desktop Systems (JDS) by using GDM. This failure is caused by the PAM configuration. The pam.conf(4) file does not contain the required entries for GDM.

On login, the following error message is displayed:

The system administrator has disabled access to 
the system temporarily

Workaround: Add the following two lines to the /etc/pam.conf file:

gdm account requisite pam_roles.so.1
gdm account required pam_unix_account.so.1

For information about the file format, see the pam.conf(4) man page.

Trusted Stripe Disappears From The Screen After Resolution Change (6460624)

When you type the /usr/X11/bin/xrander -s command to set a smaller screen resolution, Trusted Stripe is no longer displayed. This affects the Trusted CDE Desktop but not the Trusted Java DS Desktop. No error message is displayed.

Workaround: After the resolution changes, restart the Workspace Manager. Select windows -> Restart Workspace Manager from the CDE workspace menu and click OK.

Secure Attention Key or Hot Key Does Not Work on x86 Systems (6486416)

The Secure Attention key or hot key, Alt+Break, on PC keyboards does not work on x86 systems. No error message is displayed.

Workaround: None.

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:

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.
Create a new xorg.conf file.
```
# /usr/X11/bin/Xorg -configure
```
The command creates the file xorg.conf.new in the root (/) directory.
Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.
```
# cp /xorg.conf.new /etc/X11/xorg.conf
```
Modify the configurations in the file by using the following sample configurations:
- Add a new monitor section.
```
Section "Monitor"
     Identifier   "monitor_dummy"
     ModelName    "dummy"
     HorizSync    10-200
       VertRefresh  20-90
    EndSection
```
- Add a new device section.
```
Section "Device"
   BoardName    "dummy"
   Driver       "dummy"
   Identifier   "device_dummy"
   VendorName   "dummy"
   videoram    10000
EndSection
```
  Note - You might need to adjust the videoram value, depending on the screen width, height, and color depth of your particular graphics card. The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8.
- Add a new screen section.
```
Section "Screen"
   DefaultDepth 24
   SubSection "Display"
     Depth      24
     Modes      "1280x1024"
   EndSubSection
   Device       "device_dummy"
   Identifier   "screen_dummy"
   Monitor      "monitor_dummy"
EndSection
```
  Note - You might need to adjust the resolution value for your particular system setup.
Look for the following line under the ServerLayout section:
```
Screen      0  "Screen0" 0 0
```
Insert the following line below the line in the previous step:
```
Screen      1  "screen_dummy" RightOf "Screen0"
```
This new line defines Screen1, a second dummy screen that is notionally to the right of Screen0, the physical and primary screen.
Save the changes.
Reboot the system from the appropriate command-line session:
- If you are using GDM, perform the following:
  1. Type svcadm enable application/gdm2-login.
  2. Reboot the system.
- If you are using dtlogin, reboot the system and log in.
Start the Gnopernicus screen reader.
Change the Startup Mode to Magnifier.
Click Preferences, then select Magnifier.
Click Add/Modify.
Assign the following values for Magnifier preferences:
- For Source: 0.1
- For Zoomer Placement:
  - Left and Top: 0
  - Bottom and Right: maximum
Click Apply.

Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.

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 GNOME On-Screen Keyboard (GOK). The configuration fails when you are setting up the USB mouse device while using a PS2 mouse device as the core pointer. To properly set up the USB mouse, follow these steps.

Log in as superuser.
While the USB mouse device is unplugged, type the following in a terminal window:
```
# ls -l /dev/usb/hid*
```
Connect the USB mouse and type the previous command again.
Record the path of the USB mouse that is displayed on the screen.
Log in to a command-line session.
- If you are using the GNOME Display Manager, follow these steps:
  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.
Create a new xorg.conf file.
```
# /usr/X11/bin/Xorg -configure
```
The command creates the file xorg.conf.new in the root (/) directory.
Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.
```
# cp /xorg.conf.new /etc/X11/xorg.conf
```
Modify the configurations in the file:
- In the ServerLayout section, add an input device for Mouse1 after the line InputDevice "Mouse0" "CorePointer". See the following example:
```
InputDevice   "Mouse0" "CorePointer"
InputDevice   "Mouse1"
```
- In the InputDevice section that contains the line Identifier "Mouse0", apply the following changes:
  - Change Option "Device" "/dev/mouse" to Option "Device" "/dev/kdmouse".
  - Change Option "Protocol" "auto" to Option "Protocol" "VUID".
  - Add the following new Option:
```
Option    "StreamsModule" "vuid3ps2"
```
  After you have applied the changes, the section should appear similar to the following example:
```
Section "InputDevice"
   Identifier  "Mouse0"
   Driver      "mouse"
   Option      "Protocol" "VUID"
   Option      "Device" "/dev/kdmouse"
   Option      "StreamsModule" "vuid3ps2"
EndSection
```
- Create a new InputDevice section after the preceding InputDevice section:
```
Section "InputDevice"
   Identifier  "Mouse1"
   Driver      "mouse"
      Option      "Device" "/dev/usb/hid1"
EndSection
```
  Note - /dev/usb/hid1 is an example path for the USB mouse. Use the path in Step 4 to replace /dev/usb/hid1.
Save the file and exit.
Reboot the system from the appropriate command-line session:
- If you are using GDM, perform the following:
  1. Type svcadm enable application/gdm2-login.
  2. Reboot the system.
- If you are using dtlogin, reboot the system.
Log in to the accessible UI user's account.
Enable Assistive Technology Support by clicking Launch Menu => Preferences => Accessibility => Assistive Technology Support.
Log out of the system then log in to the accessible UI user's account again.
Open a terminal window and type the following command:
```
% /usr/sfw/bin/gok --select-action=switch1
```
In the GOK window, click GOK and select Preferences.
If necessary, set up GOK to the accessible UI user's needs. Otherwise, to accept the current setup, click Apply then click OK in the GOK Preferences window.
Exit GOK and then restart it by clicking Launch Menu => Applications => Accessibility => On-Screen Keyboard. The following warning message might be displayed:
```
The device you are using to control GOK is
also controlling the system pointer.
```
Click OK.
Exit GOK and then repeat steps 14-17.

The warning message is no longer displayed.

x86: Support for Intel Integrated i810 and i815 Graphics Chipsets

Intel Integrated i810 and i815 Graphics Chipsets are not supported by the Xorg X Window System server. Support is available with the Xsun server. To configure the Xsun server to use these chipsets, follow these steps:

Become superuser.
Run the program to configure keyboard, display, and mouse.
```
# kdmconfig
```
On the Introduction and X Server Selection screen, select the Xsun server.

On the View and Edit Window System Configuration screen, Intel i810/i815 (4MB) should be automatically selected and displayed as the Video Device.
If the Intel i810 and i815 Chipsets are not automatically selected, select the Change Video Device/Monitor option.
On the Video Device Selection screen, select the Intel i810/i815 (4MB) option.
Continue to select other kdmconfig options.

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

Full-Screen Magnification and Keyboard Accessibility Features Not Working (6273030)

On your Java Desktop System software, you cannot set up the following:

Full-screen magnification
Keyboard accessibility features

Workaround: Perform the following steps:

Open the /etc/X11/gdm/gdm.conf file.
Depending on your system's platform, perform the following:
- On SPARC based systems:
  1. Look for the line in the file that begins as follows:
```
command=/usr/openwin/bin/Xsun
```
  2. Append the following modification to the line:
```
+kb +accessx -dev framebuffer1 -dev 
framebuffer2
```
    For example:
```
+kb +accessx -dev /dev/fbs/pfb1 -dev /dev/fbs/pfb0
```
- On x86 based systems:
  1. Look for the line in the file that begins as follows:
```
command=/usr/X11R6/bin/Xorg
```
  2. Append the following modification to the line:
```
+kb +accessx
```

x86: `kdmconfig` Command Does Not Create System Identification Configuration File for Xorg X Server (6217442)

If you use the JumpStart installation method, the process might use a system identification configuration (sysidcfg) file. This file is used to generate a specific Xsun configuration file for a system. The Xsun configuration portion of a sysidcfg file is created by the command kdmconfig -d filename. However, on systems that use the default Xorg server, the command does not create a file with any Xorg configuration information. Consequently, you cannot use the JumpStart method on these systems without some additional preparatory steps.

Workaround: Before using the JumpStart installation method on a system that uses the Xorg server, perform the following steps.

Prepare a specific xorg.conf file to be used on the system. Store this file in the JumpStart directory of the JumpStart server.

For instructions to create an xorg.conf file and to access Xorg information, see x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669).
Create a finish script that copies the xorg.conf file to the /etc/X11 directory in the system that you want to install. For example, the script might include the following line:
```
cp ${SI_CONFIG_DIR}/xorg.conf /etc/X11/Xorg.conf
```
In the custom JumpStart rules file, include the finish script in the rules entry for systems of the type that you want to install.
Perform the custom JumpStart installation.

For instructions about how to perform a custom JumpStart installation, see the Solaris 10 11/06 Installation Guide: Custom JumpStart and Advanced Installations. Chapter 4 includes information about the JumpStart rules file, while Chapter 5 contains a section about finish scripts.

x86: `kdmconfig` Instructions to Configure Xorg X Server Are Incomplete (6205881)

Instructions that are provided in the kdmconfig program to configure the Xorg server are incomplete. The program lists basic instructions to generate an xorg.conf file. However, some relevant information is unavailable. For example, options in the xorg.conf file can be overridden in several places:

Command-line options
Information that is detected by the Xorg server when the server starts
The startup scripts for the Xorg server, which might include passing overriding arguments

Thus, for more information about Xorg configuration, refer to the following sources:

Xorg(1x) man page in the /usr/X11/man directory
Man pages for the desktop systems that use the X server, such as the following:
- dtlogin(1X) in the /usr/dt/man directory
- gdm(1) in the /usr/share/man directory

If these directories are not in your man path, use one of these options:

Add the directory to the MANPATH environment variable setting.
Use the -M directory option of the man command.

Some scripts that start the Xorg server use smf(5) repository properties. In particular, the FMRI svc:/applications/x11/x11-server is used for storing X server properties. The following properties are relevant to the Xorg server:

options/xserver
options/default_depth
options/server_args

You can set and retrieve these properties by becoming superuser and using the svccfg command, as shown in the following example:

# svccfg 
svc:> select application/x11/x11-server 
svc:/application/x11/x11-server> listprop options/default_depth options/default_depth integer 24


 
svc:/application/x11/x11-server> setprop options/default_depth = 8 
svc:/application/x11/x11-server> listprop options/default_depth options/default_depth integer 8


 
svc:/application/x11/x11-server> end
#

x86: Program That Configures Keyboard, Display, and Mouse Not Working for X Server (6178669)

In this current Solaris 10 release, the default X server has changed from Xsun to Xorg. The program that configures keyboard, display, and mouse ( kdmconfig ) applies only to the Xsun server. The program has no effect on Xorg server configuration. Consequently, you cannot use kdmconfig to configure the Xorg server. While kdmconfig allows you to select which server to use, kdmconfig only configures the Xsun server.

Workaround: To configure the Xorg server, perform the following steps:

Create an xorg.conf file with one of these commands:
- /usr/X11/bin/Xorg -configure
- /usr/X11/bin/xorgconfig
- /usr/X11/bin/xorgcfg
Edit the resultant xorg.conf file with the necessary changes.
Move the xorg.conf file to /etc/X11/xorg.conf.

For more details about Xorg configuration, refer to the Xorg man pages in /usr/X11/man. This directory is not in the default man page path. To view these man pages, use one of the following options:

Add the path to the settings of the environment variable MANPATH .
Use the syntax man -M /usr/X11/man.

Note - Xorg command line options can override xorg.conf settings. See the man pages for more details about options to use with Xorg.

CDE Removable Media Auto Run Capability Removed (4634260)

The Removable Media auto run capability in the CDE desktop environment has been temporarily removed from the Solaris 10 software.

Workaround: To use the auto run function for a CD-ROM or another removable media volume, you must do one of the following:

Run the volstart program from the top level of the removable media file system.
Follow the instructions that are included with the CD for access from outside of CDE.

Solaris PDASync Cannot Delete Last Entry From the Desktop (4260435)

After you delete the last item from the desktop, the item is restored from the handheld device to the desktop when you synchronize your handheld device. Examples of items that you might delete, and then have restored, are the last appointment in your Calendar or the last address in the Address Manager.

Workaround: Manually delete the last entry from the handheld device prior to synchronization.

Skip Navigation Links
Exit Print View
	Solaris 10 11/06 Release Notes