Bugzilla – Full Text Bug Listing
|Summary:||Fix xkbcomp errors when XKB is activated|
|Product:||ThinLinc||Reporter:||Peter Åstrand <firstname.lastname@example.org>|
|Component:||VNC||Assignee:||Pierre Ossman <email@example.com>|
|Status:||CLOSED FIXED||QA Contact:||Bugzilla mail exporter <firstname.lastname@example.org>|
|Bug Depends on:|
This bug is moved from comment #45 on bug 2048. Although full XKB support is handled on bug 3074, it is occasionally useful to activate XKB with our current Xvnc. This can be done by adding +kb to xserver_args. From bug 2048: The plan for 3.0.0 is that we should have XKB disabled, but still ship the XKB support files, so that it can be turned on. However, currently, we are shipping a symlink: /opt/thinlinc/share/X11/xkb/xkbcomp -> /usr/bin/xkbcomp I believe this is wrong; the link should be pointing to /opt/thinlinc/bin/xkbcomp, if it should exist at all. Additionally, I'll get an error message: The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Cannot open "/opt/thinlinc/share/X11/xkb/compiled/server-2.xkm" to write keyboard description > Exiting (EE) Error compiling keymap (server-2) (EE) XKB: Couldn't compile keymap Need to solve this, hopefully cleaner than creating that directory world-writable.
I'm not seeing the xkbcomp errors on RHEL6, but the symlink should perhaps still be changed. Or, we should stop shipping xkbcomp.
This got fixed as part of bug 3074. The symlink is no longer present (or needed) in newer version of xkeyboard-config. And there is no tempfile being produced anymore.