openjdk/jdk · warning

Couldn't find X Input Context\n

Error message

Couldn't find X Input Context\n

What it means

Printed by setXICFocus() in the XAWT input-method code when Java asks to set or unset X Input Method focus on an XIC that is NULL — i.e. the input context for the focused component could not be found or was already destroyed. The call is then skipped, so XIM focus tracking silently diverges from AWT focus; text composition (preedit/commit) may stop working for that component.

Source

Thrown at src/java.desktop/unix/native/libawt_xawt/awt/awt_InputMethod.c:409

        removeX11InputMethodGRefFromList(pX11IMData->x11inputmethod);
        (*env)->DeleteGlobalRef(env, pX11IMData->x11inputmethod);
    }

    if (pX11IMData->lookup_buf) {
        free((void *)pX11IMData->lookup_buf);
    }

    free((void *)pX11IMData);
}

/*
 * Sets or unsets the focus to the given XIC.
 */
static void
setXICFocus(XIC ic, unsigned short req)
{
    if (ic == NULL) {
        (void)fprintf(stderr, "Couldn't find X Input Context\n");
        return;
    }
    if (req == 1)
        XSetICFocus(ic);
    else
        XUnsetICFocus(ic);
}

/*
 * Sets the focus window to the given XIC.
 */
static void
setXICWindowFocus(XIC ic, Window w)
{
    if (ic == NULL) {
        (void)fprintf(stderr, "Couldn't find X Input Context\n");
        return;
    }

View on GitHub (pinned to 88dfb74bbe)

Solutions

1. Verify the input method server is alive: restart ibus/fcitx and check XMODIFIERS (@im=ibus/@im=fcitx) matches the running server
2. Re-launch the application after the IM server is back; stale XICs from before the restart cannot recover
3. Avoid closing windows while composition is active — commit or cancel composition before dispose
4. On Wayland, run the app in a proper XWayland session with the same IM environment set

// before launching a GUI app that needs IME, sanity-check the IM environment
String xm = System.getenv("XMODIFIERS");
if (System.getenv("XDG_SESSION_TYPE").equals("x11") && (xm == null || xm.isEmpty())) {
    System.err.println("XMODIFIERS unset — IME focus (XIC) may be unavailable");
}

When it happens

Trigger: XSetICFocus/XUnsetICFocus requests arriving after XDestroyIC ran for a window's context, or when XCreateIC failed earlier (missing XMODIFIERS, dead input-method server) leaving currentXIC == NULL. Typical during rapid window close/reopen, focus changes while an IME restarts, or opening/closing composition-enabled components.

Common situations: Running under X11 with XMODIFIERS pointing at a crashed/hung IM server (ibus/fcitx restarted under the app); usinginput-method frameworks with dialogs that gain focus during disposal; remote X sessions where the IM server connection drops. Mostly harmless noise but signals IME may be dead for that window.

Related errors

• Couldn't find X Input Context
• Failed to retrieve atom name.
• %s\n
• Error: Out of memory in ADLC\n
• JVM caught ASAN Error

AI-assisted analysis of openjdk/jdk@88dfb74bbe (2026-08-14). Data as JSON: /api/errors/df540446254c94a7. Report an issue: GitHub.