[arch-general] X errors...
Has anyone had any issues like this with X ? X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 102 (X_ChangeKeyboardControl) Serial number of failed request: 2090 Current serial number in output stream: 2091 It looks like an X issue...but how the hell do I fix/workaround ?
On Fri, Jun 13, 2008 at 12:24 PM, Allie Daneman <df@drainfade.com> wrote:
Has anyone had any issues like this with X ?
X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 102 (X_ChangeKeyboardControl)
What are you doing when you get the error? Are you by any chance using X over ssh? A little googling found this: http://www.cs.rochester.edu/twiki/bin/view/Main/LinuxChangesAugust2005
From the link: "This is a result of the openssh upgrade, which adds some security measures to X11 forwarding. The solution to ridding yourself of these error messages is to add the line
ForwardX11Trusted yes to your ~/.ssh/config file. X applications will then forward just fine. If you still have trouble, make sure you don't have an inadvertent emacs alias to emacs -nw, and if that doesn't work, use the -Y flag to ssh." -- Ryan W Sims
That was it...and that was the 1 line missing my ssh_config file. I already had: ForwardAgent yes ForwardX11 yes Thanks...
On Fri, Jun 13, 2008 at 12:24 PM, Allie Daneman <df@drainfade.com> wrote:
Has anyone had any issues like this with X ?
X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 102 (X_ChangeKeyboardControl)
What are you doing when you get the error? Are you by any chance using X over ssh? A little googling found this: http://www.cs.rochester.edu/twiki/bin/view/Main/LinuxChangesAugust2005
From the link: "This is a result of the openssh upgrade, which adds some security measures to X11 forwarding. The solution to ridding yourself of these error messages is to add the line
ForwardX11Trusted yes
to your ~/.ssh/config file. X applications will then forward just fine. If you still have trouble, make sure you don't have an inadvertent emacs alias to emacs -nw, and if that doesn't work, use the -Y flag to ssh."
-- Ryan W Sims
participants (3)
-
Allie Daneman
-
metin
-
Ryan Sims