Open Scribus Documents from the Command Line

Scribus is a GUI desktop publisher, but the command line still decides which file opens and which language it opens in. The examples target the installed Ubuntu package Scribus 1.6.1-0ubuntu7. The local manpage is dated 2010-24-06, so treat its option summary as the contract for the commands shown here, and fall back on Scribus's own built-in help if your installation behaves differently.

Allow about fifteen minutes. You need Scribus installed, a graphical Linux session, and a readable Scribus document if you want to test opening a file. Run these as your own user. Do not use sudo: Scribus stores preferences in your home directory, and launching the GUI as root can create root-owned files your normal account cannot later update.

1. Confirm the package and the display

Check which executable the shell will start, and record the package version:

$ command -v scribus
/usr/bin/scribus
$ dpkg-query -W -f='${Package} ${Version}\n' scribus-data
scribus-data 1.6.1-0ubuntu7

The package query is read-only. Launching Scribus also needs a graphical display to talk to: a Qt error about xcb, or a failure to connect to a display, means you are in a headless shell or an incomplete graphical session. Fix that session first. Do not mistake a display error for a missing document, and do not try to fix it by changing file ownership.

2. Ask Scribus for help or its version

Run these from a terminal inside the graphical session:

$ scribus --version
$ scribus --help

--version prints the version and exits. --help prints a brief usage summary and exits. Exact wording varies by release. The installed manpage gives the general command shape as scribus [-h|--help] [-v|--version] [-l|--lang language] [-la|--langs-available] [-f|--file|--] [filename].

If either command fails before printing anything, compare the error with the display check in step 1. A GUI application can fail before it even processes a valid option, and the package query above remains a useful version check when the graphical session is unavailable.

3. Open a document by path

Pass a Scribus document as an ordinary, quoted argument. An absolute path removes any ambiguity about the current directory:

$ scribus /home/your-user/Documents/brochure.sla

The manpage also documents the explicit --file form:

$ scribus --file /home/your-user/Documents/brochure.sla

• Use the plain form for a normal filename.
• Use -- when the filename itself starts with a hyphen, so Scribus does not read it as an option: $ scribus -- -cover.sla
• Quote paths containing spaces.

$ scribus -- -cover.sla

$ scribus --file '/home/your-user/Client work/brochure.sla'

Replace the example paths with files you have actually checked. A failed open is often a spelling, permission or format problem, so inspect the path without changing it:

$ test -r '/home/your-user/Client work/brochure.sla' && echo readable
readable

A successful test only proves your account can read the file. It does not prove the document is intact. Keep the original file until it has opened and you have checked its pages, linked assets and fonts.

4. Pick the interface language for one launch

List the interface translations available in this installation:

$ scribus --langs-available

Then select one with its short POSIX-style code:

$ scribus --lang en_GB /home/your-user/Documents/brochure.sla

The manpage lists codes such as en, en_GB, en_US and de_DE, but the exact available list belongs to your installation: copy a code from --langs-available rather than guessing. This changes the interface for that one launch; it does not translate the document's text.

Scribus checks LC_ALL, then LC_MESSAGES, then LANG, and falls back to whatever locale Qt supplies if none is set. If a shell wrapper or desktop launcher sets one of these, that can explain why two launches show different interfaces.

5. Diagnose fonts and colour profiles

Missing glyphs or wrong-looking colour? Ask Scribus to print its diagnostic listings on startup:

$ scribus --font-info
$ scribus --profile-info

--font-info shows the font file listing as Scribus starts. --profile-info shows the colour profiles it can use. Both are inspection commands, not fixes: save the terminal output if you are comparing two machines or reporting a missing resource.

Scribus reads Fontconfig paths such as /etc/fonts, $HOME/.fonts and $HOME/.fonts.conf, and it can also have its own internal font path set in Preferences. Ghostscript-related operations search PATH, GS_FONTPATH and GS_LIB; if more than one gs is installed, set an absolute Ghostscript path in Scribus Preferences rather than trusting whichever one happens to sit first on PATH.

6. Control startup noise and preferences carefully

--no-splash suppresses the splash screen for one startup:

$ scribus --no-splash /home/your-user/Documents/brochure.sla

--prefs points Scribus at a preferences file for the launch. Use a copy when testing a suspected preference problem, never your only working file:

$ cp --preserve=mode,timestamps "$HOME/.config/scribus/prefs150.xml" /tmp/scribus-prefs-test.xml
$ scribus --prefs /tmp/scribus-prefs-test.xml /home/your-user/Documents/brochure.sla

That copy is disposable test state: remove it once you no longer need it as evidence, and do not hand-edit the XML unless you have a specific recovery reason. Scribus preferences normally live under $HOME/.config/scribus/; the manpage names scribus150.rc and prefs150.xml for the 1.5.x family.

7. Use scripting and update checks only deliberately

--python-script, followed by a script and its own arguments, must be the last Scribus option on the line:

$ scribus --python-script /home/your-user/bin/check-layout.py -- /home/your-user/Documents/brochure.sla

--upgradecheck downloads a file from the Scribus server describing available versions. That is a network operation, not a local version check: use it only when that outbound request is acceptable on your machine and network. It does not upgrade Scribus, and it does not replace your distribution's package update process.

Common traps

Most of the options above affect a single launch. Opening a document does not save it, and closing Scribus without saving leaves the source file untouched. The exceptions worth treating carefully are --never-splash, preference selection and any script that writes state.

If a launch behaves unexpectedly, get back to a known state: close Scribus, stop using the test preferences file, and start the plain command with no optional flags. If a document changed through the GUI or a script, use Scribus's own undo, or reopen the untouched backup. Do not overwrite the only copy with shell redirection or an unreviewed automation script.