> On Mar 25, 2024, at 6:35 PM, RVP <r...@sdf.org> wrote: > > On Mon, 25 Mar 2024, Rob Whitlock wrote: > >> Is there some trick to enabling this functionality >> > > Yes. Try again after applying this patch (and restarting X). > > ``` > --- usr/X11R7/lib/X11/XKeysymDB.orig 2024-03-18 22:47:19.000000000 +0000 > +++ usr/X11R7/lib/X11/XKeysymDB 2024-03-25 21:36:39.970222356 +0000 > @@ -370,6 +370,9 @@ > XF86_ClearGrab :1008FE21 > XF86_Next_VMode :1008FE22 > XF86_Prev_VMode :1008FE23 > +XF86LogWindowTree :1008FE24 > +XF86LogGrabInfo :1008FE25 > + > > usldead_acute :100000A8 > usldead_grave :100000A9 > ``` > > You could also just supply the key-sequence for this directly: > > ``` > $ xdotool key Ctrl+Alt+F11 > ```
This did not work. It just printed "Failed to switch from vt05 to vt11: Invalid argument" in /var/log/Xorg.0.log. >> or should I file a problem report? >> > > Yes, with: > > ``` > diff -urN a/xsrc/external/mit/libX11/dist/src/XKeysymDB > b/xsrc/external/mit/libX11/dist/src/XKeysymDB > --- a/xsrc/external/mit/libX11/dist/src/XKeysymDB 2010-11-28 > 07:34:33.000000000 +0000 > +++ b/xsrc/external/mit/libX11/dist/src/XKeysymDB 2024-03-25 > 21:36:39.970222356 +0000 > @@ -370,6 +370,9 @@ > XF86_ClearGrab :1008FE21 > XF86_Next_VMode :1008FE22 > XF86_Prev_VMode :1008FE23 > +XF86LogWindowTree :1008FE24 > +XF86LogGrabInfo :1008FE25 > + > > usldead_acute :100000A8 > usldead_grave :100000A9 > ``` PR submitted: https://gnats.netbsd.org/58153 > Don't ask me why all the other keysyms just above have the extra > `_'. Going by the dates on that XKeysymDB file, it's rather old, > and things may have changed since then. I also can't find that file > in the tarballs in: https://www.x.org/releases/individual/lib/, but, > I didn't search very hard--you should ask on the tech-x11 ML. > > -RVP
