Skip to content

Defer XCompose reloads from migrations - #9568

Open
rookepoole wants to merge 1 commit into
omacom:quattrofrom
rookepoole:fix/defer-xcompose-restart
Open

Defer XCompose reloads from migrations#9568
rookepoole wants to merge 1 commit into
omacom:quattrofrom
rookepoole:fix/defer-xcompose-restart

Conversation

@rookepoole

Copy link
Copy Markdown

Summary

Stop the legacy XCompose migration from restarting fcitx5 while graphical applications are running.

The migration still repairs every supported Omarchy 3 include and preserves the user's custom compose sequences. The updated configuration is picked up at the next graphical login. This avoids invalidating XIM objects retained by X11 clients such as Steam, which can otherwise crash later when they create another input context.

The manual omarchy-restart-xcompose command is unchanged for users who explicitly choose a live reload.

Closes #9541

Test plan

  • bash -n migrations/1788102906.sh test/shell.d/legacy-power-udev-rules-migration-test.sh
  • ./test/shell.d/legacy-power-udev-rules-migration-test.sh
  • ./test/all (changed test passes; suite retains five unrelated baseline failures: three require an omarchy-pkgs checkout, plus the existing launch-about and network-QR assertions)

Related work

PR #9282 changes the XCompose include layout for sandboxed applications. If it lands, its migration should likewise leave live input-method reloads to an explicit user action or the next graphical login.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant