Following upgrade of sys-apps/kbd (1.12 to 1.13-r1), I am receiving a warning during bootup ("KDSKBENT: Invalid arument" -- see details in Actual Results). Based on forum discussion (see URL), other users have "similar" error - I assume that to mean "same error but varying keycodes", perhaps based on differing keymap selections). The warning seems to be harmless (at least in my case), as the console remains fully functional, including UTF-8, alt-Gr. I personaly have observed no effect so far, beyond the error message during boot. Reproducible: Always Steps to Reproduce: 1. upgrade sys-apps/kbd-1.12 to sys-apps/kbd-1.13-r1 2. reboot 3. Actual Results: Console text during boot-up: * Loading key mappings ... KDSKBENT: Invalid arument Failed to bind key 0 to value 638 KDSKBENT: Invalid arument Failed to bind key 0 to value 638 (does not echo "* Setting terminal encoding to UTF-8 ...") (continues normally) Expected Results: * Loading key mappings ... * Setting terminal encoding to UTF-8 ... (continues normally) # emerge --info Portage 2.1.3.9 (default-linux/ppc/ppc32/2007.0/desktop/G4, gcc-4.1.2, glibc-2.6.1-r0, 2.6.22-gentoo-r5 ppc) ================================================================= System uname: 2.6.22-gentoo-r5 ppc 7400, altivec supported Timestamp of tree: Fri, 19 Oct 2007 06:50:01 +0000 ccache version 2.4 [enabled] app-shells/bash: 3.2_p17 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r5 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61-r1 sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.21 ACCEPT_KEYWORDS="ppc" CBUILD="powerpc-unknown-linux-gnu" CFLAGS="-O2 -mtune=7400 -mcpu=7400 -maltivec -mabi=altivec -pipe" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/share/X11/xkb" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O2 -mtune=7400 -mcpu=7400 -maltivec -mabi=altivec -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="http://gentoo.osuosl.org/ ftp://ftp.gtlib.gatech.edu/pub/gentoo http://open-systems.ufl.edu/mirrors/gentoo" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="en_US" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X a52 alsa altivec bash-completion berkdb bitmap-fonts cairo cdr cli cracklib crypt cups dbus dri dvd dvdr dvdread encode esd fam firefox fortran gdbm gif gnome gpm gstreamer gtk hal iconv imagemagick java jpeg logrotate mad mp3 mpeg mudflap ncurses nls nptl nptlonly nsplugin ogg opengl pam pcre pdf perl png ppc python quicktime readline reflection reiserfs samba sdl session spl ssl svg threads tiff truetype truetype-fonts type1-fonts unicode userlocales vorbis xml xorg xv zlib" ALSA_CARDS="powermac" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LINGUAS="en_US" USERLAND="GNU" VIDEO_CARDS="r128" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY
I'm at work right now, but I tested this the other day after poking around on the forums. The error lies on line 59 of /etc/init.d/keymaps. Commenting it out stops the error, but I'm no experts at init scripts, so I have no idea what it does. From the looks of it though it converts the current keymap to unicode Also, changing keymaps helps, but then all the keys are mapped differently and you cant login.
(In reply to comment #1) > ... The error lies on line 59 of /etc/init.d/keymaps. ... Line 59 is blank in the file I am using: 53 # Set terminal encoding to either ASCII or UNICODE. 54 # See utf-8(7) for more information. 55 local termencoding="" termmsg="" 56 if [[ ${UNICODE} == "yes" ]] ; then 57 local dumpkey_opts="" 58 [[ -n ${DUMPKEYS_CHARSET} ]] && dumpkey_opts="-c ${DUMPKEYS_CHARSET}" 59 60 dumpkeys ${dumpkey_opts} | loadkeys --unicode 61 termencoding=$'\033%G' 62 termmsg="UTF-8"
The problem is in kbd 1.13 package. For some reason dumpkays dumps also character 0 for 68k and powerpc and this is not handled by loadkeys. It seems this is alread y corrected in the 1.13wip (Same url as for 1.13)
Created attachment 139368 [details, diff] kbd 1.13 -> 1.13wip diff
Created attachment 140968 [details] Proposed ebuild update based on kbd-1.13-wip Attached a PROPOSED ebuild update based on the patch provided earlier. The update simply applies the patch. I emerged this from a local overlay on a PowerMac G4 and it resolves the error and appears to be stable.
I can confirm this patch solves the problem. In addition I am able again to compose accents in OOo, which was broken without this patch. This should go into the tree urgently. Please, anybody? I am also on a G4 machine.
I've also tested the patch and I confirm that it solves the problem.
1.14.1 in the tree
After adding kbd-1.14.1-r1 has unmasked, I've found it was creating another bug. See bug #232072. It's very easy to fix it yourself but I think it's better to know it before merging the package.
This problem is occurring again in sys-apps/kbd-1.15.1 with USE="nls" on a us keyboard setting. I'm on ~x86... reopen?
no. search bugzilla and/or upgrade openrc. either way, new issue -> new bug.
