GNOME 2.0 Desktop for the Solaris Operating Environment Troubleshooting Guide

Chapter 5 Problems With Specific Applications

This section provides information about problems and associated workarounds for specific applications.

5.1 Dynamically-Set Title Does Not Work

Problem  

Bug ID 4855527, Terminal.

In the Editing profile window, Title and Command tab, the menu options for the drop-down menu Dynamically-set title do not work. Terminal uses the following bash shell environment variable to set the dynamically-set title and the shell prompt:

PROMPT_COMMAND=$'echo -ne "\\033]0;${USER}@${HOSTNAME}: ${PWD}\\007"' PS1=$'[\\u@\\h \\W]\\$ ' USER=`id -un`

On Linux /etc/bashrc sets the required environment variables, but does not set these variables for the Solaris operating environment. Hence, the dynamically-set title and the shell prompt do not work in the Solaris operating environment.

Solution  

As a workaround you can set the required environment variable by executing scripts for the various shells. 

bash shell: 

Set the following in bashrc:

case $TERM in
         xterm*)
             PS1="\[\033]0;\u@\h: \w\007\]bash\\$ "
             ;;
         *)
             PS1="bash\\$ "
             ;;
     esac

(or)

USER=`/usr/xpg4/bin/id -un`
export USER

PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007"'

ksh shell: 

Add the following in the ~.profile file:

mycd () {
cd "${@}"; echo "\033]0;${USER}@${HOSTNAME}: ${PWD}\007\c"
}
alias cd=mycd

csh shell: 

Set the following in cshrc:

switch ($TERM)
         case "xterm*":
             set host=`hostname`
             alias cd 'cd \!*; echo -n "^[]0;${user}@${host}:
${cwd}^Gcsh% "'
             breaksw
         default:
             set prompt='csh% '
             breaksw
     endsw

The '^[' and '^G' characters in the prompt string are single characters for ESC and BEL. You can enter these characters using Ctrl+v+ESC and Ctrl+v+g.

5.2 ScrollKeeper Options Not Fully Documented

Problem  

ScrollKeeper.

In the scrollkeeper-rebuilddb man page, the -o and -p options are not fully documented.

Solution  

You do not need to use the -o and -p options to perform a standard setup of the ScrollKeeper database. These options are required only in the following situations:

  • The ScrollKeeper database must be installed in a location other than the standard location. For example, setting up diskless clients.

    Use the -p path option to specify the location of the ScrollKeeper database, where path is an empty directory. The scrollkeeper-rebuilddb command will not proceed if you specify a populated path for this option.

  • The OMF files must be read from a location other than the standard location. The standard location for OMF files is specified in the /etc/scrollkeeper.conf file.

    Use the -o path option to specify the location of the OMF files. Specify the complete pathname, for example, /usr/share/omf. If you specify a partial pathname, for example, /usr/share, the scrollkeeper-rebuilddb command will take a long time, produce many warnings, and may crash.

The following example shows how to use the -o and -p options to set up the ScrollKeeper database for diskless clients:


# scrollkeeper-rebuilddb \
-p /export/root/clone/Solaris_9/\
sun4u/var/gnome/lib/scrollkeeper \
-o /export/exec/Solaris_9_sparc.all/\
usr/share/omf

5.3 Table of Contents is Empty in Help Page

Problem  

Bug id 4875223. 

The Table of Contents is missing from the first page in the GNOME Help browser.

Solution  

This is a ScrollKeeperissue. See 1.6 ScrollKeeper Fails After Installation for the workaround.