Discussion:
[SunRay-Users] XKB extension with Gnome on Ubuntu
Damiano ALBANI
2005-09-20 20:52:14 UTC
Permalink
Hello,

I have an SRSS 3.1 server on Linux x86/Ubuntu. I've
tried to enable XKB (with utxconfig) but when I logon
in a GNOME session, there's this error message :

-------
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation

X server version data:
The X.Org Foundation
60802000

If you report this situation as a bug, please include:
- The result of <b>xprop -root | grep XKB</b>
- The result of <b>gconftool-2 -R
/desktop/gnome/peripherals/keyboard/kbd</b>
-------

Which results are :

***@grenouille:~$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "sun", "type6_usb",
"us", "", ""
_XKB_RULES_NAMES(STRING) = "sun", "type6_usb", "us",
"", ""
***@grenouille:~$ gconftool-2 -R
/desktop/gnome/peripherals/keyboard/kbd
layouts = [us]
model = generic
overrideSettings = false
options = []

And then, for example, when I try to run 'xkbwatch' :
Fatal Error: Server doesn't support a compatible
XKB

What is strange is that if I am in a 'rescue' xterm
session (as chosen from GDM), xkbwatch runs without a
hitch...

Any idea ? It seems to come from GNOME apparently.

Cheers,
--
Damiano ALBANI







___________________________________________________________________________
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
Simon Annear
2005-09-23 02:26:50 UTC
Permalink
Hi all

Wondering if anyone has run into a similar problem

We're playing with Solaris 10 with srss 3.1 (same problem with both beta and newly released 3.1)

Home directories are automounted from central nfs server

When a user logs in, xscreensaver dtappgather start consuming heaps of cpu (30% each). Has only just started happening

I'm sure that the cause of the problem was either applying the latest patches (smpatch update) or someone changing permissions on our home directories.

Trussing xscreensaver shows it trying to access /home/user/.xscreensaver

Current home directory permissions are 750 and ownership of user:staff

I can resolve the problem by chmod user's home directories to 755

Has anyone else run into this problem ?

Simon

Loading...