Dmitry Azaraev

I have similar issue, but it probably bit different, but generally looks same: Arch Linux: 1) labwc/wlroots as backend: wlfreerdp (2.11.4) - generally works fine. 2) kwin - exactly same...

I'm trace problem a bit, and the problem I'm think at labwc side, I guess. For first normal Shift keydown/keyup sequence: 1. Shift pressed: `wl_keyboard_listener::key` - OK (indicates key pressed)...

I'm just printf'ed this events in wlfreerdp directly.

`WAYLAND_DEBUG=1 foot` is enough to see this thing, it is not specific to wlfreerdp.

@charbelnicolas no, there is different - modifier events in this case already flow as they should, but key events (e.g. key release) doesnt not flow. PS: Key modifier events are...

@Consolatis I guess it was default config. Now it have some explicitly defined theme, and border=1. Just re-tested: simply removed last font package, and tried to run nested labwc. ```...

@Consolatis it should be easy: Create empty config file: ```xml ``` Then run: `FONTCONFIG_FILE=${HOME}/path_to_empty_config.conf labwc`

@droc12345 checking "what font list is empty" is technically impossible . You never touch fontconfig directly, nor be able make real/meaningful request to it. The issue what pango/cairo (i forget...

Option 2 is bad by design, because font-config is dynamic thing. You can uninstall fonts on running instance and rely exclusively on cached data, and no one guarantee consistent responses...

@droc12345 as I'm seen usually already loaded fonts keep just working, even if you uninstall them. But this is just impl detail because freetype and/or pango is cache glyphs in...