Fix: Can't Type in SolidCraft on Linux (AppImage and .deb)

Run SolidCraft in your browser

The official web build, loaded right here. No install, no account. Desktop browser with a mouse recommended.

Loads the open-source web build (a few MB). Your models stay in your browser.

Next: get the desktop app

We picked your system. Files come straight from the official GitHub release (always the latest version).

Latest release: v0.30.1 (2 November 2026)

The installers are not code-signed yet, so Windows or macOS may warn you the first time. How to get past the warning.

If SolidCraft on Linux opens fine but no key does anything, not in the dimension boxes, not in text fields, not even Backspace or paste, the cause is usually your desktop's input-method setting, not SolidCraft itself. The fix is to launch the app with input methods switched off:

XMODIFIERS="@im=none" ./solidcraft-linux-x86_64.AppImage

If you just need to get some modelling done right now, the browser version at the top of this page is not affected.

This fix comes from a reader

This page exists thanks to a SolidCraft user on Linux who wrote to us in October 2026 and tested every step below on their own machine. They reported the problem, tried our first suggestion, found it only lasted one session, and worked out the launcher script that fixed it for good. Thank you!

The symptoms

Their report is a textbook case, so here is what they saw:

The setup: Loc-OS 23 on an older laptop, running X11, not Wayland. Since the in-app bug report also needs the keyboard, it couldn't be used to report the problem.

If that list matches what you see, read on.

Why it happens

On X11, the XMODIFIERS environment variable tells programs which input-method server to send keystrokes through, for example @im=ibus or @im=fcitx. Input methods are what let you type Chinese, Japanese or accented characters. When that hand-off doesn't work for a particular app, the keystrokes disappear on the way and the app never sees them.

Setting XMODIFIERS="@im=none" tells SolidCraft not to use an input method at all, so keys go straight to the app. It only changes the environment for that one program: the rest of your desktop keeps its input method.

Step 1: test the fix from a terminal

Open a terminal in the folder with the AppImage and run:

chmod +x solidcraft-linux-x86_64.AppImage
XMODIFIERS="@im=none" ./solidcraft-linux-x86_64.AppImage

Use your file's real name: release files can include the version number, such as solidcraft-0.23.1-linux-x86_64.AppImage. If you installed the .deb, run XMODIFIERS="@im=none" solidcraft instead.

Open a sketch, draw a rectangle and type a dimension. If the numbers appear, you have found the cause.

Step 2: make it permanent with a launcher script

This is the step that matters. When our reader first tried the variable, it worked, but the next time they started SolidCraft normally, the problem came back: they could save their work, but after reopening SolidCraft they couldn't type anything again. The variable only lasts for the launch where you type it.

Their solution was a small launcher script. Save this as solidcraft.sh in your home folder, changing the folder and file name to match yours (in this example the AppImage lives in ~/soft):

#!/usr/bin/env bash
cd "$HOME/soft" || exit 1
XMODIFIERS="@im=none" exec ./solidcraft-0.23.1-linux-x86_64.AppImage "$@"

Make it executable and use it to start SolidCraft from now on:

chmod +x ~/solidcraft.sh
~/solidcraft.sh

The "$@" at the end passes any file you open with the script through to SolidCraft, so ~/solidcraft.sh bracket.sc still works. With this in place, every text field works, every time.

Tip: to start it from your applications menu instead, point the menu entry's Exec= line at the script. When you update SolidCraft, remember to change the file name in the script, since a new AppImage has a new name.

Still not working?

Once you can type again, our SolidCraft tutorial walks you through your first part.

FAQ

Why can't I type anything in SolidCraft on Linux?

On some X11 desktops the input-method setting (the XMODIFIERS environment variable) routes keystrokes through an input-method server, and SolidCraft never receives them. Mouse clicks still work, which is why you can select a field but not type in it.

What is the fix?

Launch SolidCraft with input methods switched off: XMODIFIERS="@im=none" ./solidcraft-linux-x86_64.AppImage for the AppImage, or XMODIFIERS="@im=none" solidcraft for the .deb. Put that line in a small launcher script so it applies every time.

It worked once, then broke again after I restarted SolidCraft. Why?

The variable only applies to the launch where you typed it. Starting SolidCraft again from the menu or by double-clicking uses your normal environment again. Use a launcher script or edit the menu entry so the setting is always there.

Will this break typing in other languages?

It only affects SolidCraft, not the rest of your desktop. You lose your input method (for example an IME for Chinese or Japanese) inside SolidCraft, but normal keyboard input, Backspace and copy-paste work again.

Does the browser version have the same problem?

No. The free browser version takes keyboard input through the browser, so it is not affected. It is a good fallback while you set up the desktop fix.

Sources

Last updated: