Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have two linux machines, one (A) is a desktop and the second (B) is embedded and doesn't have any peripherals (in its usual configuration). I want to run X applications located on B and tunnel X output to machine A using "ssh -XC [host]". This fails. Gnomemeeting and synaptic both give me X errors and refuse to start. xeyes however displays fine.
I then attach a non-usb mouse, keyboard, and monitor to machine B and try to run synaptic and gnomemeeting locally after a startx. The startx fails. I get [EE] errors that it can't find the devices (/dev/mouse and /dev/input/mice). I've tried with /dev/psaux also.
I'm not sure I understand what you're trying to achieve.
You have a remote machine that has the capabilities to run X applications.
You have a local machine running X11? If X isn't running locally there
are no means to display the output of the remote machine.
However you can't get X to go locally because it doesn't detect your
Ok ... so, what distro are you using on the machine that has
the X problem? Are you running hotplug? PS/2 mice commonly
don't get picked up until a reboot, USB *should* work. What
does lsmod say in regards to either, any hints of them in
It would appear that I still don't understand what you're doing.
The robot is the embedded system (B), and you're trying to output
stuff from the robot on the desktops (A) screen?
No, you understand me right.
Originally Posted by Tinkster
In the first case there's no need at all to run X on the robot.
I'm not intimately familiar with how X and/or X tunneling works, but since I'm tunneling X output through SSH, clearly X is "running" at some level.
To cut to the chase, AllowMouseOpenFail=true has X tunneling to machine A working without any peripherals connected to the embedded device B. So it seems it was the mouse errors that were preventing the tunneling from working.
I would recommend not using that AllowMouseOpenFail option. You should tell your robot that he has to carry the mouse at all times. It will be like a safety. That way, if your robot ever goes on a murderous "kill all the humans"-type rampage, you can tell the military that all they have to is unplug the mouse, and X will crash.
See? The X.org authors knew what they were doing. You're just asking for trouble.