How To Install OpenOffice on Manjaro

Apache OpenOffice remains a popular office productivity suite for Linux users who need a reliable, free alternative to Microsoft Office. While Manjaro Linux officially supports LibreOffice as its default office application, many users still prefer OpenOffice for compatibility reasons, specific features, or personal preference. Installing OpenOffice on Manjaro requires working with the Arch User Repository (AUR) or alternative package formats since it’s not available in the official repositories. This comprehensive guide walks through four proven installation methods, post-installation configuration, and troubleshooting to help you get OpenOffice running smoothly on your Manjaro system.

Understanding Apache OpenOffice and Manjaro Compatibility

Apache OpenOffice is a complete office productivity suite featuring six main applications: Writer for word processing, Calc for spreadsheets, Impress for presentations, Draw for graphics and diagrams, Base for databases, and Math for mathematical formulas. The suite supports multiple file formats including the OpenDocument Format (ODF) and Microsoft Office formats.

Manjaro Linux is built on Arch Linux, inheriting its rolling-release model and access to the Arch User Repository. The AUR contains thousands of community-maintained packages not available in official repositories. Although Manjaro dropped official OpenOffice support years ago in favor of LibreOffice, users can still install it through AUR packages or universal package formats.

The key difference between the two suites lies in their development pace and community backing. LibreOffice emerged as a fork of OpenOffice with more active development and frequent updates. However, OpenOffice maintains a stable codebase that some users find more reliable for specific workflows or legacy document compatibility.

System Requirements and Prerequisites

Minimum Hardware Requirements

Before installing OpenOffice on Manjaro, verify that your system meets the minimum specifications. OpenOffice requires Linux kernel 2.6 or higher and glibc2 version 2.5 or higher. Modern Manjaro installations exceed these requirements by default.

Memory requirements are modest. OpenOffice needs at least 256MB RAM, though 512MB or more is recommended for smooth performance. Disk space requirements include approximately 400MB for the installation itself, plus additional space for user documents and temporary files.

Display requirements specify an X-Server with 1024×768 resolution supporting at least 256 colors. Contemporary systems easily meet these specifications. For full functionality, particularly database features and macro support, OpenOffice benefits from Java Runtime Environment installation. While optional, Java enables Base database management, certain wizards, and extension capabilities.

Software Prerequisites

Installing OpenOffice from the AUR requires essential build tools. The base-devel package group provides compilation tools, libraries, and utilities needed to build packages from source. Git version control system is necessary for cloning AUR repositories.

Install these prerequisites with a single command:

sudo pacman -S --needed base-devel git

The --needed flag skips packages already installed on your system. This command installs make, gcc, binutils, and other compilation utilities required for AUR package building.

For full OpenOffice functionality, install Java Runtime Environment:

sudo pacman -S jre-openjdk

Alternatively, install the full Java Development Kit if you plan to develop Java applications:

sudo pacman -S jdk-openjdk

Verify Java installation by checking the version:

java -version

Method 1: Installing OpenOffice Using Pamac (GUI Method)

Enabling AUR Support in Pamac

Pamac serves as Manjaro’s default graphical package manager, offering an intuitive interface for software installation and system updates. By default, Pamac only searches official Manjaro repositories, so AUR support must be manually enabled.

Launch Pamac from your application menu or system tray. Click the three horizontal lines (hamburger menu) in the upper right corner to access settings. Select “Preferences” from the dropdown menu. The system will prompt for your administrator password – enter it to proceed.

Navigate to the “AUR” tab in the preferences window. Check the box labeled “Enable AUR support” to activate access to community packages. This modification allows Pamac to search, display, and install packages from the Arch User Repository alongside official packages.

Optional settings include enabling “Check for updates from AUR” to receive notifications when AUR packages have new versions available. You can also enable “Check for development package updates” if you install git versions of software. Click “Apply” or “OK” to save changes and close preferences.

Installing OpenOffice Through Pamac

With AUR support enabled, installing OpenOffice becomes straightforward. Open Pamac and type “openoffice” into the search bar at the top of the window. The results display various OpenOffice-related packages, with AUR packages clearly marked with an “AUR” label.

Locate “openoffice-bin” in the search results. The “-bin” suffix indicates this package contains pre-compiled binaries rather than building from source, significantly reducing installation time. Click on the package name to view detailed information including description, version number, dependencies, optional dependencies, and build files.

Review the dependency list to understand what additional packages will be installed. OpenOffice requires several libraries for functionality, which Pamac handles automatically. Check the box next to openoffice-bin or click the “Install” button.

Pamac displays a summary showing all packages to be installed, including dependencies. Review this list and click “Apply” to begin the installation process. Pamac automatically downloads the PKGBUILD file, retrieves source packages, resolves dependencies, compiles the package, and installs everything in the correct order.

The build process takes several minutes depending on system performance and internet connection speed. A terminal window displays compilation output, allowing you to monitor progress. Once complete, Pamac displays a success message, and OpenOffice appears in your application menu under the Office category.

Method 2: Installing OpenOffice Using Yay AUR Helper

What is Yay and Why Use It

Yay (Yet Another Yogurt) is a command-line AUR helper written in Go that simplifies AUR package management. Unlike manual AUR installation, Yay automates the entire process from searching to installation.

The tool offers several advantages. Yay provides unified search across official repositories and AUR simultaneously. It handles dependency resolution automatically, including AUR dependencies that depend on other AUR packages. System updates can include AUR packages with a single command. The interface mirrors pacman syntax, making it familiar to Arch and Manjaro users.

Yay enjoys widespread adoption in the Arch community with extensive documentation and active maintenance. It strikes a balance between automation and user control, prompting for confirmation at critical steps while handling tedious tasks automatically.

Installing Yay

Before installing Yay, ensure build tools are present. Run the prerequisite installation command:

sudo pacman -S --needed base-devel git

Clone the Yay repository from AUR:

git clone https://aur.archlinux.org/yay.git

This command creates a “yay” directory containing the PKGBUILD and installation files. Navigate into this directory:

cd yay

Build and install Yay using makepkg:

makepkg -si

The -s flag installs dependencies automatically, and -i installs the package after successful build. Makepkg compiles Yay from source, a process taking just a minute or two. When prompted, confirm the installation by typing “Y” and pressing Enter.

After installation completes, verify Yay is working:

yay --version

This displays the installed Yay version number. You can now remove the cloned directory since Yay is installed system-wide:

cd ..
rm -rf yay

Yay can update itself using its own command: yay -S yay.

Installing OpenOffice with Yay

Installing OpenOffice through Yay requires a single command. Open a terminal and execute:

yay -S openoffice-bin

Yay searches both official repositories and AUR for the package. When multiple results appear, select the appropriate package number (typically 1 for openoffice-bin). Yay displays package information including version, description, dependencies, and architecture.

The tool presents the PKGBUILD contents for security review. While optional, examining PKGBUILDs helps identify malicious code or unexpected behavior. Press ‘q’ to exit the viewer.

Yay asks whether to proceed with installation. Press Enter or type ‘Y’ to continue. The tool downloads source files and dependencies automatically. Building commences, with compilation output displayed in real-time. The entire process is automated – Yay handles everything from downloading to installing.

For searching OpenOffice-related packages without installing, use:

yay openoffice

This displays all available OpenOffice packages, extensions, and related software from official repositories and AUR.

Method 3: Installing OpenOffice Using Paru AUR Helper

Understanding Paru AUR Helper

Paru represents the next generation of AUR helpers, written in Rust by a Yay co-developer. While functionally similar to Yay, Paru introduces additional features focused on security and best practices.

Key distinctions include mandatory PKGBUILD review before installation, enhancing security by forcing users to examine build scripts. Paru displays AUR comments during installation, providing community insights about packages. The tool prints Arch Linux news on system upgrades, keeping users informed about important changes.

Advanced features include chroot support for isolated building, local repository creation, and syntax highlighting with bat for improved readability. Paru emphasizes following Arch best practices, making it ideal for security-conscious users.

Both Yay and Paru can coexist on the same system without conflicts. Users can choose based on preference or use both for different purposes.

Installing Paru

Paru installation follows the standard AUR package build process. First, ensure prerequisites are installed:

sudo pacman -S --needed base-devel git

Clone the Paru repository from AUR:

git clone https://aur.archlinux.org/paru.git

Change to the paru directory:

cd paru

Build and install with makepkg:

makepkg -si

The build process compiles Paru’s Rust code, which may take a few minutes. Confirm installation when prompted.

Alternatively, if Yay is already installed on your system, install Paru directly:

yay -S paru

This method is faster since Yay handles the entire process. Verify Paru installation:

paru --version

Installing OpenOffice with Paru

Launch OpenOffice installation with Paru:

paru -S openoffice-bin

Paru displays package information and prompts for PKGBUILD review. This mandatory step ensures security by allowing inspection of build scripts before execution. The PKGBUILD appears in your default pager (usually less).

Review the build script carefully, checking for suspicious commands or unexpected behavior. Press ‘q’ to exit the pager once satisfied. Paru asks whether to proceed with installation – confirm by typing ‘Y’ or pressing Enter.

Additional information may appear, including AUR comments from other users discussing the package. This feedback provides valuable insights about installation issues or package quality. Paru automatically downloads sources, compiles the package, and installs OpenOffice along with required dependencies.

During the build process, pressing ‘Q’ exits any pager screens that appear. The installation completes with OpenOffice ready to use from your application menu.

Search for OpenOffice-related packages without installing:

paru openoffice

This command displays all matching packages from official repositories and AUR.

Method 4: Installing OpenOffice via Snap

About Snap Packages

Snap represents a universal Linux package format developed by Canonical for Ubuntu but available across distributions. Snaps bundle applications with all dependencies in a single package, ensuring consistency across different Linux systems.

Benefits include sandboxed application execution for enhanced security, automatic background updates without user intervention, and distribution-agnostic installation. The self-contained nature means Snaps are larger than traditional packages but eliminate dependency conflicts.

OpenOffice maintains an official presence in the Snap Store, providing a convenient installation option for users preferring universal packages. Snap packages update independently of system packages, ensuring the latest OpenOffice version is always available.

Installing Snapd on Manjaro

Manjaro doesn’t include snapd by default, requiring manual installation. Install the snapd package using Pamac GUI by searching for “snapd” in Add/Remove Software, or via command line:

sudo pacman -S snapd

After installation, enable the snapd systemd service to start automatically on boot:

sudo systemctl enable --now snapd.socket

The --now flag starts the service immediately while also enabling it for future boots. Create a symbolic link for classic snap support:

sudo ln -s /var/lib/snapd/snap /snap

This link enables compatibility with snaps requiring classic confinement. Log out and log back in, or restart your system to ensure all snap paths are properly initialized.

Installing OpenOffice Snap

With snapd configured, install OpenOffice with a single command:

sudo snap install openoffice

Snap downloads the OpenOffice package and all bundled dependencies. Installation progress appears in the terminal, showing download and installation status. The process completes in a few minutes depending on internet speed.

Once installed, OpenOffice appears in your application menu under the Office category. Launch Writer, Calc, or Impress directly from the launcher.

Verify OpenOffice installation and check for updates:

snap list

This command displays all installed snap packages including version numbers. OpenOffice snaps update automatically, but manual updates are possible:

sudo snap refresh openoffice

Post-Installation Configuration

Launching OpenOffice

OpenOffice integrates into your desktop environment after installation. Find it in the application menu under “Office” or search for “OpenOffice” in your application launcher. Individual components appear as separate entries: OpenOffice Writer, OpenOffice Calc, OpenOffice Impress, OpenOffice Draw, OpenOffice Base, and OpenOffice Math.

Launch from the terminal using the soffice command. General OpenOffice launcher:

soffice

Launch specific components:

soffice --writer  # Word processor
soffice --calc    # Spreadsheet
soffice --impress # Presentations
soffice --draw    # Graphics
soffice --base    # Database

The first launch takes slightly longer as OpenOffice initializes user profiles and configuration files in ~/.config/.openoffice.org/. Subsequent launches are faster.

Installing Java for Full Functionality

Java Runtime Environment is essential for specific OpenOffice features. Base database application requires Java for full functionality, as do certain macro types, database connectivity wizards, and some extensions.

Install Java using pacman:

sudo pacman -S jre-openjdk

For development capabilities, install the full JDK:

sudo pacman -S jdk-openjdk

Verify installation:

java -version

Configure Java in OpenOffice by opening Tools > Options from the menu bar. Navigate to OpenOffice > Java in the left sidebar. Ensure “Use a Java runtime environment” is checked. Select your installed JRE from the list – typically showing “Oracle Corporation” or “OpenJDK”. Click OK to save settings.

Note that disabling Java when not needed reduces OpenOffice startup time and memory usage. Enable it only when using Base, specific macros, or Java-dependent extensions.

Installing Language Packs and Spell Checkers

OpenOffice relies on system-wide dictionaries for spell checking, hyphenation, and thesaurus functionality. Install Hunspell dictionaries for spell checking:

sudo pacman -S hunspell-en_us

Replace “en_us” with your language code (hunspell-es for Spanish, hunspell-de for German, etc.). Install hyphenation rules for automatic word breaking:

sudo pacman -S hyphen hyphen-en

Install thesaurus for synonym suggestions:

sudo pacman -S libmythes mythes-en

Configure additional dictionaries through Extension Manager. Open Tools > Extension Manager from the menu bar. Click “Add” and navigate to /usr/lib/openoffice/share/extension/install/. Select dictionary files with .oxt extension and click “Open” to install. Restart OpenOffice after adding extensions.

Test spell checking in Writer by typing misspelled words – they should appear with red underlines if configured correctly.

Essential OpenOffice Configuration Settings

Optimizing Performance Settings

OpenOffice performance can be tuned for better responsiveness. Navigate to Tools > Options > Memory from the menu bar. Adjust the following settings for optimal performance:

Reduce Undo steps from the default 100 to 40-50, decreasing memory usage while maintaining reasonable undo history. Increase Graphics cache from 20MB to 128MB for smoother handling of embedded images and graphics. Set Memory per object to 20MB (default 5MB) to prevent frequent cache clearing when working with large images.

OpenOffice Quickstarter can reduce startup time by keeping core libraries loaded in memory. Enable it in Tools > Options > Memory > OpenOffice Quickstarter. This increases RAM usage but significantly speeds up application launching.

If Java isn’t needed for your workflow, disable it for faster loading. Navigate to Tools > Options > Java and uncheck “Use a Java runtime environment”. This eliminates Java VM initialization during startup.

The performance trade-offs vary by system. Test different configurations to find optimal settings for your hardware and usage patterns.

Font Configuration

Proper font configuration ensures document compatibility and appearance consistency. Install Microsoft TrueType fonts for better compatibility with Office documents:

yay -S ttf-ms-fonts

Configure font substitution by opening Tools > Options > OpenOffice > Fonts. Enable “Apply Replacement Table” checkbox. Add fonts requiring substitution – for example, add “Andale Sans UI” and replace it with “Liberation Sans” or another system font. Check “Always” and “Screen only” options to apply substitution in all contexts and only for screen display.

Adjust antialiasing for better font rendering. Navigate to Tools > Options > OpenOffice > View and configure “Screen font antialiasing”. Set the minimum font size for antialiasing – typically 8-10 points works well. Uncheck “Use system font for user interface” if you prefer OpenOffice’s default interface fonts over system fonts.

For advanced font management, use the spadmin utility from the terminal:

spadmin

This tool allows adding TrueType fonts system-wide, though modern systems typically handle this automatically.

Installing Extensions and Additional Features

Using Extension Manager

OpenOffice’s functionality expands through extensions that add new capabilities. Access Extension Manager through Tools > Extension Manager to view pre-installed extensions.

Default extensions include PDF Import for importing PDF files in Draw and Impress, Presentation Minimizer for reducing presentation file sizes, Wiki Publisher for creating MediaWiki articles, and Presenter Screen for dual-display presentation support.

Install new extensions by downloading .oxt files from the official OpenOffice extensions website. In Extension Manager, click “Add” button and navigate to the downloaded .oxt file. Select the file and click “Open” to begin installation. OpenOffice prompts for restart after extension installation – save work and restart to activate new extensions.

Command-line extension management is also available. Install extensions for current user:

/usr/lib/openoffice/program/unopkg add extension.oxt

Install system-wide for all users (requires root):

sudo /usr/lib/openoffice/program/unopkg add --shared extension.oxt

Setting Up Macros

Macro support enables automation and custom functionality in OpenOffice. The default macro directory on Arch-based systems like Manjaro is ~/.config/.openoffice.org/3/user/Scripts/, differing from standard OpenOffice installations.

Change macro storage location by opening Tools > Options > OpenOffice > Paths. Select “AutoText” or “User” in the path list and click “Edit” to modify storage location. This is particularly useful for sharing macro directories between OpenOffice and LibreOffice installations.

Remember that Java is required for many macro types to function properly. Enable Java as described in the Java configuration section. Note that macros may not work identically between OpenOffice and LibreOffice due to API differences, requiring modifications when migrating between suites.

Theming and Desktop Integration

Configuring Visual Theme

OpenOffice supports multiple UI toolkits including GTK and Qt for desktop environment integration. Set desktop integration using the OOO_FORCE_DESKTOP environment variable with values ‘gnome’ for GTK-based environments or ‘kde4’ for Qt-based environments.

Configure globally by editing /etc/profile.d/openoffice.sh or adding to your ~/.bashrc:

export OOO_FORCE_DESKTOP=gnome

For KDE/Qt environments using GTK themes, use gtk-chtheme or similar tools to select appropriate themes. Configure appearance through Tools > Options > OpenOffice > View, setting scale to 100% and adjusting antialiasing preferences.

Dark theme users may encounter readability issues. Disable “Automatically detect high-contrast mode” in Tools > Options > Accessibility to prevent automatic theme adjustments. Manually configure colors in Tools > Options > Appearance, selecting appropriate colors for document backgrounds, text, and UI elements.

Desktop Icons and File Associations

File associations connect document types with OpenOffice components. Right-click .odt, .ods, or .odp files in your file manager. Select “Open With” and choose the appropriate OpenOffice component (Writer for .odt, Calc for .ods, Impress for .odp). Check “Set as default” to make OpenOffice the default handler for these file types.

Desktop integration packages handle MIME types and icon placement automatically during installation. Verify integration by checking that OpenOffice icons appear properly in file managers and that double-clicking documents opens them in OpenOffice.

Create custom application shortcuts if needed through your desktop environment’s menu editor, typically accessible by right-clicking the application menu.

Updating and Managing OpenOffice

Updating AUR-Installed OpenOffice

AUR packages don’t update through standard Manjaro system updates. Check for updates separately using your preferred installation method.

Using Pamac, click the “Updates” tab to view available updates for both official and AUR packages. If openoffice-bin appears in the list, select it and click “Apply” to update.

Using Yay, update all system and AUR packages simultaneously:

yay -Syu

Yay checks both official repositories and AUR for updates, providing a unified upgrade experience.

Using Paru, run the update command:

paru -Syu

Or simply:

paru

Paru displays Arch Linux news during upgrades, keeping you informed about important system changes.

Manually check for new OpenOffice versions by visiting the AUR package page at https://aur.archlinux.org/packages/openoffice-bin. The page shows the current version and update history.

Updating Snap-Installed OpenOffice

Snap packages update automatically by default, checking for updates multiple times daily. Manual updates are still possible when desired.

Refresh OpenOffice to the latest version:

sudo snap refresh openoffice

Check for pending updates without installing:

snap refresh --list

View installed version and available updates:

snap info openoffice

Configure automatic update behavior through snap settings if you prefer manual update control. Snap updates are independent of system updates, ensuring OpenOffice stays current even on stable system configurations.

Troubleshooting Common Issues

OpenOffice Won’t Launch or Crashes

Launch failures often stem from configuration file corruption or permission issues. Start by disabling Java if it’s causing initialization problems – edit ~/.config/.openoffice.org/3/user/registrymodifications.xcu and locate Java settings, or disable through GUI if OpenOffice launches intermittently.

Reset user profile by renaming the configuration directory:

mv ~/.config/.openoffice.org/ ~/.config/.openoffice.org.backup

This forces OpenOffice to create fresh configuration on next launch. If the issue resolves, you can selectively copy settings from the backup.

Fix Java framework errors with correct ownership:

sudo chown -vR $USER:$USER ~/.config/

Replace $USER with your username if the variable doesn’t work. Verify file permissions in the installation directory are set correctly, particularly for /usr/lib/openoffice/.

Check system logs for specific error messages:

journalctl -xe

Search the output for OpenOffice or soffice entries that might indicate the problem cause. If all else fails, reinstall the package using your original installation method.

Font Rendering Problems

Poor font rendering affects document appearance and readability. Add Xft configuration to improve font rendering. Edit or create ~/.Xresources:

nano ~/.Xresources

Add this line:

Xft.lcdfilter: lcddefault

Merge the changes:

xrdb -merge ~/.Xresources

Configure font substitution in Tools > Options > OpenOffice > Fonts as described in the font configuration section. Install additional TrueType fonts to expand available typefaces:

sudo pacman -S ttf-liberation ttf-dejavu

Adjust antialiasing settings in Tools > Options > OpenOffice > View for better screen rendering. Use the spadmin utility for comprehensive font management:

spadmin

This tool provides detailed control over font paths, substitution, and rendering options.

Dark Theme and High Contrast Issues

Dark themes can cause readability problems in OpenOffice due to automatic high-contrast detection. Disable this feature by opening Tools > Options > LibreOffice/OpenOffice > Accessibility and unchecking “Automatically detect high-contrast mode of operating system”.

Manually configure colors in Tools > Options > Appearance. Adjust document background, application background, text color, and other elements to suit your preferred color scheme. Save custom color schemes using the “Save” button for easy restoration.

Configure GTK theme separately from desktop environment theme if using KDE or other non-GTK environments. Install gtk-chtheme:

sudo pacman -S gtk-chtheme

Run gtk-chtheme to select a lighter theme specifically for GTK applications:

gtk-chtheme

Set the OOO_FORCE_DESKTOP variable appropriately for your environment as described in the theming section. Choose lighter GTK themes if dark themes cause persistent readability issues, sacrificing theme consistency for functionality.

Uninstalling OpenOffice from Manjaro

Removing AUR-Installed OpenOffice

Uninstallation varies by original installation method. Using Pamac, open the package manager and search for “openoffice”. Click the “Remove” button next to openoffice-bin and confirm removal. Optionally remove unused dependencies by checking “Remove unrequired dependencies” in the removal dialog.

Using Yay, remove OpenOffice and dependencies:

yay -Rns openoffice-bin

The -R flag removes the package, -n removes configuration files, and -s removes dependencies no longer needed by other packages.

Using Paru, the command is identical:

paru -Rns openoffice-bin

Manually remove user configuration if desired:

rm -rf ~/.config/.openoffice.org/

This deletes personal settings, templates, and customizations. Backup this directory first if you might reinstall OpenOffice later.

Removing Snap-Installed OpenOffice

Snap package removal is straightforward. Remove OpenOffice with:

sudo snap remove openoffice

This command uninstalls OpenOffice and removes associated data. If snapd is no longer needed after removing all snap packages, remove it completely:

sudo pacman -Rns snapd

Clean up residual snap directories:

sudo rm -rf /var/lib/snapd

Note that Snap packages don’t leave system-wide dependencies since everything is bundled within the snap.

Congratulations! You have successfully installed OpenOffice. Thanks for using this tutorial for installing the Apache OpenOffice on your Manjaro Linux system. For additional help or useful information, we recommend you check the official OpenOffice website.