Control: forcemerge 953032 994036 Now, due to the comments below, these are the same bug.
Note that in my case, this doesn't fill the logs, because I execute xkbcomp just once just after starting X (but there may be good reasons to execute it much more often). On 2021-09-13 02:17:11 +0200, Vincent Lefevre wrote: > Control: reassign -1 x11-xkb-utils 7.7+5 > Control: retitle -1 x11-xkb-utils: xkbcomp gives internal errors on unknown > keysyms (e.g. some XF86* with xkb-data 2.33-1) > Control: notforwarded -1 > Control: tags -1 fixed-upstream > > On 2021-09-10 19:08:59 +0200, Vincent Lefevre wrote: > > This is apparently an upstream bug (which I have just reported), > > introduced in 2.33, as some commit added these unknown keysyms. > > Upstream regards this as a bug in xkbcomp, which has been fixed in > xkbcomp 1.4.4 (the errors are downgraded to warnings, which is OK > since one can disable warnings, and this is what I currently do, > except for testing). > > Note: x11-xkb-utils 7.7+5 (the current version in unstable) has > xkbcomp 1.4.3 only. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
