OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
audio-input low occasional DISPUTE

Stop omarchy-fcitx5.service restarting every two seconds and flooding the journal

omarchyhyprlandwaylandfcitx5systemddesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Re-checked on 4.0.4-1. /usr/lib/systemd/user/omarchy-fcitx5.service has Restart=always and RestartSec=2 with the exit-0 comment, /usr/bin/omarchy-update-pacman-guard aborts only transactions with both -S and -u, so the plain pacman -S --needed fcitx5 stands, and migration 1785167800.sh only pkills fcitx5. Issue #7461 read in full, including comments after the first audit. It documents a fifth entry point the record missed (playGitboy, 2026-09-26): the packaged /etc/xdg/autostart/org.fcitx.Fcitx5.desktop, run by systemd-xdg-autostart-generator as app-org.fcitx.Fcitx5@autostart.service. Omarchy suppresses it by shipping ~/.config/autostart/org.fcitx.Fcitx5.desktop containing only Hidden=true (present on this workstation, from /usr/share/omarchy/config/autostart, quattro commit 5ca74821), and xdg-desktop-autostart.target is active here. That makes step 1's rm ... # whatever filename grep found dangerous: a user who customised org.fcitx.Fcitx5.desktop with an Exec line would delete the mask and re-enable the packaged entry, recreating the loop. The fix now restores the mask instead of deleting that file and checks for the generated autostart unit, and the cause lists the packaged entry. Not exercised: no unit change made.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

journalctl --user fills at about 11 lines per second with Failed to create addon: dbus Unable to request dbus name. Is there another fcitx already running? and omarchy-fcitx5.service: Scheduled restart job, restart counter is at 10953. systemctl --user show omarchy-fcitx5.service -p NRestarts shows thousands (71,243 in one report). Input still works. Steam's webhelper may crash in XCreateIC while this churns. A variant logs status=203/EXEC because /usr/bin/fcitx5 is not installed.

Cause

omarchy-fcitx5.service uses Restart=always with RestartSec=2. fcitx5 exits 0 when another instance already owns org.fcitx.Fcitx5, and the unit restarts it forever. About 2.1 seconds per cycle never exceeds the default StartLimitBurst=5 in 10 seconds, so systemd never gives up. The competing instance comes from one of: the fcitx5 package's own /etc/xdg/autostart/org.fcitx.Fcitx5.desktop, which runs as app-org.fcitx.Fcitx5@autostart.service whenever the Hidden=true mask Omarchy ships at ~/.config/autostart/org.fcitx.Fcitx5.desktop is missing or edited, a user autostart entry under any other filename (for example ~/.config/autostart/fcitx5.desktop with Exec=fcitx5 -d, which the Quattro migration only pkilled), D-Bus activation through /usr/share/dbus-1/services/org.fcitx.Fcitx5.service, or a hand-run fcitx5 -r -d (for example after installing fcitx5-mozc).

Fix

Find who owns the bus name and which autostart entries exist:


busctl --user status org.fcitx.Fcitx5 | grep -E '^(PID|CGroup)='
grep -l 'Exec=.*fcitx5' ~/.config/autostart/*.desktop 2>/dev/null
cat ~/.config/autostart/org.fcitx.Fcitx5.desktop 2>/dev/null    # Omarchy ships this as Hidden=true
systemctl --user list-units --all --no-legend 'app-*Fcitx5*'
systemctl --user show omarchy-fcitx5.service -p NRestarts -p ExecMainStatus
  1. Remove the competing autostart. Never delete ~/.config/autostart/org.fcitx.Fcitx5.desktop: it is the mask that stops the package's own autostart entry. If it is missing or no longer says Hidden=true, put the mask back. Remove any other file the grep found:

printf '[Desktop Entry]\nHidden=true\n' > ~/.config/autostart/org.fcitx.Fcitx5.desktop
rm ~/.config/autostart/fcitx5.desktop      # only a file other than org.fcitx.Fcitx5.desktop that grep found
systemctl --user stop 'app-org.fcitx.Fcitx5@autostart.service' 2>/dev/null
pkill -x fcitx5
systemctl --user restart omarchy-fcitx5.service
  1. Stop clean exits from looping (covers D-Bus activation and hand-started instances, real crashes still restart):

mkdir -p ~/.config/systemd/user/omarchy-fcitx5.service.d
printf '[Service]\nRestart=on-failure\n' > ~/.config/systemd/user/omarchy-fcitx5.service.d/restart.conf
systemctl --user daemon-reload
systemctl --user restart omarchy-fcitx5.service
  1. If the log says status=203/EXEC, the binary is missing and on-failure will not stop it. Install it or disable the unit. A plain -S install is not a system upgrade, so Omarchy's pacman guard does not block it and no bypass variable is needed:

sudo pacman -S --needed fcitx5
# or
systemctl --user disable --now omarchy-fcitx5.service

After installing an fcitx5 addon later, use systemctl --user restart omarchy-fcitx5.service, never fcitx5 -r -d.

Verify

systemctl --user show omarchy-fcitx5.service -p NRestarts stays constant over a minute, busctl --user status org.fcitx.Fcitx5 | grep CGroup shows omarchy-fcitx5.service, and after the next login systemctl --user list-units --all --no-legend 'app-*Fcitx5*' lists nothing running.

Sources

omarchy-fcitx5-service-restart-loop