Bug#860582: R: Re: Bug#860582: Nokia N900 keyboard support in console
Dear Mr. Zinoviev, >Can you send: > >1. A sample command line for ckbcomp. > >2. The output ckbcomp generates. > I call setupcon -v, and that invokes ckbcomp. With the version of console-setup which is included in the Jessie standard distribution, the command ends up complaining about PC_FN_LEVEL2 not been recognised. I installed the console-setup version from Sid, which has PC_FN_LEVEL2 hardcoded, and now it is not complaining anymore. So now I cannot reproduce the buggy behaviour. In any case, it is well described at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789816: It is generating a few "Unknown key type PC_FN_LEVEL2" lines and the cursor keys are not mapped correctly for some keyboards variations. >I think it is impossible to base the behaviour of ckbcomp on the >contents of the type file. The actual semantics of the types is >undocumented and I think some details are unknown even to X developers. > >Fortunately, this is not necessary because the type files define only a >few types and it is not difficult to hardcode the proper behaviour in >ckbcomp. > This is indeed what has been done with PC_FN_LEVEL2, so that this workaround actually works. But in this way it is impossible to define custom types. But yes, if it is impossible to let ckbcomp behave accordingly to what is stated in the type file, then this workaround is the only possible solution. And I admit that probably there is no practical need for the types to be customisable, so doing a huge work to modify ckbcomp would be not worth it. In conclusion, based on your reply, I think it be better to close this bug report without doing anything. Thank you and my best regards, Enrico Menotti
Bug#860582: Nokia N900 keyboard support in console
On Wed, Apr 19, 2017 at 12:24:17AM +0200, Enrico Menotti wrote: > > I am experimenting with Debian on a Nokia N900 (RX-51). I > debootstrapped a Jessie file system. When configuring the keyboard, I > found an issue. Namely, the symbols file uses a custom type called > PC_FN_LEVEL2; however, when setupcon is called, and from there ckbcomp > is invoked, this type is not recognised. Can you send: 1. A sample command line for ckbcomp. 2. The output ckbcomp generates. > My conclusion is that the problem is ckbcomp not reading the type file > indicated in the rule file, and that should be fixed, instead of > hardcoding the custom type into ckbcomp. I think it is impossible to base the behaviour of ckbcomp on the contents of the type file. The actual semantics of the types is undocumented and I think some details are unknown even to X developers. Fortunately, this is not necessary because the type files define only a few types and it is not difficult to hardcode the proper behaviour in ckbcomp. Anton Zinoviev
Bug#860582: Nokia N900 keyboard support in console
Package: console-setup Dear Sirs, I am experimenting with Debian on a Nokia N900 (RX-51). I debootstrapped a Jessie file system. When configuring the keyboard, I found an issue. Namely, the symbols file uses a custom type called PC_FN_LEVEL2; however, when setupcon is called, and from there ckbcomp is invoked, this type is not recognised. There is a fix on the version of console-setup which is available in the Sid repository. The bug report is found at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789816 However, I believe this bug is not fixed in the proper way. Let me explain. 1. The type is already defined in /usr/share/X11/xkb/types/nokia2. This type file is correctly referenced in /usr/share/X11/xkb/rules/xorg (line 1018/1225) (although I found no trace of Nokia models in xorg.lst and xorg.xml) 3. Based on my investigations, I believe the rules file is read by cbkcomp, but the types file is not4. The fix found at https://anonscm.debian.org/cgit/d-i/console-setup.git/commit/?id=f41adb653e666cefe15af02fdbf5bb56b11677df "hardcodes" the PC_FN_LEVEL2 type into ckbcomp My conclusion is that the problem is ckbcomp not reading the type file indicated in the rule file, and that should be fixed, instead of hardcoding the custom type into ckbcomp. Best regards, Enrico Menotti
