No keyboard previews

[Micah Cowan]

In "System" -> "Preferences" -> "Keyboard Preferences", "Layout" tab, "+Add" button (brings up the dialog)... the frame labeled "Preview" never shows the currently selected keyboard. Everytime a keyboard is selected, stderr gets "** (gnome-keyboard-properties:8918): CRITICAL **: XkbGetKeyboard failed to get keyboard from the server!"

[Daniel Stone (daniels)]

if you only revert the change to XkbWriteXKBKeymapForNames in xkbfmisc.c, does
it improve? obviously, it works fine for me on Xorg; what you're seeing is a
failure to build the keymap at all.

[Dan Winship (danw-gnome)]

> if you only revert the change to XkbWriteXKBKeymapForNames in xkbfmisc.c, does
> it improve?

No, reverting just rev 1.9 doesn't help, I have to revert both 1.9 and 1.8.

> obviously, it works fine for me on Xorg;

really? Hm... David, are there any xkb-related changes from Xorg to Xgl?

[Sylvain BERTRAND (sylvain-bertrand)]

I have the same issue, with plain(err... gentoo) X.org 7.1 with gnome 2.14.x.
server-0.xkm is corrupted then fails to be reloaded when generating the response
to xkGetKbdByName request.

[Sylvain BERTRAND (sylvain-bertrand)]

Created an attachment (id=5836)
xkm file that xkbcomp is unable to load for kbGetKbdByName response

[Davidr-novell (davidr-novell)]

(In reply to comment #2)
> really? Hm... David, are there any xkb-related changes from Xorg to Xgl?
>

Initialization code in ddx is probably a bit different but other than that it
should be the same xkb code.

[Daniel Stone (daniels)]

(In reply to comment #2)
> > if you only revert the change to XkbWriteXKBKeymapForNames in xkbfmisc.c, does
> > it improve?
>
> No, reverting just rev 1.9 doesn't help, I have to revert both 1.9 and 1.8.

okay, so it's just XkbWriteXKBKeymapForNames? this could be fun. i'll have to
get an Xgl setup going, but this won't happen until after the weekend, probably
(travel hilarity).

[Matthias Clasen (mclasen)]

FWIW, I'm seeing the same issue

** (gnome-keyboard-properties:3166): CRITICAL **: XkbGetKeyboard failed to get
keyboard from the server!

on the rawhide X server, no Xgl involved.

[Simos Xenitellis  (simosx)]

(In reply to comment #7)
> FWIW, I'm seeing the same issue
>
> ** (gnome-keyboard-properties:3166): CRITICAL **: XkbGetKeyboard failed to get
> keyboard from the server!
>
> on the rawhide X server, no Xgl involved.

AFAIK, noone maintains the xkbdata package which is the default in Xorg.

You would need to upgrade to xkeyboard-config,
http://www.freedesktop.org/wiki/Software_2fXKeyboardConfig

[Dan Winship (danw-gnome)]

We're using xkeyboard-config 0.7 in SUSE. It doesn't look like there were any
changes in 0.8 that would affect this...

[Ben-bnc (ben-bnc)]

I am seeing a similar issue here. I have a trimmend down compile of Xorg 7.1,
which reports this at startup:
    xkb_keycodes { include "xfree86+aliases(qwerty)" };
    xkb_types { include "complete" };
    xkb_compatibility { include "complete" };
    xkb_symbols { include "pc/pc(pc104)+pc/us" };
    xkb_geometry { include "pc(pc104)" };

But when I use numlockx to turn on NumLock, I get:
    xkb_types { include "%" };
    xkb_compatibility { include "%" };
    xkb_symbols { include "%" };
    xkb_geometry { include "%" };
(EE) Error loading keymap /usr/share/X11/xkb/compiled/server-0.xkm

numlockx uses XkbLockModifiers() to turn NumLock on or off.

I am not completely sure this is the same bug, but am reluctant to file a new
bug that might be marked as a duplicate of this bug.

[Kem (kem)]

We are seeing the same issue in FC6, and I've tracked down the problem to the
0e88cefbfecbff0c7dd606ce0caca840f45cbc0d and
7c44bb8c49656133eae675377edea55322d254ca commits.

I've got a fix for this locally, but my patch needs a bit of cleanup. I'll
check it in once I finish my testing. FYI, what I did was to revert those two
commits but keep the parts that removed the unused !XKB_IN_SERVER and
HAVE_CONFIG_H code paths.

[Kem (kem)]

Should be fixed in git now. If you still see problems with the latest code,
please reopen the bug.

[Micah Cowan (micahcowan)]

In "System" -> "Preferences" -> "Keyboard Preferences", "Layout" tab, "+Add" button (brings up the dialog)... the frame labeled "Preview" never shows the currently selected keyboard. Everytime a keyboard is selected, stderr gets "** (gnome-keyboard-properties:8918): CRITICAL **: XkbGetKeyboard failed to get keyboard from the server!"

[Sergey V. Udaltsov (sergey-udaltsov)]

It is not a control-center bug, it is something broken in xlib, XkbGetKeyboard returns NULL

[didier (did447-deactivatedaccount)]

Right and it's fixed upstream

[Sergey V. Udaltsov (sergey-udaltsov)]

If you don't mind, could you please give a hint where was breakage - because people keep asking me (since I am g-k-p maintainer) and I would like to have an answer...

[Sebastien Bacher (seb128)]

Thank you Sergey and didier

[Sebastien Bacher (seb128)]

Patch used by the current fedora package. The upstream commit corresponding seems to be http://lists.freedesktop.org/archives/xorg-commit/2006-July/008488.html

[Sergey V. Udaltsov (sergey-udaltsov)]

Is this patch going to be applied in eft? The huge empty dialog in gnome-keyboard-properties looks very ugly.

[Sebastien Bacher (seb128)]

no, edgy is stable now and that patch is not trivial so probably not a candidate for a stable update :/

[Sergey V. Udaltsov (sergey-udaltsov)]

But this is a clear bug and regression! g-k-p is broken as it is. Same about g-k-i.

[Corsaire01 (stephane-tranchemer)]

Same here with Ubuntu 6.10 final, I get the list of the available keyboards but no image to show the key placements.

system is 6.10 x86_64, upgraded from a 6.06 with the 'gksu' command, worked on 6.06, forced to reinstall the gnome-control-center package to be sure, same result.

[Sergey V. Udaltsov (sergey-udaltsov)]

It is really ugly - especally two sets of buttons, you see?

[Gert Kulyk (gkulyk)]

I've build a fixed version for my own use (using a slightly-modified, that is a one that also changes Makefile.in, fedora patch), a .diff.gz file attached for people who do want to play around with it.

Sebastien: Please tell me, if such a changed version could enter edgy-updates (after a while in edgy-proposed). The patch applies cleanly, no problems encountered (although the source tells that it was build today, I'm using a patched version for a few days now). The bug is really annoying.

Regards,

Gert

[Gert Kulyk (gkulyk)]

PS: Here's a screenshot showing the keyboard-layout with the modified package :-)

[Sebastien Bacher (seb128)]

not a control-center bug

[Sebastien Bacher (seb128)]

Sergey, it's clear that the dialog is ugly and bugged without that patch, still I don't know org enough to be wanting to push that patch to a stable serie. If somebody wants to do that, feel free

Gert, you can read https://wiki.ubuntu.com/StableReleaseUpdates about the procedure to get that update to edgy

[TomasHnyk (sup)]

I just tried Herd 1 (solely because of this because I wanted to make a keyboard screenshot) and the bug is still present. Is it supposed to be like that?

[Octavio Alvarez (alvarezp)]

It goes beyound Ubuntu not showing keyboard previews and looking ugly. There are other applications that depend on XkbGetKeyboard. In my case, it's Superkb. This application doesn't run at all in Ubuntu 6.10 because of the bug. It worked in Ubuntu 6.06 LTS.

I kindly ask for this bugfix to get pushed to mainstream.

[Martin Pool (mbp)]

Just confirming this is still broken in edgy.

[Áron Sisak (asisak)]

Even worse, seems to be still broken in feisty as well.

[Sebastien Bacher (seb128)]

Fixed with that upload:

 xorg-server (1:1.1.1-0ubuntu13) feisty; urgency=low
 .
   * 19_revert_xkb_change_breaking_XkbGetKeyboard.patch:
     - patch from fedora (with extra Makefile.in change), revert change that
       broke XkbGetKeyboard() (Ubuntu: #58083)
   * 37_Fix-__glXDRIbindTexImage-for-32-bpp-on-big-endian-platforms.diff:
     - upstream patch copied from the Debian package, fix blue screen with
       compiz on ppc (Ubuntu: #58373)

[Sergey V. Udaltsov (sergey-udaltsov)]

Any chance to get it in edgy? Feisty is a bit long way to go till release...

[Sebastien Bacher (seb128)]

The patch is not trivial and I'm not an xorg hacker, I'm not comfortable to push it to stable. Maybe after some testing. Sergey, I can build a non-official deb for edgy if you want though, it would permit you to get a working version to look at the gnome-control-center bugs, what architecture do you use?

[Sergey V. Udaltsov (sergey-udaltsov)]

I would love debs for x86 (not 64) and ppc, if possible. Thanks a bunch.
But really, it would make sense to put it into testing, I think edgy users would love to get this one fixed as well.

[Octavio Alvarez (alvarezp)]

We would gladly test it in Edgy and report any weirdness. I'm interested in sending the patch to stable.

(Yeah, it's not trivial, but it is a "revert to a previous known-to-be-working state" patch.)

[Sergey V. Udaltsov (sergey-udaltsov)]

Sebastien, is there any progress with debs for Edgy? I have so many bugs and patches in gnome bugzilla regarding this preview...;)

[VladAtNYC (vladatnyc)]

Does anyone know if there is a package that i can install that will fix this issue, it is rather annoying and i really need to use the keyboard layout view.

[Sebastien Bacher (seb128)]

Packages for edgy i386 are available on http://people.ubuntu.com/~seb128/xorg-server-edgy-update, you can download them and install with "sudo dpkg -i *.deb"

[TomasHnyk (sup)]

thanks, works like a charm (I will report if anything breaks in the future, but after one hour of running all seems to be just fine)

[Sergey V. Udaltsov (sergey-udaltsov)]

Sebastien, thanks, this is really great. And it works. Would you please be able to build the same stuff for ppc please?

[Octavio Alvarez (alvarezp)]

Sebastien, it works perfectly. Thanks a lot. I'll post any breakage.

[ricardisimo (ricardisimo)]

Sorry for the nũb question, but is it "sudo apt-get [each package listed there]" followed by "sudo dpkg -i [one-by-one]"? Or am I just finding one that is appropriate for my system? Thanks so much in advance. You guys do great work.

[Octavio Alvarez (alvarezp)]

You should just download the packages you have installed (you might check with dpkg -l) and issue sudo dpkg -i *.deb.

[ricardisimo (ricardisimo)]

Thank you Octavio. This is the closest thing I have listed: ii xserver-xorg-i 1.1.0-0ubuntu1 X.Org X server -- keyboard input driver
Is it safe to assume I'm going with "core" rather than "dev"? I'm on Edgy, if that helps at all. Thanks again.

[Tony Lewis (tonylewis)]

There's another solution available, with a less drastic fix: http://ubuntuforums.org/showthread.php?t=309424

In short, this distilled down to removing the existing /usr/share/X11/xkb (e.g. renaming it to .xkb-broken or something) and linking /usr/share/X11/xkb to /etc/X11/xkb:

    cd /usr/share/X11
    sudo mv xkb .xkb-broken
    sudo ln -s ../../../etc/X11/xkb/

Further investigation seems to indicate that the xkb-data-legacy package will provide everything we need, but that package has dependencies that will regress your system badly.

But I see the fact that we can't fix it in the distro proper as a major setback. Is it considered low risk enough to include something like this symlink in the xkb-data package, and thus fix it within the distro?

That sounds better to me than Seb having to track these packages, and users having to manually install them for the life of Edgy.

[Sebastien Bacher (seb128)]

Tony, please don't advice people to do manual changes like that, that sort of hacks can break upgrades months later and then people are confused and blame the distribution for things they broke themself and not good for anybody.

That can be fixed and is fixed to feisty. Preview from keymaps is a small feature why people make so much noise about it? The patch is non trivial and we have no xorg maintainer at the moment which explains why nobody is wanting to take the responsability to do that change on a stable distribution

[Sergey V. Udaltsov (sergey-udaltsov)]

This is really interesting though. That hack implies that xkb-data-legacy provides everything X need to work properly. Does this mean xkeyboard-config package is broken somehow or what?
(and I respectfully disagree with Sebastian - it is still 2 months till feisty, and this bug is visible to _everyone_ trying to add new layout to the keyboard configuration).

[Tony Lewis (tonylewis)]

Sebastian, it's more than just "preview from keymaps", whatever that is. After upgrading to Edgy, I lost my multimedia keys. I went to reassign my keyboard mapping from the pull down in the Kubuntu Systems Settings, and there were *no* keyboards to choose from, therefore no graphical way I could see to get my multimedia keys back.

Without being precious about it, IMO, this is a significant inconvenience.

If this is affecting everyone, then the small change to the packages as above might be worth it. If it's just me or a subset of people, then I don't understand what went wrong in my upgrade process (OK, so I didn't use update-manager)

[Octavio Alvarez (alvarezp)]

> Preview from keymaps is a small feature why people make so much noise about it?

It goes beyound Ubuntu not showing keyboard previews and looking ugly. -- I can't use or develop my graphical keyboard launcher, so I had to change the way I launch applications because of this bug.

BTW, I have seen *no* negative side-effects from the packages you provided on you link above, two computers here have it installed, both are x86.

[Octavio Alvarez (alvarezp)]

Sebastien, now that Ubuntu released a new security fix numbered 0ubuntu12.2, the packages you kindly provided for testing are constantly being targeted for upgrading by Update Manager. The ones from stable are *not* fixed yet.

I can affirm I have had no issues whatsoever during all this time, using the packages you provided.

[Sebastien Bacher (seb128)]

edgy is not a LTS version and new stable will be available next will, it's not likely we will apply the change to edgy now

[Daniel Saunders (daniel-saunders)]

This has broken for me since upgrading from 7.10 to 8.04.

[Sebastien Bacher (seb128)]

don't comment on a closed bug only because you have a similar issue