https://bugs.kde.org/show_bug.cgi?id=522089
David Edmundson <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|REPORTED |CONFIRMED --- Comment #3 from David Edmundson <[email protected]> --- I haven't tested anything, but this is problematic: inputmethod.cpp has a QXkbCommon::ScopedXKBState mXkbState; ``` void Keyboard::keyboard_modifiers(uint32_t serial, uint32_t mods_depressed, uint32_t mods_latched, uint32_t mods_locked, uint32_t group) { xkb_state_update_mask(mXkbState.get(), mods_depressed, mods_latched, mods_locked, 0, 0, group); ``` OverlayController::OverlayController m_xkbComposeState = xkb_compose_state_new(m_xkbComposeTable, XKB_COMPOSE_STATE_NO_FLAGS); Creates a new compose state, the one in OverlayController is used to resolve keysyms, it never updates the group from modifiers. ---- We should just have one xkb object throughout. Even with 6.7.2 it might resolve the bug reported, but if you had: QWERTY AZERTY as your layouts, then switched to layout(group) 1, and press and hold the top left keyboard key that should resolve to "A" we would want the right popup. -- You are receiving this mail because: You are watching all bug changes.
