Can you attach the result of xkbcomp :0 -xkb out.xkb?

Also, what is output in xev utility when you press rwin and menu?

I received this error when running xkbcomp:

$ xkbcomp :0 -xkb out.xkb
Warning:          Could not load keyboard geometry for :0
                  BadAlloc (insufficient resources for operation)
                  Resulting keymap file will not describe geometry

The resulting out.xkb is attached.

Also attached is out.xev, the output of xev when rwin and menu are
pressed (in that order).

This is BTW a fresh install.  I had initially set compose:menu in
xorg.conf, and changed it after one session to compose:rwin.  Not sure
if that could affect anything.

> $ xkbcomp :0 -xkb out.xkb
> Warning:          Could not load keyboard geometry for :0
>                   BadAlloc (insufficient resources for operation)
>                   Resulting keymap file will not describe geometry
From my experience, that message indicates there was problem initializing XKB internal structures. If so, it is really problem in XKB code.

> --- Comment #2 from Chris King <colanderman@gmail.com> 2010-11-20 19:45:34 PST ---
> The resulting out.xkb is attached.
> 
Did you forget the attachment?

Created attachment 40450 [details]
xkbcomp :0 -xkb out.xkb

Created attachment 40451 [details]
xev output, rwin, then menu

(In reply to comment #4)
> Did you forget the attachment?

My fault, I thought attaching them in an e-mail reply would work.  They are attached to the bug report now.

(In reply to comment #5)
> Created an attachment (id=40450) [details]
> xkbcomp :0 -xkb out.xkb

That says you're using compose:menu.  Care to attach the X log?

Created attachment 40453 [details]
xorg.conf showing compose:rwin in use

I have rebooted several times since switching to compose:rwin (kernel recompiles etc.).

Created attachment 40454 [details]
Xorg log showing compose:menu

This bug still exists in the xorg 7.5+7 package.  Any word on this
since last year?

I do not understand! From your logs

(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc104"
(**) Option "xkb_layout" "us"
(**) Option "xkb_options" "ctrl:nocaps,compose:menu"

it is clear you are using compose:menu in your config. Why are you complaining about compose:rwin?

Sorry for delay with the bug.

On Tue, Dec 20, 2011 at 6:09 PM,  <bugzilla-daemon@freedesktop.org> wrote:
> I do not understand! From your logs
>
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "pc104"
> (**) Option "xkb_layout" "us"
> (**) Option "xkb_options" "ctrl:nocaps,compose:menu"
>
> it is clear you are using compose:menu in your config. Why are you complaining
> about compose:rwin?

Because in my /etc/X11/xorg.conf, I have written:

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "kbd"
        Option          "XkbRules"      "xorg"
        Option          "XkbModel"      "pc104"
        Option          "XkbLayout"     "us"
        Option          "XkbOptions"    "ctrl:nocaps,compose:rwin"
EndSection

Is there something amiss here, that causes ctrl:nocaps to work but
compose:rwin not to?

(In reply to comment #13)
> Because in my /etc/X11/xorg.conf, I have written:
> 
> Section "InputDevice"
>         Identifier      "Generic Keyboard"
>         Driver          "kbd"
>         Option          "XkbRules"      "xorg"
>         Option          "XkbModel"      "pc104"
>         Option          "XkbLayout"     "us"
>         Option          "XkbOptions"    "ctrl:nocaps,compose:rwin"
> EndSection
> 
> Is there something amiss here, that causes ctrl:nocaps to work but
> compose:rwin not to?

Your log says:
(II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.

and:
(II) config/udev: Adding input device HID 04d9:1203 (/dev/input/event8)
(**) HID 04d9:1203: Applying InputClass "evdev keyboard catchall"
(**) HID 04d9:1203: always reports core events
(**) HID 04d9:1203: Device: "/dev/input/event8"
(II) HID 04d9:1203: Found keys
(II) HID 04d9:1203: Configuring as keyboard
(II) XINPUT: Adding extended input device "HID 04d9:1203" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc104"
(**) Option "xkb_layout" "us"
(**) Option "xkb_options" "ctrl:nocaps,compose:menu"

which means that xorg.conf entries for the obsolete kbd driver are
ignored as your server is using the modern evdev driver as configured
by udev & xorg.conf snippets.   See documentation for example at:

https://fedoraproject.org/wiki/Input_device_configuration
http://wiki.debian.org/XStrikeForce/InputHotplugGuide

On Tue, Dec 20, 2011 at 6:29 PM,  <bugzilla-daemon@freedesktop.org> wrote:
> which means that xorg.conf entries for the obsolete kbd driver are
> ignored as your server is using the modern evdev driver as configured
> by udev & xorg.conf snippets.   See documentation for example at:
>
> https://fedoraproject.org/wiki/Input_device_configuration
> http://wiki.debian.org/XStrikeForce/InputHotplugGuide

Ah thanks, those helped.  It was strange that kbd partially worked.
There's no indication in kbd(4) that it is obsolete; hence I felt I
could continue using it from my old configuration.