This section describes desktop issues in the Oracle Solaris 11.3 release.
The Evolution email application does not start after installing Oracle Solaris.
Workaround: After installing Evolution, log out and log in again. The application will start successfully.
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.
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.
|
To implement the workaround, perform the following steps:
Connect the USB devices.
The recommended USB connectors for the devices on various platforms are listed in Figure 4, Table 4, Recommended Usage of USB Connectors and Values.
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 T3–4 and you are using a physical keyboard, set ehci-port-forced-to-companion=3.
For information about the value that you can set for this variable, see Figure 4, Table 4, Recommended Usage of USB Connectors and Values.
Reboot the system.
# init 6
When Trusted Extensions is enabled, users are logged out after 15 minutes of idle time. However, the default value of idletime in the user_attr (1M) database specifies to lock the screen after 30 minutes.
Workaround: To restore the default behavior, add the following properties in the /etc/security/policy.conf file:
idletime=30 idlecmd=lock
Note that the idlecmd setting is ignored unless idletime is also specified. These properties can also be customized for individual users by using the usermod command. For more information, see the usermod(1M) man page.
After upgrading Firefox to version 31.1.x, the plugin container leaves core whenever plugins are made active. No error message is displayed, but the plugin-container binary crashes.
Workaround: Disable all the plugins by performing the following steps:
Choose Add-ons from the Tools menu.
Click the Plugins tab.
Select the Never Activate option from the drop-down list for each plugin.