Go to main content

Oracle® Solaris 11.4 Release Notes

Exit Print View

Updated: April 2018
 
 

Desktop Issues

This section describes desktop issues in the Oracle Solaris 11.4 release.

Window Titles are Not Displayed (27663280)

In the April 2018 update to Oracle Solaris 11.4 Beta, window titles are not displayed in the title bar for xterm and other applications that use toolkits other than GTK+.

One of the following warnings might be displayed:

Warning: locale not supported by Xlib, locale set to C
Warning: X locale modifiers not supported, using default

The following error message might be displayed:

xterm: Failed to open input method

Workaround: Set all locale facets to true.

$ pkg change-facet "locale.*=True"

GNOME 3: The Same User Cannot Run Multiple VNC Sessions (27275811)

You cannot start multiple simultaneous GNOME 3 sessions with the same uid.

Cannot Change Mouse Handedness in GNOME 3.24 (27372205)

Selecting Left in Settings → Mouse/Touchpad does not cause the mouse buttons to operate as a left-handed mouse.

Workaround: Use the xmodmap command to configure the mouse to be used as a left-handed mouse, as shown in the following example:

$ xmodmap -e "pointer = 3 2 1"

SPARC: Desktop Issues With USB Keyboard, Mouse, and Physical Monitor (15700526)

When using a physical keyboard, mouse, or monitor, repeated attempts to open and use a terminal window on the Oracle Solaris Desktop can result in loss of characters and mouse control.

This issue might occur because of errors caused by missing microframes. These errors occur when full or low-speed USB 1.0 or 1.1 keyboard and mouse devices are connected to the USB ports on a system under an onboard USB 2.0 hub. However, these errors do not occur when the keyboard and the mouse devices are connected to a system USB port, which is in turn connected to an internal hub that is manually bound to the ohci (USB 1.0 or 1.1) driver.


Note -  If you are using a virtual keyboard and mouse, all devices under the hub are forced to run at low speed. The devices will still work, but they run at a lower USB 1.0 or 1.1 speed.

Workaround: Set the value for the ehci-port-forced-to-companion variable in the /kernel/drv/ehci.conf file. The value of this variable is used by the ehci (USB 2.0) driver to release control of a particular port on the USB controller.

The value of the ehci-port-forced-to-companion variable differs based on the type of platform and the type of USB device used. The following table lists the recommended usage of USB connectors and the corresponding value of the ehci-port-forced-to-companion variable.

Table 2  Recommended Usage of USB Connectors and Values
SPARC Platform
Type of USB Device
Recommended Usage of USB Connectors
Value of the ehci-port-forced-to-companion Variable in the /kernel/drv/ehci.conf File
T4-1, T4-2
Physical keyboard or mouse
Use the front USB connector
4
T4-4
Physical keyboard or mouse
Use the rear USB connector
3
T4-1, T4-2, T4-4
Virtual keyboard or mouse
None
2

To implement the workaround, perform the following steps:

  1. Connect the USB devices.

    The recommended USB connectors for the devices on various platforms are listed in Figure 2, Table 2, Recommended Usage of USB Connectors and Values.

  2. Set the value of the ehci-port-forced-to-companion variable in the /kernel/drv/ehci.conf file.

    For example, if the SPARC platform is T4–4 and you are using a physical keyboard, set ehci-port-forced-to-companion=3.

  3. Reboot the system.

    # init 6