Since >sys-apps/kbd-1.5 console pt-latin1 keymap doesn't allow to type characters as 'ã,â,ê,ô,à,á' When you type that key, nothing happens. Reproducible: Always Steps to Reproduce: 1. Install >sys-apps/kbd-1.5 2. loadkeys -v pt-latin1 3. Actual Results: 'construção' becomes 'construço', e.g. Expected Results: 'construção', e.g. Keymaps directories: 1.5 version: http://www.ashtophet.org/files_bgo/kbd-1.5.tar.bz2 (WORKING) 1.5.2-r1 version: http://www.ashtophet.org/files_bgo/kbd-1.5.2-r1.tar.bz2 (NOT WORKING) Attached will be: Logs running loadkeys -v pt-latin1 with 1.5 and 1.5.2-r1. Logs running dumpkeys with 1.5 and 1.5.2-r1. Logs listing contents of 1.5 and 1.5.2-r1 installations.
Created attachment 235603 [details] loadkeys -v pt-latin1 (WORKING), using 1.5
Created attachment 235605 [details] loadkeys -v pt-latin1 (NOT WORKING, 1.5.2-r1)
Created attachment 235607 [details] dumpkeys (WORKING, 1.5)
Created attachment 235609 [details] dumpkeys (NOT WORKING, 1.5.2-r1)
Created attachment 235611 [details] paludis --contents kbd (1.5)
Created attachment 235613 [details] paludis --contents kbd (1.5.2.r1)
Created attachment 235615 [details] kbd keymap directory (1.5)
Created attachment 235617 [details] kbd keymap directory (1.5.2-r1)
It seems to be that this is a bug in detection keysym type.
$ grep masculine pt-latin1.map keycode 40 = masculine ordfeminine $ grep -m1 0x00ba ksyms.c { 0x00ba, "masculine" }, $ grep 'define.*\^ 0xf000' loadkeys.c #define U(x) ((x) ^ 0xf000) $ echo $((0x00ba)) 186 $ echo $((0x00ba ^ 0xf000)) 61626 $ grep '40, table 0 ' loadkeys_good.log keycode 40, table 0 = 186 $ grep '40, table 0 ' loadkeys_bad.log keycode 40, table 0 = 61626
If there's anything I could add or test to help, let me know. Thank you very much.
loadkeys has detected that your console is in unicode mode ... so it tries to load the keymap in this mode. Please, try the following way: $ kbd_mode -a $ loadkeys -v pt-latin1
Hi. I follow the steps with no luck (attached is loadkeys log). However if I do an kbd_mode -u _after_ loadkeys everything turns fine. My console should be in unicode mode. I don't know if I'm doing something wrong, but I'm using this settings for years and the problem only occurs when using >sys-apps/kbd-1.5. Probably relevant config files: awk '/^[^#]/' /etc/conf.d/consolefont: consolefont="sigma-general-8x16" awk '/^[#]/' /etc/rc.conf rc_interactive="YES" rc_shell=/sbin/sulogin rc_depend_strict="NO" rc_logger="YES" unicode="YES" net_fs_list="afs cifs coda davfs fuse fuse.sshfs gfs glusterfs lustre ncpfs nfs nfs4 ocfs2 shfs smbfs" rc_tty_number=12 Thank you very much.
Created attachment 237003 [details] loadkeys -v pt-latin1 (WORKING if I run kbd_mode -u after it) after kbd_mode -a, 1.5.2-r1
I just added --ascii option to prevent switching to unicode mode. This change allows not use kbd_mode before and after loadkeys. http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=commitdiff;h=000b966ae19bdb9e2d27dd8a02c83a6f282abe6d
Ok. Let's see if I'm doing things right. Installed patched sys-apps/kbd # kbd_mode # The keyboard is in Unicode (UTF-8) mode # loadkeys pt-latin1 (or loadkeys -u pt-latin1) ( no fish) # loadkeys -a pt-latin1 # loadkeys: warning: loading non-Unicode keymap on Unicode console (perhaps you want to do `kbd_mode -a'?) Loading /usr/share/keymaps/i386/qwerty/pt-latin1.map.gz (ok) Is this supposed to be this way?
(In reply to comment #16) > Is this supposed to be this way? Yes.
This is not a final fix. I will try to fix this regression in another way.
Please, test this commit: http://git.altlinux.org/people/legion/packages/kbd.git?p=kbd.git;a=commitdiff;h=b4735104164bb5b5b23f885caa5011f8506eb773
Perfect, Alexey! Tested both manually (log attached) and via gentoo init script. Thank you _very_ much for your work. Guess we can call this bug FIXED. Cheers.
Created attachment 237657 [details] loadkeys -v pt-latin1 after kbd git commit b4735104164bb5b5b23f885caa5011f8506eb773
