On Dec 2, 2007 11:48 AM, Rachel Greenham <email@hidden> wrote:
Keyboard worked fine in the XDMCP login screen, but once logged in
produces gibberish. While all mouse activity worked perfectly, and I
could interact with applications on the remote end with no problem as
long as it was using the mouse, the keyboard produces utter gibberish,
it's not even close. typing "utter gibberish" gets
"dww<backspace><tab>n4g00<backspace><tab>g<no-action>3" In xdm it was
fine (or I couldn't have logged in). There's probably some very obvious
way to fix this...? Adding "+kb" did nothing. Adding "-kb" made Ubuntu
prompt me to identify the keyboard, either to "Use X settings" or "Keep
GNOME settings"... I chose the former, which ended up making no
difference; still gibberish.
Are you using gnome 2.18? I've had that same problem on gnome 2.18 on
edubuntu and gentoo servers. I found the following workaround (see
the last paragraph on the page linked below)
Basically, you add an invalid keyboard layout, and then gnome fails to
load the invalid layout and...apparently loads a working default one.
Hm, there aren't any already there in
desktop/gnome/peripherals/keyboard/kbd. There's one set up in
/desktop/gnome/peripherals/keyboard/kbk.sysbackup which is just
us-generic, which I think it's been falling back to anyway.
... But I'll try messing with it...
Ooh! That seems to have worked. Haha. (Putting a bogus value - I
couldn't type a real one if I wanted to - into the kbd/layouts key. I
left the kbd.sysbackup folder alone.) Now it appears I can type in it
properly in Xnest...
... twice in a row. I also don't get the error dialogs that guy reports
getting.
Aha, but I do in Xephyr, but as he says, the keyboard works afterwards
anyway...
And adding -kb to the Xephyr commandline makes those errors go away.
OK. :-) I'd prefer fullscreen, but just at the moment, and for the first
time, I actually have a working solution. :-) I think Xnest is working
better than Xephyr though; the double-mouse-pointer problem isn't there
and the remote desktop size always matches the given screen size. We
definitely can't afford to lose Xnest yet.
I'd still prefer to go fullscreen with Xquartz, as in:
and use Spaces to move it where I want it. But it's still quitting out
(no sign of an error or a crash, just a quit) immediately on login - on
destruction of the xdm fullscreen 'window' I'd guess? A properly working
Xephyr -fullscreen would be fine. (By "properly working" I mean, no
titlebar, and actually fits full-screen properly.)
--
Rachel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden
