Linux console tools development discussion
 help / color / mirror / Atom feed
From: Lars Wendler <>
Subject: [kbd] >=kbd-2.0.0 doesn't load keymaps on sparc
Date: Tue, 22 Apr 2014 19:26:36 +0200
Message-ID: <20140422192636.4988c86e@shanghai.paradoxon.rec> (raw)

[-- Attachment #1: Type: text/plain, Size: 1804 bytes --]

Hello dear list readers,

it seems like >=kbd-2.0.0 fails to load keymaps on my sparc machine
which is a SunFire V240 running Gentoo Linux. Same kbd versions on x86
Gentoo machines are working fine so does kbd-1.15.5 on sparc.

This is what I get with kbd-1.15.5:

# loadkeys -V ; loadkeys -v de-latin1-nodeadkeys | egrep
"^Load|^Changed" loadkeys from kbd 1.15.5
Loading /usr/share/keymaps/i386/qwertz/
Changed 975 keys and 26 strings.
Loaded 0 compose definitions.

As you can see, keys were changed and my keyboard (Sun Type 6 USB) with
german layout has the correct keys assigned.

This is what I get with >=sys-apps/kbd-2.0.0 instead:

# loadkeys -V ; loadkeys -v de-latin1-nodeadkeys | egrep
"^Load|^Changed" loadkeys from kbd 2.0.1
Loading /usr/share/keymaps/i386/qwertz/
switching to
switching to qwertz-layout
switching to compose
switching to linux-with-alt-and-altgr
switching to linux-keys-bare
switching to
switching to compose.latin1

Changed 0 keys and 26 strings
Loaded 158 compose definitions

And still wrong keyboard layout as indicated by the output "Changed 0
keys". (On a sidenote, it seems like loadkeys from >=kbd-2.0.0 prints
verbose messages to stderr and not stdout like kbd-1.15* did.)

I have no idea how to debug this especially since loadkeys doesn't
print any kind of warning or error.

More detailed information about the sparc machine's toolchain etc. can
be obtained from the Gentoo bug I opened at [1] in case that matters.

Please CC me on replies as I am not subscribes to this list.


Kind regards
Lars Wendler
Gentoo package maintainer
GPG: 4DD8 C47C CDFA 5295 E1A6 3FC8 F696 74AB 981C A6FC

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

                 reply	other threads:[~2014-04-22 17:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140422192636.4988c86e@shanghai.paradoxon.rec \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux console tools development discussion

This inbox may be cloned and mirrored by anyone:

	git clone --mirror kbd/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kbd kbd/ \
	public-inbox-index kbd

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone