Bug#364489: marked as done (xkbcomp looks for files in the wrong directory)
Your message dated Mon, 24 Apr 2006 12:27:17 +0200
with message-id <20060424102717.GA14065@country.grep.be>
and subject line Bug#364489: xkbcomp looks for files in the wrong directory
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
(filing this on xbase-clients rather than xorg-xserver-core, since
according to strace, xkbcomp is the thing that actually looks at the
Since the move to X11R7, I had issues with my laptop's keyboard (an
Apple PowerBook). Being lazy (and not in the vicinity of another system
to fix the laptop, should I fuck up the keyboard), I didn't check it out
My X keyboard definition looks like this:
Identifier "Generic Keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "macintosh"
Option "XkbLayout" "wouter"
Which should mean that X would look for a keymap with the "macintosh"
geometry, and the "wouter" layout. Indeed, with previous versions of X,
and my keymap in /etc/X11/xkb/symbols/macintosh/wouter, this used to
work correctly; however, for it to work with current versions of X, it
only works if I put my modified keymap in
/usr/share/X11/xkb/symbols/wouter, rather than in
/usr/share/X11/xkb/symbols/macintosh_vndr/wouter, as I would expect.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-powerpc
Locale: LANG=nl_BE.ISO-8859-15@euro, LC_CTYPE=nl_BE.ISO-8859-15@euro (charmap=ISO-8859-15)
Versions of packages xbase-clients depends on:
ii libc6 2.3.6-7 GNU C Library: Shared libraries
ii libfontconfig1 2.3.2-5.1 generic font configuration library
ii libfreetype6 2.1.10-3 FreeType 2 font engine, shared lib
ii libfs6 2:1.0.0-3 X11 Font Services library
ii libgl1-mesa-glx [libgl1] 6.4.1-0.4 A free implementation of the OpenG
ii libice6 1:1.0.0-3 X11 Inter-Client Exchange library
ii libpng12-0 1.2.8rel-5.1 PNG library - runtime
ii libsm6 1:1.0.0-4 X11 Session Management library
ii libx11-6 2:1.0.0-6 X11 client-side library
ii libxau6 1:1.0.0-3 X11 authorisation library
ii libxaw7 1:1.0.1-5 X11 Athena Widget library
ii libxcursor1 220.127.116.11-5 X cursor management library
ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar
ii libxft2 18.104.22.168-6 FreeType-based font drawing librar
ii libxi6 1:1.0.0-5 X11 Input extension library
ii libxkbfile1 1:1.0.2-3 X11 keyboard file manipulation lib
ii libxmu6 1:1.0.1-3 X11 miscellaneous utility library
ii libxmuu1 1:1.0.1-3 X11 miscellaneous micro-utility li
ii libxrandr2 2:22.214.171.124-4 X11 RandR extension library
ii libxrender1 1:0.9.0.2-4 X Rendering Extension client libra
ii libxss1 1:1.0.1-4 X11 Screen Saver extension library
ii libxt6 1:1.0.0-4 X11 toolkit intrinsics library
ii libxtrap6 1:1.0.0-3 X11 event trapping extension libra
ii libxtst6 1:1.0.1-3 X11 Testing -- Resource extension
ii libxv1 1:1.0.1-3 X11 Video extension library
ii libxxf86dga1 2:1.0.0-3 X11 Direct Graphics Access extensi
ii libxxf86vm1 1:1.0.0-4 X11 XFree86 video mode extension l
ii x11-common 1:7.0.10 X Window System (X.Org) infrastruc
ii zlib1g 1:1.2.3-11 compression library - runtime
xbase-clients recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Apr 24, 2006 at 07:13:36AM +0100, Daniel Stone wrote:
> On Sun, Apr 23, 2006 at 11:12:34PM +0200, Wouter Verhelst wrote:
> > On Sun, Apr 23, 2006 at 08:55:59PM +0100, Daniel Stone wrote:
> > > Closing as invalid, since this is a user configuration issue.
> > Then at the very minimum this should be documented. Rather than having a
> > non-working "macintosh_vndr" directory, it should either work, or be
> > documented that it needs to be enabled somehow (by an option in
> > xorg.conf, I guess?), or be removed.
> It *is* documented. That it existed previously was not documented, but
> in the rules file.
Okay, I probably missed it, then.
> If you
> > A directory on disk with keymaps that cannot ever possibly be used is a
> > bug in my book.
> What? Which directory?
> I'm not going to bother re-closing it: if you want to keep it open, good
> luck. All I'm saying, is that you made local modifications to XKB, and
> that was what failed.
... because I didn't fix my rules file? Okay, that's as good an
explanation as any.
> Everything else works fine. Your mail shows a lack of understanding
> of XKB
Hmm, that wouldn't be impossible.
> (yes, it is hideously underdocumented), so arguing semantics about it
> probably isn't the best idea.
Good enough for me. Closing the bug.
Fun will now commence
-- Seven Of Nine, "Ashes to Ashes", stardate 53679.4
--- End Message ---