## Adobe® Reader® 9.1 for Linux® and Solaris®

Welcome to Adobe Reader 9.1 software for Linux and Solaris operating systems. Adobe Reader is the free viewing companion for Adobe applications that produce Adobe Portable Document Format (Adobe PDF) files. To create, enhance, review, edit, and share information in Adobe PDF files, use Adobe Acrobat® 9.0 Professional and Adobe Acrobat 9.0 Standard software. Learn more about Acrobat software by visiting www.adobe.com/products/acrobat.

Click the following links to learn more about Adobe Reader 9.1.0 for Linux and Solaris:

- System requirements
- Installing and starting Adobe Reader 9.1.0
- Web browser support
- Non-English languages
- MDI
- Troubleshooting
- Keyboard shortcuts
- Legal notices

## System requirements

Make sure that your system meets the minimum requirements to run Adobe Reader 9.1 software, as described in the following sections.

### System requirements for Linux

- 32-bit Intel® Pentium® processor or equivalent
- Red Hat® Linux WS 5, SUSE® Linux Enterprise Desktop (SLED) 10 SP2 and Ubuntu 7.10
- 512 MB of RAM (1 GB recommended)
- 175MB of available hard-disk space (additional 75MB required for all supported font packs)
- GTK+ (GIMP Toolkit) user interface library, version 2.6 or later
- Firefox 2.0 or later
- CUPS libraries (1.2 or above)

### System requirements for Solaris®

- 32-bit Intel Pentium processor or equivalent
- Solaris 10 u5 and OpenSolaris 2008.11
- 512 MB of RAM (1 GB recommended)
- 200MB of available hard-disk space (additional 75MB required for all supported font packs
- GTK+ (GIMP Toolkit) user interface library, version 2.6 or later (on Solaris 10; also works with GTK 2.4.9)
- Firefox 2.0 or later
- CUPS libraries (1.2 or above)

## Installing and starting Adobe Reader 9.1

### Installation instructions

You can use any of the following methods to install and uninstall Adobe Reader 9.1 software for Linux and Solaris. You must be logged on as the root user (superuser, administrator) to install the software using the RPM, DEB or PKG (only for Solaris) package.

By default, if you install using the RPM, DEB on Linux and PKG package on Solaris, Adobe Reader is installed at /opt/Adobe/Reader9. You can, however, specify a different location.

### To install Adobe Reader 9.1 using a .bin installer

1. Open a terminal window.

2. Change directory (using the `cd` command) to the directory that contains the bin file.

3. Make sure that .bin installer has the execute permissions. If not then run

`chmod u+x AdbeRdr9.1.0-1_i486linux_enu.bin`

4. Run the following command:

`./AdbeRdr9.1.0-1_i486linux_enu.bin`
By default Adobe Reader is installed in /opt/Adobe. You can however, specify a different location by using the following command-line option: --install_path= <dir path where you want to install>

5. Add <reader_install_dir>/bin to the PATH environment variable to allow browsers to launch Adobe Reader, where <reader_install_dir> is the installation directory of Adobe Reader 9.1.

### To install Adobe Reader 9.1 using an RPM installer in the GNOME environment

1. Open the RPM package by double clicking on it.

2. When prompted, enter the root password for your system, and click OK.

3. Click Continue in the Complete System Preparation dialog box.

### To install Adobe Reader 9.1 using an RPM installer in the KDE environment

1. Open the RPM package.

2. Click Install Package With YaST.

3. When prompted, enter the root password for your system, and click OK.

### To install Adobe Reader 9.1 using the command line: RPM package

1. Open a terminal window.

2. Change directory (using the `cd` command) to the directory that contains the RPM package.

3. Run the following command as an administrator or root:

`rpm -i AdbeRdr9.1.0-1_i486linux_enu.rpm`

### To install Adobe Reader 9.1 using the command line: DEB package

1. Open a terminal window.

2. Change directory (using the `cd` command) to the directory that contains the DEB package.

3. Run the following command as an administrator or root:

`dpkg -i AdbeRdr9.1.0-1_i386linux_enu.deb`

### To install Adobe Reader 9.1 using the command line: PKG package (only for Solaris)

1. Open a terminal window.

2. Change directory (using the `cd` command) to the directory that contains the PKG package.

3. Unzip the package using following command:

`bunzip2 AdbeRdr9.1.0-1_i386solaris_enu.pkg.bz2`

4. Run the following command as an administrator or root:

`pkgadd –d AdbeRdr9.1.0-1_i386solaris_enu.pkg`

### To install Adobe Reader 9.1 using a tarball installer

1. Open a terminal window.

2. Change directory (using the `cd` command) to the directory that contains the tarball archive.

3. Run following command

`

bunzip2 AdbeRdr9.1.0-1_i486linux_enu.tar.bz2

tar -xvf AdbeRdr9.1.0-1_i486linux_enu.tar

`

4. In the newly created AdobeReader directory, run the INSTALL script. By default, on Linux, Adobe Reader is installed in /opt/Adobe. You can however, specify a different location by using the following command-line option: --install_path= <reader_install_dir>

5. Add <reader_install_dir>/bin to the PATH environment variable to allow browsers to launch Adobe Reader, where <reader_install_dir> is the installation directory of Adobe Reader 9.1.

### To uninstall Adobe Reader 9.1 using the command line

1. Open a terminal window.

2.(a) In case of RPM installer:

Run the following command as an administrator or root:

`rpm -e AdobeReader_enu`

2.(b) In case of DEB installer:

Run the following command as an administrator or root:

`dpkg -r adobereader-enu`
2.(a) In case of PKG installer:

Run the following command as an administrator or root:

`pkgrm ADBEreadr-enu`

2.(d) In case of tarball or bin installer:

Run the following command:

`<reader_install_dir>/bin/UNINSTALL`

### Starting Adobe Reader and opening Help

### To start Adobe Reader

Run the acroread script. This script is in the <reader_install_dir> /bin directory, where <reader_install_dir> is the directory into which Adobe Reader 9.1 was installed.

### To open Help from the command line

Run the acroread script with `-help` as a command-line argument. This script is in the <reader_install_dir> /bin directory, where <reader_install_dir> is the directory into which Adobe Reader 9.1 was installed.

### Man Page And Bash-completion

Man page installation: It is a root installation.

Bash Completion : Users must have a bash completion package installed on their systems to use the bash completion capability. Also it should be a root installation.

## Web browser support

Adobe Reader 9.1 comes with a browser plug-in that allows you to view and use PDF files in a browser window. The plug-in is compliant with all browsers that support Gecko (including Firefox 2.0 or later).

### Installing the Browser plugin

Refer the file `<reader_install_dir>/Browser/HowTo/$LANG/Browser_Plugin_HowTo.txt` for information on the browser plugin provided along with Adobe Reader.

## Non-English languages

### To enable right-to-left language options in Adobe Reader

1. Choose Edit > Preferences.

2. In the Preferences dialog box, select International Categories and select Enable Right-To-Left Language Options.

3. Click OK.

For more details, refer Non-English languages section in Acrobat Help.

## MDI

Adobe Reader 9.1 for Linux/Solaris provides a tabbed document interface - multiple documents are contained in a single application window, with Tabs to navigate between them. Now you can choose to open your documents in tabs or in separate windows like Adobe Reader 8.0.

### To switch between the modes

  • Choose Edit > Preferences > Documents.
  • Uncheck Open documents in tabs (requires restart) in Open settings and restart Reader to open PDFs in separate windows.

The tabbed interface provides features to allow easier and better organization of the documents you are viewing.

### Rearrange tabs

  • To rearrange the tabs in a window, click and drag the tab to its new position.

Note: This feature is supported on distributions with Gtk+ version 2.10 or higher.

### Create new window from a tab

  Do one of the following:
  • You can move out a tab to create a new window. Click and drag the tab out of the current window.

Note: This feature is supported on distributions with Gtk+ version 2.10 or higher.

  • Right-click the tab, and choose Detach Tab.

### Move tab to a different window

  • To move a tab to a different reader window, click and drag the tab from its original window into the destination window.

Note: This feature is supported on distributions with Gtk+ version 2.10 or higher.

### Duplicate tab

  • To open the same document in a new tab in the same window, right click the tab, and choose Duplicate Tab.

### Close tab

  Do one of the following:
  • Click the [x] icon in the tab.
  • Right-click the tab, and choose Close Tab.

### Close Other Tabs

  • Right-click the tab, and choose Close Other Tabs.

### Close Tabs to the Left

  • Right-click the tab, and choose Close Tabs to the Left.

### Close Tabs to the Right

  • Right-click the tab, and choose Close Tabs to the Right.

You can change some of the preferences associated with tabs using the Preferences dialog box. The preferences settings control how the application behaves whenever you use it; they are not associated with any particular PDF document.

  • Choose Edit > Preferences > Documents and edit the preferences in Tab settings section.

### Show tabs at

Top Show tabs at the top below the menu bar.

Bottom Show tabs at the bottom of Reader window.

Show thumbnails on tab hover Determines whether page thumbnails are shown on hovering over the tabs. If this option is not selected, filename/title of the PDF will be shown.

Open new tab next to active tab Specifies whether to open a new tab next to the active tab or at the end.

When closing a tab, switch to last active tab Determines whether the last active tab comes into focus on closing a tab. If this option is not selected, the previous tab will come into focus.

Warn when closing multiple tabs Enables warning dialog that would appear when you close a window with multiple tabs.

### KeyBoard Shortcuts

Ctrl+Tab, Ctrl+Page Down for Next Tab

Ctrl+Shift+Tab, Ctrl+Page Up for Previous tab

Alt+1…9 for Switch to a tab(first 9)

## Troubleshooting

This section includes descriptions of various issues that may arise as you use Adobe Reader 9.1 for UNIX. If you experience problems when running Adobe Reader 9.1, this section may help you to determine their cause. For general product information and additional troubleshooting information, visit the Adobe Product Support Knowledge Base at www.adobe.com/support, or choose Help > Online Support in Adobe Reader.

### General

MIME type registrations and icon associations are not reflected after installation. Restart your desktop session for the changes to take effect. Note that on Linux this feature is only available for installations done using root privileges.

Chinese, Japanese, and Korean bold characters appear blurred. If the text was created in an application that used synthetic bolding, white areas or breaks in the text may appear when the text is magnified. To avoid this problem, enable the Smooth Text and Use CoolType options in the Page Display preferences.

Unable to create comments or bookmarks using the Hong Kong character set. Because the Hong Kong character set is not part of the standard system fonts, you cannot comment or create bookmarks using those characters. To solve this problem, install the Chinese Traditional Language pack (the Honk Kong character set is an extension of the Chinese Traditional set).

To view embedded html (such as Html Ads, ReviewTracker, etc.) within Adobe Reader, you need to add the path to firefox 1.5+ or Mozilla 1.7.3+(compiled with gtk2+) or xulrunner in the "Preferences > Internet > libgtkembedmoz/libxul Folder". This path may be present in the following file on your system: /etc/gre.d/gre.conf, in the following form: GRE_PATH=<path_to_be_picked_up>

Adobe Reader doesn't run correctly. Adobe Reader 9.1 needs access to the `pwd` command. As a result, Adobe Reader does not run correctly from a directory where the `pwd` command fails. To solve this problem, make sure that the `pwd` command runs in the bin/ directory of the Adobe Reader 9.1 installation directory.

Adobe Reader retains the preferences of a previous version. Before you run Adobe Reader 9.1 for the first time, you may want to remove the directory $HOME/.adobe, where $HOME is the user's home directory. Removing this directory ensures that Adobe Reader used the default preference settings when you start it for the first time.

Adobe Reader preferences are not saved. If the directory containing Adobe Reader preferences is not writable, the preferences cannot be saved. To solve this problem, make sure that the $HOME/.adobe directory, where $HOME is the user's home directory, is writable.

Third-party applications do not start when Adobe Reader 9.1 for is running using 32-bit emulation on a 64-bit machine. When running in 32-bit emulation mode on 64-bit machines, the various applications that Adobe Reader interacts with also need to be 32-bit binaries running in the emulation mode.

Scripting between an HTML page and Adobe Reader does not work when Adobe Reader is running inside the browser. This issue exists because of the limitation of the browser. Upgrade to a browser version that supports scripting from plug-ins to solve the problem.

Some system fonts do not appear correctly in the Document. Adobe Reader, by default, searches for system fonts in its resource folder and also in the directories listed in the PSRESOURCEPATH environment variable. If the required fonts are not embedded in the document, checking the Document > Use Local Fonts option, enables Adobe Reader to pick up the fonts from the system. Note that the fonts provided by fontconfig (via fc-cache) are cached by default by Adobe Reader. In order to disable caching of fonts specified by fontconfig, the user should set the environment variable ACRO_DISABLE_FONT_CONFIG=1 before launching Adobe Reader.

Stretching or skewing of page text on some systems. This problem can be resolved by going to Edit > Preferences, clicking the Page Display tab, and setting Custom Resolution to the currently displayed System setting.

Menus and tabs appear inverted in Arabic and Hebrew locales. In Arabic or Hebrew locales, the menus, tabs and other UI elements appear inverted, displaying right-to-left instead of left-to-right. This issue is due to the design of the UI toolkit.

The sh shell parser has problems with some characters in some Asian languages that use multibyte characters. If you encounter the error message "invalid multibyte characters" or other problems when running the INSTALL, acroread, or install_browser_plugin scripts, try running the scripts with the ksh or bash shell.

### Security

Unable to open documents secured with Policy Server. If the Policy Server certificate is not installed, a message appears indicating that there was a problem communicating with the service. To solve this problem, install the server certificate using the command line as shown on the console: `acroread -installCertificate` <URL> `` <PORT>

Reader not able to communicate over SSL. Please install Root CA certificates using : `acroread -installCertificate [-PEM | -DER] <Path to certificate file>`

Password-protected PDF files cannot be printed to PostScript® from the command line. Even though password-protected files can be printed from Adobe Reader, you cannot print the files to PostScript from the command line.

libldap could not be loaded. PPKLite plugin requires the installation of the OpenLDAP package and some security features will not work in its absence. If you notice an alert saying that libldap.so was not loaded, you need to install the LDAP libraries (OpenLDAP package). If that doesn't solve the problem, do one of the following:

- On Linux, make a link to the installed libldap.so.X and liblber.so.X in <reader_install_dir> /Reader/intellinux/lib with the names `libldap.so` and `liblber.so` .
- On Solaris 10, make a link to the installed libldap and liblber libraries in <reader_install_dir> /Reader/<platform>/lib with the names `libldap.so` and `liblber.so` .

### Search

The Find command does not locate Unicode characters. Before searching for Unicode characters in a PDF file, add `\u` before the Unicode character in the search dialog box. For example, to search for the Unicode equivalent of the ASCII letter A, type `\u0041` in the dialog box. For some CJK characters, such as Unicode 4e01, you can specify `\u4e01`.

Adobe Reader search is slow and doesn't find files. To create full text search indexes that can be reliably used across platforms, you must use the ISO 9660 file naming conventions for the indexed files (8.3 uppercase, restricted character set). Otherwise, Adobe Reader attempts to guess what the UNIX file names are, which causes delays in searching and may result in files not being found.

If you paste the CJK-A character U+3400, U+3500, U+3600, or U+3700 into the search field and perform a search, the search fails even if the character exists in the PDF document you're searching. Type the character in the search field instead of pasting it.

Search does not complete for socket files. If the specified search path contains a socket file (typical paths are /tmp or $HOME), the search does not complete. Make sure that the specified path contains only regular files and no socket files.

### Printing

PDF files don't print. When you print a PostScript document using the `lp` command, a symbolic link is created from the spool file to the file being printed; the link saves space on the file system, but causes a problem when printing from Adobe Reader. To solve this problem, include the`-c` option (copy) with the `lp` or `lpr` command in the Print dialog box. This forces the pd process to copy the file to the spool area instead of making a symbolic link.

Printing issues with CUPS. On certain platforms like Solaris, CUPS (Common UNIX Printing System) may not be present as default. In that case the user needs to install CUPS on the system and include the "CUPS libraries" in `LD_LIBRARY_PATH`. If, however, CUPS is not present on the system, Adobe Reader would use the default `lp` command for printing. This command can be changed inside the Print Dialog Box.

### Accessibility

Read Out Loud menu options are disabled. Adobe Reader supports gnome-speech-0.3.1 version and later. For earlier versions, the menu options are disabled (grayed out). Check the version of gnome-speech installed on your machine by running the following command: `rpm -qa | grep -i gnome-speech` . To test whether the gnome-speech version is compatible with Adobe Reader, run the command `test-speech` .

Read Out Loud does not work after upgrading gnome-speech. Test using the command `test-speech` . Link to the installed libraries libORBit-2.so.X, libgnomespeech.so.X, libbonobo-activation.so.X, and libbonobo-2.so.X in <reader_install_dir> /Reader/intellinux/lib with the names `libORBit-2.so` , `libgnomespeech.so` , `libbonobo-activation.so` and `libbonobo-2.so` .

Accessibility is not active. Adobe Reader checks the gconf registry to determine whether accessibility support is enabled on a system. If gconftool-2 is not available on a system, accessibility support is disabled. If your system does not have gconftool-2 and you wish to use the accessibility features of Adobe Reader, change the line `ACRO_AT_ACTIVE="false"` to `ACRO_AT_ACTIVE="true"` in the file <reader_install_dir> /bin/acroread, in the block `if [ "$IS_GCONF_TOOL" = "no" ]` near the end of the file.

To enable accessibility, using gconf-editor or gconftool-2, set the key /desktop/gnome/interface/accessibility to true. Then, enable the keyboard selection cursor (F7 toggles the cursor. It can also be enabled by choosing Edit >Preferences, clicking the Accessibility tab and selecting Always Display the Keyboard Selection Cursor. Finally, check the option by choosing Edit > Preferences, clicking the Reading tab and make sure that Enable Document Accessibility is selected.

### Mail Client

Trouble sending mail using Mutt. If a terminal window flashes and disappears when the selected email client is Mutt, add the line `set autoedit=no" to $HOME/.muttrc` to enable sending mail using mutt.

Evolution crashes when sending mail. This issue happens with earlier versions of Evolution. If Evolution crashes on sending mail (when Evolution is the selected email client), try keeping Evolution running in the background. If it still crashes, upgrade to Evolution 2.0 or later. You might need to keep it running in the background.

### 3D

Adobe Reader crashes on opening/closing multiple files with 3D contents. This is a known problem with the DRI common code, https://bugs.freedesktop.org/show_bug.cgi?id=2733. It has been fixed in the newer versions of the library.

On opening a PDF with embedded 3D content, Adobe Reader does not display the 3D textures properly and displays the error message "[driAllocateTexture:577] unable to allocate texture" on the console. The workaround for this is to add the line "Videoram 16386" in the "Device" section of the /etc/X11/xorg.conf file, hence increasing the memory reserved for texture handling.

## Keyboard shortcuts

Ctrl+Insert and Shift+Insert keyboard accelerators can be used as alternatives to Edit > Copy and Edit > Paste operations in the Reader, especially in dialogs.

Reader and Acrobat have the same keyboard shortcuts. To view the full list, see Keyboard shortcuts in Acrobat Help.

## Legal notices

© 2008 Adobe Systems Incorporated. All rights reserved.

Adobe, Acrobat, Reader, and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries. Red Hat is a trademark or registered trademark of Red Hat, Inc in the United States and other countries. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Linux is a registered trademark of Linus Torvalds. Novell is a registered trademark of Novell, Inc. Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. All other trademarks are the property of their respective owners.

Last updated May 2009.