GNOME 2.0 Desktop for the Solaris Operating Environment Troubleshooting Guide

Chapter 1 Installation Problems

This section provides tips about dealing with problems that arise when you install the GNOME 2.0 Desktop on the SolarisTM 8 operating environment or Solaris 9 operating environment.

1.1 Installation Log


Where do I look for installation errors? 


The most recent GNOME 2.0 Desktop installation log is in the following location: /var/sadm/install/logs

1.2 Installation Failed Error Message


The installation fails with the following error message: pkgadd: ERROR: cppath(): unable to start


You are either using the wrong version of tar or the tar file is corrupt. You must use Solaris tar or GNU tar version 1.13 or greater. If the tar file is corrupt, you must download the tar file again. 

1.3 Uninstalling the GNOME 1.4 Desktop


I already have the GNOME 1.4 Desktop on system. How do I uninstall the GNOME 1.4 Desktop? 


Perform the following steps:  

  1. Log into CDE as root.

  2. Open a terminal window.

  3. Type cd /var/sadm/prod

  4. Type java uninstall_gnome_1_4

If you have already installed the GNOME 2.0 Desktop, you can remove the GNOME 1.4 Desktop by logging in as root and running the following command: /usr/sbin/remove-gnome -version 1.4

1.4 Uninstalling the GNOME 2.0 Desktop


How do I uninstall the GNOME 2.0 Desktop? 


Perform the following steps:

  1. Log in as root.

  2. Run the following command: /usr/sbin/remove-gnome

1.5 Installing the GNOME Desktop Without the Installer


How do I install the GNOME 2.0 Desktop without the GUI installer? 


Run the alternative text-based install script. To do this you must first unpack the tar file to create a GNOME directory in your current directory. Then run the script which corresponds to your system architecture:  

SPARC Architecture Edition: ./GNOME/sparc/pkgs/install

x86: Architecture Edition: ./GNOME/i386/pkgs/install

1.6 ScrollKeeper Fails After Installation


ScrollKeeper fails after Jumpstarts, upgrades and live upgrades. 


ScrollKeeper fails due to software dependencies not being available. The workaround is as follows: 

For all installations, upgrades and live upgrades that install directly into the root filesystem, the ScrollKeeper database is propagated during the installation, using a postinstall script provided with each package as required. 

For all other installations that do not install into the root filesystem directory, the postinstall script does not propagate the ScrollKeeper database. 

You must propagate the ScrollKeeper database manually when you log in for the first time. You need root access to perform this action. Execute the following commands in the C locale: 

  1. su password

  2. /usr/bin/scrollkeeper-rebuilddb

In some cases, the location of /usr/bin/scrollkeeper-rebuilddb might be similar to the following: {INSTALL_ROOT}/usr/bin/scrollkeeper-rebuilddb