This section describes issues that apply to the Sun Java Desktop System (Java DS) in the Solaris 10 OS.
This section describes issues related to Email and Calendars.
If you drag and drop email messages to a new email message body, the content of the new email message is corrupted.
Workaround: To send multiple attachments, perform the following steps:
Select the messages you want to attach.
On the Menu bar, choose Action => Forward => Attached.
Alternatively, you can press Ctrl-J to send the messages.
After you change the authentication type for the incoming mail server, Email and Calendar might not work correctly.
Workaround: Restart Email and Calendar.
After you import an LDAP Data Interchange Format file containing several contacts, only some of the contacts are displayed in your contact folder. This is a display problem only. Email and Calendar has imported all the contacts.
Workaround: Restart Email and Calendar.
This section describes login issue.
You might encounter the following error message when you log in to a Java Desktop System session:
Could not look up internet address for hostname. This will prevent GNOME from operating correctly. It may be possible to correct the problem by adding hostname to the file /etc/hosts |
Workaround: Ensure that your hostname is set up correctly in the /etc/hosts file. Perform the following steps:
Set the hostname in the /etc/hosts file as follows:
127.0.0.1 localhost loghost hostname localhost.localdomain |
hostname is the name of your system.
Ensure that your hostname is listed in the /etc/nodename file. This file must also contain the following line:
127.0.0.1 localhost loghost hostname localhost.localdomain |
When you log into Java Desktop System Release 3, your $PATH is set incorrectly to the following:
/usr/bin::/usr/dt/bin:/usr/openwin/bin:/bin: /usr/ucb:/usr/openwin/bin:/usr/dt/bin |
Workaround: Remove the following from your $PATH:
/usr/openwin/bin:
/bin:
::
The resulting path should be similar to the following example:
/usr/bin:/usr/dt/bin:/usr/ucb:/usr/openwin/bin:/usr/dt/bin |
If you use dtlogin remote connection, you cannot connect to the GNOME Display Manager from certain systems.
Workaround: When you are prompted to select the remote login, specify the IP address instead of the hostname.
If you use the Yelp browser to open the online help for Volume Control, the help file for the Keyboard Accessibility panel application is opened instead.
Workaround: None.
If you open an application's online help and no help files exist for that application, an error dialog box is displayed. Unless you click OK, the online Help system freezes and you cannot open the online help of other applications that you start subsequently.
Workaround: You must click the OK button in the error dialog box.
You cannot print documents from the Mozilla browser if the documents contain Unicode characters that are not in the Basic Multilingual Plane (BMP).
Workaround: None.
In the Mozilla browser, you can specify that User Preferences should be transferred to and from the Roaming Access server. You specify your Roaming Access option by following these steps:
On the browser, click Edit and select Preferences.
Select Roaming User, then select Item Selection.
On the right panel, select User Preferences.
However, the selection of User Preferences does not take effect.
Workaround: None.
In the Mozilla browser, you enable caret browsing by pressing F7. When caret browsing is enabled, the keyboard shortcut Ctrl-Home brings you to the beginning of the web page that you are browsing. However, this keyboard shortcut does not work when you browse certain sites such as www.yahoo.com and www.mozilla.org.
Workaround: Disable caret browsing by pressing F7.
User preferences in your home account for an earlier version of the GNOME Desktop might be partly incompatible with the version on the Java DS Release 3.
Workaround: Reset your preferences. Perform the following steps:
Log out of the Java Desktop System.
Click Session and choose Failsafe terminal.
Log in.
In the failsafe terminal window, enter the following commands:
% gnome-cleanup exit |
Log in again.
Your GNOME preferences are now reset.
The GNU Image Manipulation Program (GIMP) is not available in the Graphics menu.
Workaround: Perform the following steps.
Open a terminal window.
Edit the /usr/share/applications/gimp-2.0.desktop file.
Change the Exec and TryExec lines to add the full path to the GIMP binary:
TryExec=/usr/sfw/bin/gimp2.0 Exec=/usr/sfw/bin/gimp-remote-2.0 %u |
You might be unable to complete the online registration of the StarOffice 7 software if the software cannot find Mozilla on the system. The software must be able to locate the Email and Calendar application to successfully send documents.
Workaround: Add /usr/sfw/bin to your PATH. Perform the following steps.
Open a terminal window.
Issue the following command:
% export PATH=/usr/sfw/bin:$PATH |
To start the StarOffice software, issue the following command:
% soffice |
Complete the StarOffice registration procedure.
The slide bar and the side counter do not work when the Sound Recorder is recording a new.wav file.
Workaround: None.
The option in the Volume Control panel application that enables you to start the Volume Control desktop applications does not work.
Workaround: None.
In the Solaris software, you restrict application launching by setting to true the /desktop/gnome/lockdown/restrict_application_launching gonf key. This setting allows only certain applications to appear on the Launch menu where you can start these applications. The allowed applications are listed in the /desktop/gnome/lockdown/allowed_applications gonf key.
Currently, the list includes applications that are outdated and are no longer included in the Java Desktop System software. Moreover, the list also contains references to certain applications with incorrect directory locations. Consequently, if you restrict application launching, certain key applications such as Mozilla or StarOffice do not appear on the Launch menu.
Workaround: Perform the following steps.
Become superuser.
Remove the ~/.gconf/desktop/gnome/lockdown directory if the directory exists.
# rm -rf ~/.gconf/desktop/gnome/lockdown |
Log out of the system and then log in again.
Using the keyboard indicator might make the keyboard unusable when you switch between X servers.
Workaround: None. Do not use the Keyboard Indicator.
The File Manager might fail if you use the following View options:
View as Catalog
View as Image Collection
Depending on the View options that you use, the following error messages might be displayed:
Error:
The application nautilus has quit unexpectedly |
Error:
The Catalog view encountered an error while starting up |
Error:
The Image Collection view encountered an error while starting up |
Workaround: None. Every time these problems occur, restart File Manager or click the Restart Application button on the crash dialog box.
If you use the Sound Recorder multimedia application in CD Quality, Lossless mode, the application fails when recording starts. The following error message is displayed:
The Application "gnome-sound-recorder" has quit unexpectedly. |
Workaround: Perform the following steps.
Become superuser.
Issue the following command:
# GCONF_CONFIG_SOURCE=xml::/etc/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule /etc/gconf/schemas/gnome-audio-profiles.schemas |
In addition, existing users must perform the following steps.
If the gnome-audio-profiles-properties application is running, stop the application by closing the application window.
If the profile cdlossless exists in ~/.gconf/system/gstreamer/audio/profiles, remove the profile.
% rm ~/.gconf/system/gstreamer/audio/profiles/cdlossless |
Log out of the system and then log in again.
You can only delete files from your own home directory file system.
Workaround: To delete files outside your home directory file system, open a terminal window and use the command line.
You cannot use Archive Manager to create the following types of archives:
.arj
.lha
.bzip
.lzop
.zoo
Workaround: None.