Comment 5 for bug 1999207

I'm a bit confused about your questions related with xkb-data but I hope that this will help: here is the result of `setxkbmap -print`:

xkb_keymap {
 xkb_keycodes { include "evdev+aliases(azerty)" };
 xkb_types { include "complete" };
 xkb_compat { include "complete" };
 xkb_symbols { include "pc+fr(latin9)+fr(oss):2+inet(evdev)" };
 xkb_geometry { include "pc(pc105)" };
};

And `setxkbmap -query`:

rules: evdev
model: pc105
layout: fr,fr
variant: latin9,oss

About the consequences for users, well, the source of all this is the breaking of compositionupdate and compositionend events for those users on Firefox. My app relies on compositionend events, but, as those events were not created by myself, I guess that my app is not the only program relying on those events. If those events are not accurate, it will break any program relying on it.