Skip to content

[Public Beta] AuriType for Linux Desktop Is Now Open for Testing

Hello Linux desktop users,

After more than half a year of continuous work, AuriType (聆风) has entered public beta on Linux desktops.

Chinese input on Linux is not short of workable options. What still interrupts the rhythm are small, recurring frictions: pinyin left behind in a GTK4 editor after commit, the keyboard LED and your actual case drifting apart while mixing Chinese and English, the candidate box lagging behind the caret under Wayland, and rare characters turning into tofu boxes.

AuriType starts from a cross-platform semantic core runtime (libauri). The first public beta concentrates on one path: Ubuntu 24.04 LTS / 26.04 LTS + GNOME + IBus + Wayland, and takes those high-frequency, easily-compromised engineering details seriously.

The details I am working on

1. Intent belongs to the user: process the input, do not keep it as a data asset

  • Local inference: candidate ranking, long-sentence segmentation, and error tolerance happen only in local memory, in the current input session. Nothing is uploaded, and no user profile is built. Words the engine learned are written only to your own user dictionary on your own disk, and can be exported or forgotten at will.
  • No sign-in, no ads: there is no account system. By default the logs do not contain what you typed — not the composition string, not the candidates, not the committed text — and the data model reserves no field for “understanding the user”.
  • Model neutral: the cloud side is an optional plug-in, off by default, and once enabled it talks to any OpenAI-compatible endpoint (your own key, or a private local deployment). No data leaves the machine without explicit permission.

2. Facing the seams of the Linux input stack

  • Nothing left behind in the host: while composing, the preedit is never written into the host document — on Linux the engine clears update_preedit_text, and the pinyin is drawn only in the panel header. The “ghost pinyin a GTK4 editor cannot get rid of after commit” never gets a chance to exist.
  • Keyboard LED sync: Caps Lock is treated as an input state that every keystroke path must observe faithfully, not a flag that may be approximated. The lamp, the A badge on the panel, and letter pass-through follow one rule, so switching between Chinese, English, and code does not lose the beat.
  • Wayland candidate panel anchoring: the candidate box is a self-drawn window in its own process, and its position has to be reconciled between GNOME Shell, IBus, and the host’s insertion point. On GNOME a caret-tracking extension is responsible for reading that point (after a first install, log out and back in once so it loads). Bridging to native Wayland text-input-v3 and to Fcitx5 is a later route; this beta still runs on IBus.

3. A rendering layer of its own: ending tofu boxes in the candidate panel

  • The panel has its own font fallback chain: the family you pick → the fallback you set → the bundled Alibaba PuHuiTi 3.0 → the system sans-serif.
  • Two TTFs of the same family ship inside it, and AlibabaPuHuiTi-3-55-Regular-L3.ttf covers the GB 18030-2022 extension plane. A missing glyph falls through to the face that actually has it. Rare characters stay legible in the candidate box without depending on which fonts the host application happens to have.
  • Once the text is committed, rendering goes back to the editor’s own font — the input method does not reach past its job to replace the host’s typography.

4. Mature language-model priors

  • The core lexicon and language model inherit and refine the Wanxiang pinyin scheme (rime-wanxiang) from the open-source community, so long-sentence segmentation and first-choice hit rate rest on solid priors.
  • Upstream licenses are declared in full in every distribution: the lexicon CC BY 4.0, the candidate panel and IBus frontend GPL-3.0, libauri BSD-3-Clause. After installation you can read them in /usr/share/doc/<package>/copyright.

Quick install (Ubuntu 24.04 / 26.04 LTS)

The current beta ships an amd64 .deb combined package:

Terminal window
# 1. Get the package from the beta download page
# https://auritype.com/download/
# 2. Install the combined package (runtime + lexicon + IBus frontend — this one is enough)
sudo apt install ./auritype_*.deb
# 3. Reload the engine
ibus restart

Enable it: Ubuntu Settings → Keyboard → Input Sources → click + → choose Chinese → add 聆风拼音 (engine name auritype-pinyin).

After the first install, log out and log back in once, otherwise the candidate window may not sit next to the insertion point. Afterwards, a self-check helps:

Terminal window
auri-doctor

What this beta is, and what it is not

This build is not yet a general stable release; it is an experimental build and an invitation to test it.

  1. The current boundary: right now all effort goes into making Ubuntu + GNOME + IBus + Wayland + GTK4 solid. Fcitx 5, other non-GNOME desktops, and domestic distributions (Kylin / UOS, and so on) will be picked up in order once this path has been verified properly — until then, neither the site nor the packages describe them as supported.
  2. Defects stated plainly: if you hit caret-tracking problems or dropped keys on complex multi-monitor setups, particular legacy X11 applications, or some Electron containers, please open an issue that reproduces. The output of auri-doctor is the most useful attachment.
  3. Performance baselines: resident memory and deterministic latency are hard usability floors for me. Measured numbers will be published with the build logs rather than promised in advance.

Repositories and feedback

I want to earn this gradually, with verifiable deliveries and clear boundaries. I look forward to your keystrokes and your honest feedback.