bug#65068: 29.1; xkb-interception interaction causes problems with key combinations

["Alexander Prähauser" <alexander.praehauser@gmx.at>]

I just noticed that the last line in the dual-function-keys config 
contains an x I must have inadvertantly written in at
some point and not noticed because I hadn't restarted udevmon 
since. Please remove that x if you try it out, otherwise
it will produce an error.

Alexander Prähauser [2023-08-16 Wed 09:50] wrote:

> [1. xkb file --- text/plain; server-0.xkb]...
>
>
> Note that I the command produced the following warning:
>
>> Warning:          Could not load keyboard geometry for :0
>>                   BadName (named color or font does not exist)
>>                   Resulting keymap file will not describe
>> geometry
>
> The keymap seems alright though. I've been modifying the 
> adnw-keymap
> because making a new one didn't really work with
> the modifiers. Here is also my dual-function-keys config:
>
> [3. dual function keys config --- text/plain; 
> my-mappings.yaml]...
>
>
>
> Po Lu [2023-08-16 Wed 09:29] wrote:
>
>> Alexander Prähauser <alexander.praehauser@gmx.at> writes:
>>
>>> Sorry for the late reply.
>>>
>>>> Which virtual modifier key have you assigned to the 
>>>> apostrophe
>>>> key?
>>>
>>> I've made the apostrophe key (AC11 in xkb) a level 3 switch 
>>> through
>>> the following function:
>>>
>>>> // The AC11 key (while pressed) chooses the third shift 
>>>> level.
>>>> partial modifier_keys
>>>> xkb_symbols "ac11_switch" {
>>>>   key <AC11> {
>>>>     type[Group1]="ONE_LEVEL",
>>>>     symbols[Group1] = [ ISO_Level3_Shift ]
>>>>   };
>>>> };
>>>
>>> If tapped it sends an F14 signal (which I use in Emacs to 
>>> insert
>>> math
>>> symbols in cdlatex).
>>
>> I guess I still don't fully understand your XKB
>> configuration. Having
>> access to the complete XKB configuration on your X server would 
>> be a
>> great help to that end.
>>
>> Would you please run:
>>
>>   xkbcomp -xkb $DISPLAY
>>
>> and attach each generated *.xkb file?