MComix is available in most major distributions' packaging systems, and should be installed using the distribution's system mechanism if possible. If your distribution only ships an ancient version of MComix, you might opt to install it as Flatpak instead.
Ubuntu has packaged an up-to-date version of MComix starting with Ubuntu 23.04 (Lunar). The same holds true for Debian 12 (Bookworm).
~ $ sudo apt install mcomix
openSUSE users can download a current MComix version starting from openSUSE 15.4 (Leap)
~ $ sudo zypper install mcomix
The Arch Linux User Repository (AUR) usually has the most current version of MComix.
~ $ yay -S mcomix
If your distribution supports the installation of Flatpaks, you can download and install MComix from Flathub:
~ $ flatpak install flathub net.sourceforge.mcomix
Starting with version 3.0.0, MComix is available from the WinGet package manager.
PS > winget install mcomix
Users of the Chocolatey package manager can download the mcomix
package, which takes care of installation and upgrading MComix.
PS > choco install -y mcomix
MComix is also available in the Extras bucket of the Scoop package manager. Follow the following steps in a console:
> scoop bucket add extras
> scoop install extras/mcomix
Simply install the MSI package. The installation requires administrator access. If such access is not available on the machine you plan to use MComix on, you can fall back extracting mcomix-win64-<version>.zip
anywhere on your harddisk, and run MComix.exe
from there.
The uninstaller leaves user data, such as the configuration and library contents, on your disk. To completely remove these files, manually delete the folder %APPDATA%/MComix
.
Since MComix has heavy dependencies on non-Python binary packages that are tendious to install, running it from source is somewhat difficult. At the very least, you will need PyGObject, which has a very good Getting Started guide for various operating systems. Please remember that MComix still requires GTK 3, while the documentation usually refers to the GTK 4 package. Adapt package manager calls as needed when installing the packages.
Some examples:
* Replace mingw-w64-x86_64-gtk4
with mingw-w64-x86_64-gtk3
on Windows/MSYS2
* Replace gir1.2-gtk-4.0
with gir1.2-gtk-3.0
on Ubuntu/Debian
* Replace gtk4
with gtk3
on Arch Linux
Windows/MSYS2 note: Due to a bug in Setuptools, the ujson package, which is needed to process pyproject.toml projects, cannot be built on MSYS2. Please install the mingw-w64-x86_64-python-ujson
package from Pacman.
With PyGObject installed, you can now create a virtual environment for MComix. Virtual environments used in Python to separate dependencies of various Python applications from each other, in order to avoid depdency conflicts between system and application packages. Virtual environments can be created in a variety of ways using different packages, but the most simple is probably using the venv
package, which is often bundled with Python.
~ $ python3 -m venv --system-site-packages mcomix-venv
~ $ source mcomix-venv/bin/activate
(mcomix-venv) ~ $
Using the --system-site-packages
switch is important to give the environment access to system packages. Without it, you will be missing the pre-built PyGObject library, and Python will attempt to build it from source, which will likely fail unless you installed a lot of additional dependencies. When the virtual environment has been activated by sourcing the activation script, all calls to python
, pip
and similar Python tools will now refer to your virtual environment instead of the system environment. This means that you can easily install packages even without elevated rights, and uninstall them quickly by deleting the virtual environment directory. Instead of first activating the virtual environment in the shell, it is also possible to call mcomix-venv/bin/python
directly.
With the virtual environment activated, extract the MComix source tarball and install the package using the pip
standard module:
(mcomix-venv) ~ $ tar -xzf mcomix-<versionnr>.tar.gz
(mcomix-venv) ~ $ cd mcomix-<versionnr>
(mcomix-venv) mcomix-<versionnr> $ python -m pip install .
Pip now installs all required dependencies as well as the mcomix
executable. When the virtual environment is active, calling mcomix
will now run the program. You can also run mcomix-venv/bin/mcomix
directly without activating the virtual environment.
If you want additional file format support for MComix, install the optional depdency fileformats
:
(mcomix-venv) mcomix-<versionnr> $ python -m pip install .[fileformats]
On Linux, you may want to copy additional application meta files to /usr/local/share/
for better desktop integration. All files are stored in the share
folder in the MComix source archive, with paths already matching their expected destination in /usr/local/share
. Please note that these files cannot be automatically uninstalled when copied by hand.
The extracted MComix directory can now be safely deleted. To uninstall MComix, simply delete the virtual environment folder, and MComix' settings directory. It can be found in your user directory, usually ~/.config/mcomix
on Linux and %APPDATA%/MComix
on Windows.
You can mostly follow the regular instructions above. Instead of using a source tarball, check out the repository from SourceForge with Git. Then, in the repository folder, install an editable package of MComix by passing the -e
switch to pip install
. This will still download all dependencies, but instead of copying a read-only package to your virtual environment, the package will be linked to the repository source code. This way, you can modify the source code, and changes will appear immediately after restarting MComix.
(mcomix-venv) mcomix $ export PYGOBJECT_STUB_CONFIG=Gtk3,Gdk3,Soup2
(mcomix-venv) mcomix $ python -m pip install -e .[dev]
The dev
optional depdency installs tools for static code analysis, Python language server and other useful tools.