Input and display form parallel groups. Fcitx 5 provides the input framework and application communication; Chinese Addons supplies Chinese conversion engines. brightnessctl, ddcutil and hyprsunset address backlight devices, compatible monitor hardware controls and software color temperature respectively.
Entering Chinese text: keyboard input follows the application’s input-method integration; Fcitx invokes the selected engine to produce candidates, then commits the chosen text to the application. Poor candidates, inability to activate an engine, and failure in one application belong to different stages. A keyboard layout is not a Chinese conversion engine.
Adjusting a display: a laptop panel may expose a brightnessctl-compatible backlight, while an external monitor may accept ddcutil’s DDC/CI commands. Hardware and connection determine support. hyprsunset changes color temperature with Hyprland rather than physical backlight intensity.
These display tools are not a pipeline processing one brightness value. Identify the display and whether the desired change concerns brightness or color temperature first.
Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.
Input-method framework. Language engines and GTK/Qt integration are separate packages.
Package
fcitx5
Membership
Core manifest
Omarchy configuration or entry point
Setup → Input
Purpose and everyday use
Coordinates input methods and candidate selection, especially for languages that need composition. A keyboard layout alone does not provide Pinyin conversion.
How it works and connects
The framework loads language engines and communicates with applications through toolkit or protocol integration. GTK, Qt and Wayland applications may follow different paths.
Configuration and customization
Use Omarchy’s input setup and select an installed engine. Framework installation, engine availability, activation shortcuts and application integration are separate settings.
Troubleshooting approach
Test in more than one application. If only one toolkit fails, inspect its integration; if none work, check whether the input-method process and engine are active.
Limits and change considerations
Do not blindly combine environment snippets from X11 and Wayland tutorials. Candidate windows and composition behavior can depend on application support.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi fcitx5
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Chinese input engines, including Pinyin. Present in this snapshot’s core manifest; configuring input remains a separate step.
Package
fcitx5-chinese-addons
Membership
Core manifest
Purpose and everyday use
Adds Chinese input engines such as Pinyin to Fcitx 5. It supplies language-specific conversion rather than the entire input-method service.
How it works and connects
Typed sequences are converted into candidates through the selected engine and its dictionaries. Fcitx handles activation and communication with the application.
Configuration and customization
Select the Chinese engine in input settings, then adjust punctuation, candidate behavior and dictionaries supported by that engine. Back up personal dictionaries before migration.
Troubleshooting approach
If the engine is absent from the list, verify package installation and refresh the input-method session through the supported workflow. Application-only failures belong to integration troubleshooting.
Limits and change considerations
This snapshot includes it in the core manifest, but installation does not mean an engine is selected. Different Chinese input engines have different dictionaries and settings.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi fcitx5-chinese-addons
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Adjusts display color temperature for night-light use.
Package
hyprsunset
Membership
Core manifest
Purpose and everyday use
Changes display color temperature for a warmer night-light appearance. It changes color presentation rather than physical backlight brightness.
How it works and connects
Works with Hyprland’s display capabilities. The shell can expose a convenient toggle while the color-temperature tool performs the adjustment.
Configuration and customization
Use the provided night-light control first. If adding custom scheduling, ensure only one tool is responsible for color-temperature changes.
Troubleshooting approach
If a display remains unusually warm, check active night-light state before changing monitor calibration. Compare displays and recent session changes.
Limits and change considerations
Warm color temperature changes perceived colors and is unsuitable for judging color-critical work without accounting for it. It does not fix GPU output failures.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi hyprsunset
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Controls supported backlight devices. External monitors may use DDC/CI instead.
Package
brightnessctl
Membership
Core manifest
Purpose and everyday use
Reads and adjusts brightness on supported backlight or LED devices. Commonly relevant to laptop panels and keyboard lighting.
How it works and connects
Uses kernel-exposed device interfaces. Desktop sliders may call a brightness tool, but the actual available range comes from the device and driver.
Configuration and customization
Identify the target device before assigning shortcuts. Multiple brightness devices may exist; a broad command can select a different device than intended.
Troubleshooting approach
Inspect device information and permissions. If an external monitor is unaffected, investigate DDC/CI support rather than repeatedly changing laptop backlight settings.
Limits and change considerations
Not every screen exposes a compatible backlight device. Very low brightness can make recovery difficult, so test incremental changes.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi brightnessctl
brightnessctl info
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Communicates with supported external monitors through DDC/CI.
Package
ddcutil
Membership
Core manifest
Purpose and everyday use
Communicates with compatible external monitors to query or change hardware controls such as brightness. Useful when laptop backlight controls do not affect an external display.
How it works and connects
Uses DDC/CI and monitor feature codes over the available display connection. Monitor firmware, cables and docks can all affect communication.
Configuration and customization
Identify the intended monitor and supported features before setting values. Some monitors require DDC/CI to be enabled in their own on-screen menu.
Troubleshooting approach
If discovery fails, compare a direct cable connection with the dock path and check monitor settings. Do not assume every advertised feature is implemented reliably.
Limits and change considerations
It does not control window scaling or night-light color transforms. Feature support varies, and repeatedly polling hardware can be slow.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi ddcutil
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.