server-$DISPLAY.xkm no longer written?

[Stefan Dirsch]

On Fri, Aug 04, 2006 at 02:28:17PM +0300, Daniel Stone wrote:
> On Fri, Aug 04, 2006 at 01:14:47PM +0200, Stefan Dirsch wrote:
> > On Fri, Aug 04, 2006 at 01:51:31PM +0300, Daniel Stone wrote:
> > > On Fri, Aug 04, 2006 at 01:51:07PM +0300, Daniel Stone wrote:
> > > > On Fri, Aug 04, 2006 at 12:40:55PM +0200, Stefan Dirsch wrote:
> > > > > On Fri, Aug 04, 2006 at 11:06:44AM +0300, Daniel Stone wrote:
> > > > > > On Fri, Aug 04, 2006 at 09:44:29AM +0200, Stefan Dirsch wrote:
> > > > > > > I'm using xorg-server 1.1.99.3 and noticed that server-0.xkm is no
> > > > > > > longer written. When trying to load a keyboard layout, which does
> > > > > > > *not* exist I see
> > > > > > > 
> > > > > > >   (EE) Error loading keymap /var/lib/xkb/compiled/server-0.xkm
> > > > > > > 
> > > > > > > in the Xserver logfile although I did specify
> > > > > > > '--with-xkb-output=/var/lib/xkb/compiled' for building the Xserver.
> > > > > > > and /var/lib/xkb/compiled directory does exist. Anyone who can
> > > > > > > reproduce this issue?
> > [...]
> > > Sorry, that should be:
> > > setxkbmap -layout de -print | xkbcomp - :0
> > 
> > Thanks. But this of course will not work with an invalid keyboard map.
> > 
> > # setxkbmap -layout asdf -print | xkbcomp - :0 2>&1
> > Error:            Can't find file "asdf" for symbols include
> >                   Exiting
> >                   Abandoning symbols file "(null)"
> > Error:            success in unknown
> >                   Couldn't write keyboard description to :0
> > 
> > It works well with a valid map though:
> > 
> > # setxkbmap -layout de -print
> > Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> >                   Ignoring extra symbols
> > Warning:          No symbols defined for <SYRQ> (keycode 92)
> > Warning:          No symbols defined for <BRK> (keycode 114)
> > 
> > My initial question has been, why the Xserver no longer uses the
> > compiled dir. Or is this a misleading error message?
> 
> Oh, sorry, I see what you mean.  Since the server forks xkbcomp, the
> only way it tells success from failure is the existence or not of
> server-%d.xkm.  So that message is just a generic 'dang, xkbcomp
> failed'.

Ok. So it's simply misleading. Especially, because this file also
doesn't exist (I'm not sure whether it is created when the Xerver
calls xkbcomp and immediately removed after xkbcomp has finished),
when xkbcomp succeeds.

> Yes, this sucks.  #6143 (and, more generally, #6141).

Well, I'm not sure if anyone besides you understand these bugreports.
But since you are both assignee and reporter this shouldn't hurt that
much. ;-)

Best regards,
Stefan

Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.)   SUSE LINUX Products GmbH
Tel: 0911-740 53 0            Maxfeldstraße 5
FAX: 0911-740 53 479          D-90409 Nürnberg
http://www.suse.de            Germany 
------------------------------------------------------