[Xcb] [Bug 27945] With xorg-server-1.7.6, Xnest doesn't run, failing in xcb "assertion"

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue May 4 00:07:44 PDT 2010


--- Comment #2 from katabami at lavabit.com 2010-05-04 00:07:43 PDT ---
Both Xnest and the real server are 1.7.6. Xnest abort happens

Program received signal SIGABRT, Aborted.
0x00007ffff4efdc45 in raise () from /lib/libc.so.6
(gdb) bt
#0  0x00007ffff4efdc45 in raise () from /lib/libc.so.6
#1  0x00007ffff4eff811 in abort () from /lib/libc.so.6
#2  0x00007ffff4ef6d79 in __assert_fail () from /lib/libc.so.6
#3  0x00007ffff78e2653 in _XReply () from /usr/lib/libX11.so.6
#4  0x00007ffff78bf80f in XGetKeyboardControl () from /usr/lib/libX11.so.6
#5  0x000000000042081e in xnestKeyboardProc (pDev=0x9be200, onoff=0)
    at Keyboard.c:189
#6  0x000000000055aae0 in ActivateDevice (dev=0x9be200, sendevent=1 '\001')
    at devices.c:470
#7  0x000000000055b005 in InitAndStartDevices () at devices.c:640
#8  0x00000000005a803b in main (argc=2, argv=0x7fffffffe318, 
    envp=0x7fffffffe330) at main.c:258

I use my own hacked keyboard. (That's why I use Xnest, instead of
Xephyr which doesn't accept keyboard configuration.) The real server
works ok with it, but when I invoke Xnest, the real server startx
> Warning:          Duplicate shape name ""
>                   Using last definition
(repeated many times)
> Warning:          Multiple doodads named ""
>                   Using first definition
(repeated many times)
Errors from xkbcomp are not fatal to the X server

setxkbmap and xkbcomp are new, too. My keyboard driver is evdev, and
in Gentoo Linux which I use, evdev configuration is passed from
hal. Upgrading of xorg-server is done in Gentoo way, so I'm not going
my own cowboy way.

Sorry if my bug report is clumsy, I'm not skilled. (I though it's
better go upstream directly for such delicate issue, rather than

Thanks a lot for your kind reply.

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

More information about the Xcb mailing list