CLI Diagnostics Troubleshooting

Kalium 1.1.0 Beta

The majority of the CLI is also available in the GUI.

Quick Start — AppImage

Kalium is distributed as an AppImage. When running it directly, use the full path to the AppImage, followed by the command and any options.

Command syntax

/path/to/Kalium-1.1.0-x86_64.AppImage COMMAND [OPTIONS]

For example:

set-vfs-memory is a command
-p /path/to/mo2 is an option passed to that command
--version is a global option

Check the Kalium version

/path/to/Kalium-1.1.0-x86_64.AppImage --version

Output:

Kalium 1.1.0

Display CLI help

/path/to/Kalium-1.1.0-x86_64.AppImage -h

Important: Opening a terminal in the directory containing the AppImage does not make kalium available as a command. Unless you have created your own symlink or added Kalium to $PATH, use the complete AppImage path as shown above.

Full CLI Help (`-h`)

/path/to/Kalium-1.1.0-x86_64.AppImage -h

usage: kalium [-h] [--version]
              {setup-mo2,list-protons,list-mo2,status,enable-nxm,check-steam,diagnose,backpatch-skyrim,repair-shortcut,install-collections,install-usvfs,fix-paths,install-loot,set-theme,set-vfs-memory,install-nexus-plugin}
              ...

Kalium — Linux Modding Helper (MO2 via Steam/Proton). Author: Bobby Comet.

positional arguments:
  {setup-mo2,list-protons,list-mo2,status,enable-nxm,check-steam,diagnose,backpatch-skyrim,repair-shortcut,install-collections,install-usvfs,fix-paths,install-loot,set-theme,set-vfs-memory,install-nexus-plugin}

    setup-mo2             Set up existing MO2 with Steam integration
    list-protons           List available Proton 10+ versions
    list-mo2               List managed MO2 instances
    status                 Kalium/MO2 environment status (support-friendly overview)
    enable-nxm             Register NXM handler and activate last MO2 instance
    check-steam            Diagnose Steam install, libraries, mounts, shortcuts
    diagnose               Full environment health report (also writes a file for GitHub issues)
    backpatch-skyrim       Backpatch a supported game via Steam depots
                           (Skyrim SE, Fallout 4, Starfield, Cyberpunk, Witcher 3)
    repair-shortcut        Re-add an MO2 folder as a non-Steam game
                           (writes shortcuts.vdf)
    install-collections    Install MO2 Collections plugin (Nexus #1541)
    install-usvfs          Update USVFS binaries in an MO2 folder to 0.5.7.2
                           (fixes virtual-folder duplication / slow boots on Wine 10.20+)
    fix-paths              Normalize backslash paths in MO2's customExecutables
                           (SKSE, LOOT, xEdit, etc.) to forward slashes
    install-loot           Download portable LOOT, write run_loot.bat
                           (--game= for this instance), and register it in ModOrganizer.ini
    set-theme              Set MO2's UI style to a bundled .qss theme
                           (default: dracula.qss)
    set-vfs-memory         Set [vfs] max_memory in ModOrganizer.ini
                           (default: 2147483648 = 2 GB)
    install-nexus-plugin   Install an MO2 plugin from a Nexus Mods page URL
                           into <mo2>/plugins/

options:
  -h, --help              show this help message and exit
  --version               show program's version number and exit

CLI Command Reference

All examples below assume the AppImage is located at:

/path/to/Kalium-1.1.0-x86_64.AppImage

Replace this with the actual location of your AppImage.

Command	Purpose	Example
`setup-mo2`	Install or set up an existing MO2 installation	`/path/to/Kalium-1.1.0-x86_64.AppImage setup-mo2 -p /path/to/mo2`
`list-protons`	List available Proton 10+ versions	`/path/to/Kalium-1.1.0-x86_64.AppImage list-protons`
`list-mo2`	List managed MO2 instances	`/path/to/Kalium-1.1.0-x86_64.AppImage list-mo2 --json`
`status`	Display a quick environment overview	`/path/to/Kalium-1.1.0-x86_64.AppImage status`
`enable-nxm`	Register the NXM handler and activate the last MO2 instance	`/path/to/Kalium-1.1.0-x86_64.AppImage enable-nxm`
`check-steam`	Diagnose Steam installation, libraries, mounts, AppIDs, and shortcuts	`/path/to/Kalium-1.1.0-x86_64.AppImage check-steam --json`
`diagnose`	Run a complete Kalium/MO2 environment health report	`/path/to/Kalium-1.1.0-x86_64.AppImage diagnose`
`backpatch-skyrim`	Backpatch a supported game through Steam depots	`/path/to/Kalium-1.1.0-x86_64.AppImage backpatch-skyrim -p /game/folder --target 1.6.1170`
`repair-shortcut`	Re-add an MO2 installation as a Steam non-Steam game	`/path/to/Kalium-1.1.0-x86_64.AppImage repair-shortcut -p /path/to/mo2`
`install-collections`	Install the MO2 Collections plugin	`/path/to/Kalium-1.1.0-x86_64.AppImage install-collections -p /path/to/mo2`
`install-usvfs`	Update USVFS to version 0.5.7.2	`/path/to/Kalium-1.1.0-x86_64.AppImage install-usvfs -p /path/to/mo2`
`fix-paths`	Normalize backslash paths in MO2 `customExecutables`	`/path/to/Kalium-1.1.0-x86_64.AppImage fix-paths -p /path/to/mo2`
`install-loot`	Install portable LOOT and register it with MO2	`/path/to/Kalium-1.1.0-x86_64.AppImage install-loot -p /path/to/mo2`
`set-theme`	Set the MO2 UI theme	`/path/to/Kalium-1.1.0-x86_64.AppImage set-theme -p /path/to/mo2`
`set-vfs-memory`	Set the MO2 VFS `max_memory` value	`/path/to/Kalium-1.1.0-x86_64.AppImage set-vfs-memory -p /path/to/mo2`
`install-nexus-plugin`	Install an MO2 plugin from a Nexus Mods URL	`/path/to/Kalium-1.1.0-x86_64.AppImage install-nexus-plugin -p /path/to/mo2 -u https://...`

Diagnostics

Kalium provides two levels of diagnostics.

`status`

Provides a quick, support-friendly overview of the current Kalium/MO2 environment.

/path/to/Kalium-1.1.0-x86_64.AppImage status

Use this for a quick check of the environment.

`check-steam`

Checks Steam-specific configuration and infrastructure.

/path/to/Kalium-1.1.0-x86_64.AppImage check-steam

For machine-readable output:

/path/to/Kalium-1.1.0-x86_64.AppImage check-steam --json

Checks include:

Steam installation
Steam libraries
AppID ownership
Game library locations
Compatibility mounts
MO2 non-Steam shortcuts
Relevant Steam configuration

This is primarily a Steam infrastructure diagnostic.

`diagnose`

Runs a complete Kalium/MO2 environment health check.

/path/to/Kalium-1.1.0-x86_64.AppImage diagnose

The diagnostic system checks:

Kalium version
Linux distribution
Kernel version
Python version
Desktop environment
Session type
GPU
Steam installation
All detected Steam libraries
Skyrim SE AppID 489830
Game Proton prefix
All managed MO2 instances
Available Proton 10+ versions
STEAM_COMPAT_MOUNTS
NXM handler
Portable LOOT
System LOOT
Steam process status
MO2 configuration files
USVFS version

Example results

Environment appears healthy.

or:

Environment has X failures and Y warnings.

Warnings and failures are marked for review, including issues such as:

Old USVFS versions
Missing LOOT
Missing ModOrganizer.ini
Missing or invalid Proton configuration
Missing Steam libraries
NXM configuration problems

The diagnostic report is also saved as:

kalium_diagnose_YYYYMMDD_HHMMSS.txt

This file can be attached to a GitHub issue when requesting support.

Troubleshooting

1. `bash: /path/to/kalium: Is a directory`

This normally happens when the AppImage's directory is used as though it were the executable.

For example, opening a terminal in the AppImage directory does not make the directory itself a command.

You may also see:

Command 'kalium' not found, did you mean:
  command 'kalzium' from snap kalzium (...)
  command 'kalzium' from deb kalzium (...)

Fix

Run the AppImage itself and provide the command:

/path/to/Kalium-1.1.0-x86_64.AppImage COMMAND

For example:

/path/to/Kalium-1.1.0-x86_64.AppImage status

2. `Permission denied` or `Cannot execute binary file`

The AppImage may not have its executable permission set.

Fix

Run:

chmod +x /path/to/Kalium-1.1.0-x86_64.AppImage

Then try:

/path/to/Kalium-1.1.0-x86_64.AppImage --version

3. The AppImage opens but does nothing

Make sure you are using the correct Kalium AppImage:

Kalium-1.1.0-x86_64.AppImage

Do not substitute another AppImage file that may have been produced during development or packaging.

Test the AppImage

Run:

/path/to/Kalium-1.1.0-x86_64.AppImage -h

If the CLI help appears, the AppImage is executing correctly.

4. Steam is not detected / Proton is missing

Kalium requires a working Steam installation and at least one Proton 10+ environment for the current 1.1.0 workflow.

Fix

Make sure Steam is installed and working.
Install or enable a Proton 10+ version.
Run:

/path/to/Kalium-1.1.0-x86_64.AppImage check-steam

You can also open the Diagnostics tab in Kalium.

Supported Proton environments may include Proton variants such as GE-Proton or other Proton 10+ builds, provided they are compatible with your Steam installation.

5. MO2 installation fails with `not found at /path/to/mo2`

The path supplied with -p does not contain:

ModOrganizer.exe

Fix

Point -p to the folder containing ModOrganizer.exe.

Example:

/path/to/Kalium-1.1.0-x86_64.AppImage setup-mo2 -p /path/to/mo2

Use an absolute path.

6. `USVFS 0.5.6 — update to 0.5.7.2 recommended`

Older USVFS versions can cause virtual-folder duplication and other compatibility problems with newer Wine/Proton environments.

Fix

Run:

/path/to/Kalium-1.1.0-x86_64.AppImage install-usvfs -p /path/to/mo2

New MO2 installations will receive the updated USVFS automatically.

Existing installations can be updated manually using the command above or through Kalium's MO2 interface.

7. LOOT is not installed

Kalium uses a portable LOOT installation located alongside the MO2 instance.

Fix

Run:

/path/to/Kalium-1.1.0-x86_64.AppImage install-loot -p /path/to/mo2

Kalium will:

Download portable LOOT.
Install it into the MO2 environment.
Create the run_loot.bat launcher.
Configure ModOrganizer.ini.
Bind LOOT to the selected game.

8. `ModOrganizer.ini not created yet`

Portable MO2 may not create its configuration file until it has been launched at least once.

Fix

Launch MO2 once.

Then run:

/path/to/Kalium-1.1.0-x86_64.AppImage setup-mo2 -p /path/to/mo2

Kalium can then configure the existing MO2 environment.

9. Backpatch fails / `No depot found`

This generally means the required Steam depots have not finished downloading or the wrong content directory was selected.

Fix

Wait for the Steam depots to finish downloading.
Verify that the correct content directory is being used.
For Skyrim SE, this will typically be:

steamapps/content/app_489830

Run the backpatch operation again.

The backpatcher handles the supported game targets, but Steam depot availability and download state are outside Kalium's control.

10. NXM links are not working

The NXM handler may not be registered correctly, or the browser may be associated with the wrong application.

Fix

Run:

/path/to/Kalium-1.1.0-x86_64.AppImage enable-nxm

Then verify that your browser is using the Kalium NXM Handler, rather than attempting to launch the main Kalium application directly.

Important Design Boundary

Kalium is an environment manager for MO2 and Windows-based modding tools running through Proton.

Kalium does not replace MO2.

MO2 remains responsible for:

Mod management
Profiles
Load order
Mod activation
Virtual filesystem management
Mod installation

Kalium is responsible for preparing and maintaining the environment around MO2, including:

Steam integration
Proton environments
MO2 installation
NXM registration
USVFS maintenance
LOOT integration
MO2 plugin installation
Path compatibility
Steam library detection
Depot backpatching
Diagnostics and recovery

This separation is intentional. Kalium is designed to get as close to the normal Windows MO2 workflow as possible without becoming a replacement for MO2 or attempting to manage MO2's internal behavior.

Beta Status

Kalium 1.1.0 is currently a Beta release.

The following areas are still undergoing additional testing:

Steam depot backpatching
LOOT integration and accuracy
GOG support
Heroic support
Compatibility across different Proton/Wine versions
Compatibility with large and complex modlists

LOOT currently runs inside the same Proton environment as the selected MO2 instance. This allows it to interact with the MO2 virtualized filesystem through USVFS. Further testing is being performed before making stronger claims about parity with native Windows LOOT behavior.

If you encounter a problem, run:

/path/to/Kalium-1.1.0-x86_64.AppImage diagnose

and attach the generated diagnostic report to your issue when possible.

Kalium is actively being tested and improved during the 1.1.0 Beta cycle.

Uh oh!

CLI Diagnostics Troubleshooting

Kalium 1.1.0 Beta

Quick Start — AppImage

Command syntax

Check the Kalium version

Display CLI help

Full CLI Help (-h)

CLI Command Reference

Diagnostics

status

check-steam

diagnose

Example results

Troubleshooting

1. bash: /path/to/kalium: Is a directory

Fix

2. Permission denied or Cannot execute binary file

Fix

3. The AppImage opens but does nothing

Test the AppImage

4. Steam is not detected / Proton is missing

Fix

5. MO2 installation fails with not found at /path/to/mo2

Fix

6. USVFS 0.5.6 — update to 0.5.7.2 recommended

Fix

7. LOOT is not installed

Fix

8. ModOrganizer.ini not created yet

Fix

9. Backpatch fails / No depot found

Fix

10. NXM links are not working

Fix

Important Design Boundary

Beta Status

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Clone this wiki locally

Full CLI Help (`-h`)

`status`

`check-steam`

`diagnose`

1. `bash: /path/to/kalium: Is a directory`

2. `Permission denied` or `Cannot execute binary file`

5. MO2 installation fails with `not found at /path/to/mo2`

6. `USVFS 0.5.6 — update to 0.5.7.2 recommended`

8. `ModOrganizer.ini not created yet`

9. Backpatch fails / `No depot found`